Skip to content
This repository has been archived by the owner on Jan 15, 2021. It is now read-only.

Travis should use latest XCode version #36

Closed
enricogior opened this issue Aug 25, 2016 · 4 comments
Closed

Travis should use latest XCode version #36

enricogior opened this issue Aug 25, 2016 · 4 comments
Assignees
Milestone

Comments

@enricogior
Copy link
Member

enricogior commented Aug 25, 2016

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.

@yaronyg
Copy link
Member

yaronyg commented Aug 31, 2016

Right now it's using Xcode 6 and 7 and that means we need 2x time to run which is silly so we need to turn of 6 but we don't yet know how.

@enricogior
Copy link
Member Author

enricogior commented Sep 1, 2016

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

@yaronyg
Copy link
Member

yaronyg commented Sep 1, 2016

We will experiment with other services since we really don't want to debug Travis. Maybe run it with Jenkins on a mac mini?

@enricogior
Copy link
Member Author

I've opened a new issue to track the specific work of finding an alternative.
#43

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants