-
-
Notifications
You must be signed in to change notification settings - Fork 925
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Travis build should be split in a "build jruby" phase and the rest #3050
Comments
I originally added travis_retry around entire builds because maven dependency fetching was failing intermittently. If maven builds (the actual build part) have stabilized, it would be reasonable to reduce the scope of travis_retry. |
in other projects I do a |
I think we should do travis_retry just around the build itself and remove the test run from being retried. If there's flaky tests or specs we should address them or mask them. |
@mkristian Could you try to move the build in |
will find some time tomorrow - there are other little build issue pending On Tue, Jun 16, 2015 at 2:11 PM, Benoit Daloze notifications@github.com
|
it looks like those "extended" maven tests crash the VM once in a while. the old retry did hide this |
@mkristian Thanks! |
Current travis configuration has a
travis_retry
around the whole maven command, which makes some failing builds last 3 times as long as they should.Also, if building jruby fails, there is no much point in running the tests afterwards.
Should
./mnvw -Pbootstrap install
be in theinstall
orbefore_script
section?The text was updated successfully, but these errors were encountered: