You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 15, 2021. It is now read-only.
I've tried to update trevis.xml to use the latest XCode version previously, but it was failing because the log size exceeded the max length, the solution maybe to redirect the stderr and/or the stdout to a log file. I need to verify if we can later access the log file for investigation if needed.
The text was updated successfully, but these errors were encountered:
Things are not looking good at all with Travis and XCode 7.3.
The first build failed after 40 minutes because of tests failure with jxcore V8: [03:48|% 100|+ 633|- 3]: Done
The second build failed after 1h27m because of tests failure with both jxcore V8 and SM: [03:00|% 100|+ 633|- 3]: Done [04:49|% 100|+ 634|- 2]: Done
The third build failed after 41 minutes because of tests failure with jxcore V8: [02:57|% 100|+ 634|- 2]: Done
By default Travis uses XCode 6.1 on OS X 10.9 and in that case it takes 20m to build and run the tests successfully.
So there are two issues with Travis and XCode 7.3:
the unjustified long time to compile.
the random tests failure that we never experience when using XCode 7.3 on our dev machines.
I also tried XCode 6.4 on OS X 10.10, it built in 17m and failed for V8:
ld: library not found for -lgcc_s.10.5
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[1]: *** [/Users/travis/build/thaliproject/jxcore/out/Release/mksnapshot] Error 1
make: *** [jx] Error 2
also one test failed for SpiderMonkey: [03:15|% 100|+ 635|- 1]: Done
This is a sub task of #16
I've tried to update trevis.xml to use the latest XCode version previously, but it was failing because the log size exceeded the max length, the solution maybe to redirect the stderr and/or the stdout to a log file. I need to verify if we can later access the log file for investigation if needed.
The text was updated successfully, but these errors were encountered: