Potential timeout issues - tests running in the same vm

chris hegarty chris.hegarty at oracle.com
Wed Nov 16 23:23:38 UTC 2011

On 16/11/2011 18:09, Alan Bateman wrote:
> On 16/11/2011 17:43, Gary Adams wrote:
>> Agreed!
>> I intend to do a full linux/arm jtreg
>> run with a local beagleBoard cranked down
>> to 300 MHz. Sounds like I should test
>> the default and samevm mode.
>> I'll start with a jdk7 embedded image
>> to get a baseline.

The timeouts in the tests you mentioned are particularly small, I guess 
this is where the issue of reliability is coming from, right? If these 
timeouts (in some cases) are just catch all for bugs that used to 
deadlock, but no longer do (since they are now fixed). Would it make 
sense to just increase these timeouts in the tests themselves?


> It's not currently possible to specify the top level test directory and
> run all tests in samevm or agentvm mode. I don't think it's possible to
> run the AWT tests in samevm mode for example. If you look at
> jdk/test/Makefile then you'll see which areas can run in agentvm (or
> samevm) mode. It's something that I was chatting with Jon about recently
> and he pointed me to a patch from Mark Wielaard [1] that whitelists
> directories of tests that can run in samevm mode. I think Jon is hoping
> to integrate this, maybe extending it to work with the newer agent vm mode.
> -Alan
> [1]
> http://mail.openjdk.java.net/pipermail/jtreg-use/2008-November/000048.html

More information about the core-libs-dev mailing list