Issue1128 durack1 cython0.22 update#1129
Issue1128 durack1 cython0.22 update#1129durack1 wants to merge 20 commits intoCDAT:masterfrom durack1:issue1128_durack1_cython0.22Update
Conversation
|
@doutriaux1 yep that travis_submit call could be the problem..? |
|
Useful info on travis CI build options: http://docs.travis-ci.com/user/build-timeouts/#Build-times-out-because-no-output-was-received |
|
@doutriaux1 seems like timeouts are more explicitly the problem now: |
|
@aashish24 I think your expertise is required here - seems like the travis config needs some tweaks.. |
There was a problem hiding this comment.
Please don't change travis options. I explicitly set them for a reason. The travis has a timeout so we can only test lean mode for now. Also, I would recommend having a discussion over the email first -:)
|
@durack1 could you please undo travis changes for now. Currently the travis is set only for lean mode as travis has time limitations. I am working on another solution but in the mean time, if you want to test then you can setup a dashboard that can test a particular branch say "integration". Let me know if you need more help on that. |
|
@aashish24 I don't think this is true, with travis ci we have 120 mins.. It also seems that the problem is more related to timeouts within the install (no activity for 20 mins) rather than exceeding the 120 min limit, when reviewing the logs of the failed builds this seems to be the problem |
|
@aashish24 following the log errors this is what we've tried: http://docs.travis-ci.com/user/build-timeouts/#Build-times-out-because-no-output-was-received |
|
@aashish24 so this is the latest build failure, with both travis_build.cmake and travis_submit.cmake back in (using |
…om/durack1/uvcdat into issue1128_durack1_cython0.22Update
…k1/uvcdat into issue1128_durack1_cython0.22Update
@doutriaux1 @aashish24 there's no rush to merge this - 2.3 would be fine..