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 mvn validate for the travis install script. maybe jruby could do a mvn install which basically just downloads and compiles the main parts (core + truffle + lib)

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 install:?
I would do it myself but I am not sure what's -Dinvoker.skip=false is about or what kind of cleaning is desirable.

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
wrote:

@mkristian https://github.com/mkristian Could you try to move the build
in install:?
I would do it myself but I am not sure what's -Dinvoker.skip=false is
about or what kind of cleaning is desirable.

—
Reply to this email directly or view it on GitHub
#3050 (comment).

it looks like those "extended" maven tests crash the VM once in a while. the old retry did hide this

@mkristian Thanks!