[INXY.COM] Re: AW: compc Error on CI / Jenkins (folder-name-dependent/Cache?)

[Billie Abrahams (INXY.COM)]

##- Please type your reply above this line -##

Your request (#464846) has been updated. To add additional comments, reply to 
this email or click the link below:


--

Billie Abrahams, Oct 24, 2023, 23:54 GMT+3

Hello,

I don't see anything that points to us. Please tell me how we can help you?

Best regards,
Billie Abrahams
INXY.HOSTING Support Team

https://inxy.hosting/


This email is a service from INXY.COM.









[KM9WMV-E2E3M]

[INXY.COM] Re: AW: compc Error on CI / Jenkins (folder-name-dependent/Cache?)

[Aaron McKane (INXY.COM)]

##- Please type your reply above this line -##

Your request (#464846) has been updated. To add additional comments, reply to 
this email or click the link below:


--

Aaron McKane, Oct 24, 2023, 13:57 GMT+3

Hello,

Please specify the following information for us to review this:


1. The email address that your INXY account is linked to;
2. The service ID;

Thank you.

Best regards,

Aaron McKane

inxy.hosting Support Team

Suite 401, Agias Zonis Centre, Agias Zonis Street 12, Limassol, 3027, Cyprus

https://www.inxy.hosting/


This email is a service from INXY.COM.









[KM9WMV-E2E3M]

[Request received]

[INXY.COM]

##- Please type your reply above this line -##

Your request (464846) has been received and is being reviewed by our support 
staff.

To add additional comments, reply to this email.


This email is a service from INXY.COM.









[KM9WMV-E2E3M]

Re: compc Error on CI / Jenkins (folder-name-dependent/Cache?)

[Alex Harui]

Hi Jan,

I downloaded the output and displayed it in VSCode.  VSCode says there are 4808 
lines of output.
It looks like compc is called several times, but the last call is on line 587.  
On line 1747 the first of 3 errors are reported.  I think that should cause the 
build to fail.

One thing you could try is to capture the same output for the successful build 
and compare output.  Find and replace folder names so they all match before 
comparing output.

Hope that helps,
-Alex

On 10/23/23, 4:09 AM, "Weber Jan" mailto:jan.we...@dallmeier.com.inva>LID> wrote:


EXTERNAL: Use caution when clicking on links or opening attachments.




Hi Alex,


first of all, thank you very much for your support on this issue - really 
appreciated!


I'm pretty sure the build output is entirely written in the console log; 
normally we do see here the typical stack traces and actual compiler errors in 
the same way we would see them from/in the IDE.


I have uploaded the Jenkins output log to the cloud from the build process 
which fails so you can actually see what is getting logged:


https://cloud.dallmeier.com/s/D246GdaGSQ9Q9km 

Password: H76X436K


Hint: I removed a few non-public texts in the log and replaced them with "[*** 
CONTENT MANUALLY REMOVED HERE ***]"




















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 
>




Germany




Germany




[banner]
 




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 mailto:aha...@adobe.com.inva>LID>
Gesendet: Donnerstag, 19. Oktober 2023 19:14
An: users@flex.apache.org 
Cc: Fischer Michael mailto:michael.fisc...@dallmeier.com>>; Staudte Norbert 
mailto:norbert.stau...@dallmeier.com>>
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.


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" 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; 
 
 
 (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