www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: Continuum - Commons Pool unit test is stuck (again)
Date Tue, 13 Sep 2011 10:45:46 GMT
On 13 September 2011 10:18, Stefan Bodewig <bodewig@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?
AFAIK, that just kills the test thread, not the entire process.

Also, I presume the same problem applies to Continuum itself killing builds.

> Stefan

View raw message