[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-serviceability-dev
Subject:    Integrated: 8282666: nsk/jvmti/PopFrame/popframe004 failed with: TEST FAILED: 30 JVMTI events were g
From:       Serguei Spitsyn <sspitsyn () openjdk ! org>
Date:       2022-07-29 21:53:41
Message-ID: wKG5HjDvm0vRpmEDasi3dRTkSNVw1FowohUJtMLlTsg=.35896b53-0976-41ca-88f8-273c0c906d48 () github ! com
[Download RAW message or body]

On Fri, 29 Jul 2022 19:08:35 GMT, Serguei Spitsyn <sspitsyn@openjdk.org> wrote:

> The nsk.jvmti test popframe004 is failing with the JVM args:
> `-Xcomp -XX:+CreateCoredumpOnCrash -ea -esa -XX:CompileThreshold=100 \
> -XX:+UnlockExperimentalVMOptions -XX:-TieredCompilation` 
> The call to join() below should not have a timeout parameter.
> 
> try {
> if (popFrameClsThr.isAlive())
> popFrameClsThr.join(2000);
> } catch (InterruptedException e) {
> out.println("TEST INCOMPLETE: caught " + e);
> totRes = FAILED;
> }
> if (popFrameClsThr.isAlive()) {
> out.println("TEST FAILED: thread with the method of " +
> "the popped frame is still alive");
> totRes = FAILED;
> } 
> 
> If the execution is slow by any reason (e.g. because of a compilation) then it \
> causes the main thread to fail joining with the target thread which is why the test \
> is failing with these symptoms. 
> This problem is hard to reproduce even in 1000's of runs on mach5.

This pull request has now been integrated.

Changeset: 15943e42
Author:    Serguei Spitsyn <sspitsyn@openjdk.org>
URL:       https://git.openjdk.org/jdk/commit/15943e424244abb2fd033521f3ca562f3539e8fd
                
Stats:     2 lines in 1 file changed: 0 ins; 0 del; 2 mod

8282666: nsk/jvmti/PopFrame/popframe004 failed with: TEST FAILED: 30 JVMTI events \
were generated by the function PopFrame()

Reviewed-by: lmesnik, amenkov

-------------

PR: https://git.openjdk.org/jdk/pull/9689


[prev in list] [next in list] [prev in thread] [next in thread]