The compiler source is part of the Flex SDK, so if you can build from sources you can modify the compiler to generate more info.
I took a look at the exit code logic. It looks like it is returning number of errors, but it should report those errors to System.err. Could that output stream be missing from the captured output? -Alex On 10/19/23, 1:12 AM, "Weber Jan" <jan.we...@dallmeier.com.inva <mailto:jan.we...@dallmeier.com.inva>LID> wrote: EXTERNAL: Use caution when clicking on links or opening attachments. On the CI there is one job with several pipeline steps - if this job is targeting the folder with the ending "Tool" instead of "Tool2" it always fails without giving a specific error. The source code and git revision is the very same; job is set to do a clean/full checkout, too. I deleted the entire folder for "Tool" so it gets recreated but it still fails to build. I did compare the entire contents of both folders with a diff ("Tool" and "Tool2") and both are exactly the same. The job/pipeline uses both, compc and mxmlc, to first build some libraries using compc and then build the main executable using mxmlc. When the name is "Tool": 1) one specific module cannot be built with compc so the step for creating the main executable using mxmlc is never reached 2) pipeline steps before this one failing module do actually get build successfully with compc When the output folder is renamed to something else like "Tool2" everything is built successfully. The only error we can see in the logs when the one module is failing to be built is "ERROR: script returned exit code 1". The screenshot from "https://cloud.dallmeier.com/s/9Hdk6KaF4HxGQNB"; <https://cloud.dallmeier.com/s/9Hdk6KaF4HxGQNB;> (password "FWxH9jb7") shows the job with its pipeline steps where the first build on the screenshot #7 is outputting to the folder ending with "Tool2" (successful build), the second build #8 is using the folder with the ending "Tool" (which fails, see "No changes" label indicating nothing has changed commit/repository-wise); build #9 then having changed the name of the output folder back to ending "Tool2" builds successfully again. For the upcoming build #10, I now delete the entire folder ending with "Tool" from workspace on the CI, change the project to output to folder "Tool" (which currently is "Tool2" from build #9) by renaming the project on Jenkins ("Rename Pipeline SeMSy5-Translation-Tool2" to "SeMSy5-Translation-Tool") and then it fails again to build. I was wondering if it would be possible to get a some kind of debug-version of compc which outputs additional information on the actual error and why it cannot build? Mit freundlichen Grüßen / Best Regards i.A. Jan Weber Software Development Contact: Location: Head & Accounts Office: tel +49 941 8700 326 Bahnhofstr. 16 Bahnhofstr. 16 fax 93047 Regensburg 93047 Regensburg mail jan.we...@dallmeier.com <mailto:jan.we...@dallmeier.com><mailto:jan.we...@dallmeier.com <mailto:jan.we...@dallmeier.com>> Germany Germany [banner] <https://www.dallmeier.com/signatur> <https://www.dallmeier.com/signatur;> http://www.dallmeier.com/<http://www.dallmeier.com/en/home.html> <http://www.dallmeier.com/;> Dallmeier electronic GmbH & Co.KG CEO: Registry Court: VAT ID: Unlimited Partner: Registry Court: Thomas Dallmeier Amtsgericht Regensburg HRA 6827 DE813790649 Dallmeier GmbH Amtsgericht Regensburg HRB 9085 -----Ursprüngliche Nachricht----- Von: Alex Harui <aha...@adobe.com.inva <mailto:aha...@adobe.com.inva>LID> Gesendet: Montag, 9. Oktober 2023 18:28 An: users@flex.apache.org <mailto:users@flex.apache.org> Betreff: Re: compc Error on CI / Jenkins (folder-name-dependent/Cache?) ACHTUNG: Diese Mail kommt von einem externen Absender. Bitte behandeln Sie alle Dateianhänge und Links mit besonderer Vorsicht. Im Zweifel wenden Sie sich bitte an die IT. Is there a valid job/workspace/pipeline that uses the folder ending in "Tool" instead of "Tool2"? Otherwise, try deleting that workspace and see if it gets re-created again and which job did it. Are there other jobs or pipelines that run compc or mxmlc? -Alex On 10/9/23, 12:32 AM, "Weber Jan" <jan.we...@dallmeier.com.inva <mailto:jan.we...@dallmeier.com.inva> <mailto:jan.we...@dallmeier.com.inva <mailto:jan.we...@dallmeier.com.inva>>LID> wrote: EXTERNAL: Use caution when clicking on links or opening attachments. I’m reaching out to you regarding a rather strange behavior of compc on the CI/Jenkins, when it tries to build a specific swc module within a pipeline script. An error occurs, where it looks like this is actually depending on the name of the root folder where the modules are located at. The pipeline builds several modules successfully with compc but one of the modules always fails to build. If the folder where the sources are located and where compc is outputting to is renamed, the module is actually build. Same sources (/git revision, clean/new checkout). I uploaded two images for better imagination of what is going on here: Jenkins Pipeline: URL: https://cloud.dallmeier.com/s/9Hdk6KaF4HxGQNB <https://cloud.dallmeier.com/s/9Hdk6KaF4HxGQNB> <https://cloud.dallmeier.com/s/9Hdk6KaF4HxGQNB> <https://cloud.dallmeier.com/s/9Hdk6KaF4HxGQNB;> Password: FWxH9jb7 Jenkins Workspace with the different folder names: URL: https://cloud.dallmeier.com/s/pj7qZCsiEebnwMT <https://cloud.dallmeier.com/s/pj7qZCsiEebnwMT> <https://cloud.dallmeier.com/s/pj7qZCsiEebnwMT> <https://cloud.dallmeier.com/s/pj7qZCsiEebnwMT;> Password: MsGrttg5 When the specific module is not building, the following error is outputted - please note the difference in the folder names, which is "SeMSy5-Translation-Tool" (building fails) and "SeMSy5-Translation-Tool2" (building successfully). Running in D:\Program Files (x86)\Jenkins\workspace\SeMSy5-Translation-Tool\SeMSy-Next-Lib D:\Program Files (x86)\Jenkins\workspace\SeMSy5-Translation-Tool\SeMSy-Next-Lib>"C:\Program Files (x86)\Ant-1.10.12\bin\ant" main Buildfile: D:\Program Files (x86)\Jenkins\workspace\SeMSy5-Translation-Tool\SeMSy-Next-Lib\build.xml [compc] Loading configuration file D:\dependencies\AIR_50.2.2\frameworks\air-config.xml BUILD FAILED D:\Program Files (x86)\Jenkins\workspace\SeMSy5-Translation-Tool\SeMSy-Next-Lib\build.xml:46: compc task failed. ERROR: script returned exit code 1 When it is building, the following output: Running in D:\Program Files (x86)\Jenkins\workspace\SeMSy5-Translation-Tool2\SeMSy-Next-Lib D:\Program Files (x86)\Jenkins\workspace\SeMSy5-Translation-Tool2\SeMSy-Next-Lib>"C:\Program Files (x86)\Ant-1.10.12\bin\ant" main Buildfile: D:\Program Files (x86)\Jenkins\workspace\SeMSy5-Translation-Tool2\SeMSy-Next-Lib\build.xml [compc] Loading configuration file D:\dependencies\AIR_50.2.2\frameworks\air-config.xml [compc] D:\Program Files (x86)\Jenkins\workspace\SeMSy5-Translation-Tool2\SeMSy-Next-Lib\build\SeMSy-Next-Lib.swc (15942226 bytes) BUILD SUCCESSFUL The issue is very strange and hard to understand. Could anyone imagine anything that may cause this? Is something cached somewhere where I could clear the cache? Mit freundlichen Grüßen / Best Regards i.A. Jan Weber Software Development Contact: Location: Head & Accounts Office: tel +49 941 8700 326 Bahnhofstr. 16 Bahnhofstr. 16 fax 93047 Regensburg 93047 Regensburg mail jan.we...@dallmeier.com <mailto:jan.we...@dallmeier.com> <mailto:jan.we...@dallmeier.com <mailto:jan.we...@dallmeier.com>><mailto:jan.we...@dallmeier.com <mailto:jan.we...@dallmeier.com> <mailto:jan.we...@dallmeier.com <mailto:jan.we...@dallmeier.com>>> Germany Germany [banner] <https://www.dallmeier.com/signatur> <https://www.dallmeier.com/signatur;> <https://www.dallmeier.com/signatur;> <https://www.dallmeier.com/signatur;> http://www.dallmeier.com/<http://www.dallmeier.com/en/home.html> <http://www.dallmeier.com/;> <http://www.dallmeier.com/;> <http://www.dallmeier.com/;> Dallmeier electronic GmbH & Co.KG CEO: Registry Court: VAT ID: Unlimited Partner: Registry Court: Thomas Dallmeier Amtsgericht Regensburg HRA 6827 DE813790649 Dallmeier GmbH Amtsgericht Regensburg HRB 9085
