Potential timeout issues - tests running in the same vm

Alan Bateman Alan.Bateman at oracle.com
Wed Nov 16 17:27:49 UTC 2011

On 16/11/2011 17:02, Gary Adams wrote:
> If we could demonstrate that the tests were not reliable in samevm mode
> on a slow machine, then there might be more evidence that these tests
> need to be isolated. e.g. even though the test execution is requested 
> to be
> in as fast as possible configuration, the test itself may be 
> inherently unreliable
> when run in that mode.
If tests can't run in samevm (or agentvm) mode then they need to specify 
/othervm in their @run tag. Just so you know, we've put a lot of work 
into fixing tests so that they can run in agentvm mode (at least for the 
libraries, security, networking). It's unfortunate that we have some 
tests that can't run in samevm/agentvm mode but mostly it's because the 
tests change something in the environment that would cause problems for 
other tests or they need special environments. So are you just grep'ing 
the repository for tests that override the timeout or have you run into 
problems with these tests?


More information about the core-libs-dev mailing list