On Thu, 2014-12-11 at 18:33 +0100, Bertrand Delacretaz wrote: > Hi, > > On Thu, Dec 11, 2014 at 5:35 PM, Carsten Ziegeler <cziege...@apache.org> > wrote: > > Is Jenkins logging at the log output?... > > I don't think so, the log ends with > ... > >> Killed > >> > >> Results : > ... > > I haven't found the reason in this log, probably an external/Jenkins > cause. It's not a timeout AFAICS as the job took 19 minutes.
If you look at the main Jenkins build log [1] it complains that surefire crashed: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-failsafe-plugin:2.16:integration-test (default) on project org.apache.sling.event: Execution default of goal org.apache.maven.plugins:maven-failsafe-plugin:2.16:integration-test failed: The forked VM terminated without saying properly goodbye. VM crash or System.exit called ? One (wild) idea is that two jobs were running at the same time on the slave and both were using lots of memory so the Linux OOM killer stopped our process. Robert [1]: https://builds.apache.org/job/sling-trunk-1.7/1237/console
