On 2011-09-13, sebb wrote: > On 13 September 2011 10:18, Stefan Bodewig <bode...@apache.org> wrote: >> On 2011-09-13, sebb wrote:
>>> In case it helps anyone else, I updated the pom as follows: >>> <artifactId>maven-surefire-plugin</artifactId> >>> <configuration> >>> <!-- Don't allow test to run for more than 30 minutes --> >>> >>> <forkedProcessTimeoutInSeconds>1800</forkedProcessTimeoutInSeconds> >>> This kills the test; however the output only reports the test class, >>> not the individual method, and the surefire report file is empty. >>> To get better info, add @Test(timeout=nnn) to all the likely culprits. >> Just be careful to disable core dumps if you do something like this on a >> Unix-like system. We used to have a problem with a multitude of core >> dumps for java processes filling up the disk of vmgump when surefire >> killed forked processes. > Just to be clear, I presume you are not referring to > @Test(timeout=nnn) causing dumps? Yes - at least I wouldn't know if @Test did cause core dumps. > Also, I presume the same problem applies to Continuum itself killing builds. True, as it was true for Gump itself. Likely applies to Jenkins and others as well. On second thought it has been the FreeBSD jail and not vmgump where this happened as core dumps seem to be disabled on Ubuntu by default. Stefan
