Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-releng] Why are our JUnit tests not running? -- all fixed, time reset to 1 hour.

Just wanted to follow up,
I think the issue with tests "hanging" was

After moving to the build with that fix reverted, we no longer timed out, even with 30 minute maximum ... well, except for the big jpt one. :)

So, I've set our time back to 1 hour maximum per suite, which is still way to long ... but best solution until we have better strategies and policies.


From: David M Williams/Raleigh/IBM@IBMUS
To: wtp-releng@xxxxxxxxxxx
Date: 11/25/2009 07:32 PM
Subject: [wtp-releng] Why are our JUnit tests not running?
Sent by: wtp-releng-bounces@xxxxxxxxxxx

Well, they are, a little. But, the overall test process times out before they complete. That process is restricted to 4 hours, and each test bundle is restricted to one hour.
And what's happening is that some tests are taking their whole hour allotment before being timed out.

Not sure why this started  happening (build machine does not seem especially busy) but it is suspicious that I just moved up the Platform prereq.  

While we investigate though, I've changed the overall limit to 5 hours, and each test limit to 30 minutes. (On a local build, I canceled some of our longer tests ... you know who you are ... and the rest seemed to finish fine). We'll see if this combination gets us through.

Just wanted to keep everyone informed with as much as I know ... what little that is.

wtp-releng mailing list

Back to the top