Potential timeout issues - tests running in the same vm
chris.hegarty at oracle.com
Thu Nov 17 09:14:10 UTC 2011
On 17/11/2011 08:29, Alan Bateman wrote:
> I see Chris's mail points out that some tests do have an unusually small
> timeout. For those tests then I would be tempted to just remove the
> timeout. Most likely the original author of the test put a small timeout
> to make it quick to test on a JDK that didn't have the fix.
Right, I've seen this before ( bug in JDK that causes deadlock, set
small timeout on test so doesn't block for too long before being
interrupted by jtreg). But if these tests ever fail then it means we
have a problem, the small timeout is just not necessary at all in a JDK
that doesn't have the issue being tested for.
Maybe this would be a good place to start and eliminate some of the low
hanging fruit ;-)
More information about the core-libs-dev