Details
-
Bug
-
Status: Resolved
-
P4
-
Resolution: Fixed
-
None
-
b03
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8292907 | 17.0.6-oracle | Thomas Schatzl | P4 | Resolved | Fixed | b01 |
JDK-8283108 | 17.0.4 | Goetz Lindenmaier | P4 | Resolved | Fixed | b01 |
Description
The invocation that runs with large pages are guarded with @requires vm.gc.G1 and doesn't explicitly state that G1 should be used.
This means two things:
1) We are not running the large pages subtest when other GCs are specified
2) Under some circumstances another GC is ergonomically selected and we run the test with that GC even though the test was guarded by @require vm.gc.G1.
I propose that we move the subtest to its own run section, without any requirement about the used GC.
This means two things:
1) We are not running the large pages subtest when other GCs are specified
2) Under some circumstances another GC is ergonomically selected and we run the test with that GC even though the test was guarded by @require vm.gc.G1.
I propose that we move the subtest to its own run section, without any requirement about the used GC.
Attachments
Issue Links
- backported by
-
JDK-8283108 TestSystemGC uses "require vm.gc.G1" for large pages subtest
-
- Resolved
-
-
JDK-8292907 TestSystemGC uses "require vm.gc.G1" for large pages subtest
-
- Resolved
-
- relates to
-
JDK-8276796 gc/TestSystemGC.java large pages subtest fails with ZGC
-
- Resolved
-
- links to
-
Commit openjdk/jdk17u-dev/16f75080
-
Commit openjdk/jdk/1a818154
-
Review openjdk/jdk17u-dev/238
-
Review openjdk/jdk/4538
(2 links to)