JDK-8263725 : JFR oldobject tests are not run when GCs are specified explicitly
- Type: Enhancement
- Component: hotspot
- Sub-Component: jfr
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2021-03-17
- Updated: 2024-11-12
- Resolved: 2021-03-18
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 17 |
|---|
17 b15Fixed  |
Related Reports
|
Relates :
|
Description
The tests are tagged with @requires == "null", which has the effect that if you run with GC explicitly set, like: make -C ../build/fastdebug test TEST=test/jdk/jdk/jfr/event/oldobject/TestZ.java JTREG="JAVA_OPTIONS=-XX:+UseG1GC" then the tests won't run. The intention has probably been to only run the test with the default GC. I propose that we remove this and run the tests with other GCs as well.
Comments
|