-
Bug
-
Resolution: Unresolved
-
P5
-
11, 12, 15, 16
Following popframe tests fail with Graal on macos and windows.
- vmTestbase/nsk/jvmti/PopFrame/popframe001/TestDescription.java
TEST FAILED: a tested frame has not been really popped
- vmTestbase/nsk/jvmti/PopFrame/popframe003/TestDescription.java
TEST FAILED: a tested frame has not been really popped
- vmTestbase/nsk/jvmti/PopFrame/popframe005/TestDescription.java
TEST FAILED: finally block was executed after popping
TEST FAILED: the lockObj[0]'s monitor became free too early
TEST FAILED: Lock acquired by a frame, different from the popped one,
was released when the popped frame had been popped
- vmTestbase/nsk/jvmti/PopFrame/popframe001/TestDescription.java
TEST FAILED: a tested frame has not been really popped
- vmTestbase/nsk/jvmti/PopFrame/popframe003/TestDescription.java
TEST FAILED: a tested frame has not been really popped
- vmTestbase/nsk/jvmti/PopFrame/popframe005/TestDescription.java
TEST FAILED: finally block was executed after popping
TEST FAILED: the lockObj[0]'s monitor became free too early
TEST FAILED: Lock acquired by a frame, different from the popped one,
was released when the popped frame had been popped
- relates to
-
JDK-8215196 [Graal] vmTestbase/nsk/jvmti/PopFrame/popframe003/TestDescription.java fails with "changes for the arguments of the popped frame's method, did not remain current argument values"
-
- Open
-
-
JDK-8214093 [Graal] jck:vm/jvmti/ForceEarlyReturn tests intermittently and randomly fail with Graal
-
- Closed
-
-
JDK-8216386 vmTestbase/nsk/jvmti/PopFrame/popframe005/TestDescription.java fails
-
- Resolved
-