-
Bug
-
Resolution: Fixed
-
P4
-
8
-
b06
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8357235 | 21.0.9-oracle | Md Shahbaz Yusuf | P4 | Resolved | Fixed | master |
| JDK-8357487 | 21.0.8 | Goetz Lindenmaier | P4 | Resolved | Fixed | b05 |
| JDK-8357295 | 17.0.17-oracle | Md Shahbaz Yusuf | P4 | Resolved | Fixed | master |
| JDK-8357495 | 17.0.16 | Goetz Lindenmaier | P4 | Resolved | Fixed | b05 |
Creating threads...
Can't reproduce OOME due to a limit on iterations/execution time. Test was useless.
when they are unable to reproduce OOME.
This is not a problem when the tests are run individually. However, when resexhausted004, which in turn runs all the 3 tests, is run we are not able to distinguish which test is logging the message.
- backported by
-
JDK-8357235 Incomplete logging in nsk/jvmti/ResourceExhausted/resexhausted00* tests
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- links to
-
Commit(master)
openjdk/jdk17u-dev/613778a0
-
Commit(master)
openjdk/jdk21u-dev/861d3ec1
-
Commit(master)
openjdk/jdk/33f9be8d
-
Review(master)
openjdk/jdk17u-dev/3597
-
Review(master)
openjdk/jdk21u-dev/1817
-
Review(master)
openjdk/jdk/22939