RFR(S): 8211932: [ppc][testbug] runtime/jni/terminatedThread/TestTerminatedThread.java fails as threads don't terminate immediately (original) (raw)

David Holmes david.holmes at oracle.com
Tue Oct 9 23:21:59 UTC 2018

Hi Goetz,

There is already an open bug for this issue - JDK-8208159 - but it has only reproduced in a stress environment where we think thread-id's are being recycled (which means waiting longer won't help). This should be OS not CPU specific so I'm very interested to know in what circumstances you see this failure.

I created an instrumented version of the test that did a pthread_kill on the target to check for ESRCH - which it got - yet we still see failures in those stress environments.

David

On 10/10/2018 1:10 AM, Lindenmaier, Goetz wrote:

Hi,

On ppc, one still sees increasing thread cpu times after a thread has joined. This makes TestTerminatedThread fail. This change gives the check a few seconds to wait until the thread disappears. Please review. http://cr.openjdk.java.net/~goetz/wr18/8211931-terminatedThrd/01/test/hotspot/jtreg/runtime/jni/terminatedThread/TestTerminatedThread.java.udiff.html Best regards, Goetz.

More information about the hotspot-runtime-dev mailing list