-
Bug
-
Resolution: Fixed
-
P2
-
21
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8343587 | 17.0.15-oracle | Daniel Skantz | P2 | Closed | Fixed | b01 |
| JDK-8345457 | 17.0.15 | Goetz Lindenmaier | P2 | Resolved | Fixed | b01 |
| JDK-8346092 | 17.0.14.0.1-oracle | Daniel Skantz | P2 | Resolved | Fixed | b01 |
| JDK-8343821 | 17.0.13.0.1-oracle | Daniel Skantz | P2 | Closed | Fixed | b01 |
| JDK-8349456 | 11.0.28-oracle | Daniel Skantz | P2 | Resolved | Fixed | master |
The following fake exception stacktrace is for failure analysis.
nsk.share.Fake_Exception_for_RULE_Creation: (ji05t001.cpp:263) TEST FAILURE: AttachCurrentThread() returns: -1
at nsk_lvcomplain(nsk_tools.cpp:172)
# ERROR: ji05t001.cpp, 263: TEST FAILURE: AttachCurrentThread() returns: -1
- backported by
-
JDK-8345457 Test vmTestbase/nsk/jvmti/scenarios/jni_interception/JI05/ji05t001/TestDescription.java fails after JDK-8308341
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
JDK-8309243 Re-examine when JNI methods should be allowed during the VM initialization process
-
- Open
-
-
-
- Resolved
-
- links to
-
Commit
openjdk/jdk/01199698
-
Commit(master)
openjdk/jdk17u-dev/ed63b718
-
Review
openjdk/jdk/14239
-
Review(master)
openjdk/jdk17u-dev/3084