Hi David, The tests start a couple of external processes and have a procedure of destroying them if something unexpected happens. But when JVM crashes in the middle of the execution this procedure is useless and processes are left on servers. It should be up to framework to do clean-up. Unfortunately the JTreg framework has no mechanism of removing process trees today. But it has been discussed a lot and hopefully will be implemented in the nearest future.
Best regards, Katja ----- Original Message ----- From: david.hol...@oracle.com To: yekaterina.kantser...@oracle.com, serviceability-dev@openjdk.java.net Sent: Monday, April 7, 2014 2:57:09 AM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna Subject: Re: RFR: 8031766: jstatd nightly tests failing with Expected one jstatd process, got 2. Test will be canceled. Hi Katja, I don't object to making the test more resilient, but I do have to wonder why we have multiple jstatd processes as that would seem to indicate another problem that needs addressing. David On 4/04/2014 11:25 PM, Yekaterina Kantserova wrote: > Hi, > > Could I please have a review of this fix. > > webrev: http://cr.openjdk.java.net/~ykantser/8031766/webrev.00/ > bug: https://bugs.openjdk.java.net/browse/JDK-8031766 > > The bug is not visible. But short summary is as follows. > sun/tools/jstatd/TestJstatdPort.java, TestJstatdPortAndServer.java, > TestJstatdServer.java have been failing because they expect only one > jstad process running. I've added a unique identifier for the jstad > process tests start. So the tests will no more care about how many other > jstad processes are running. > > Thanks, > Katja
