-
Notifications
You must be signed in to change notification settings - Fork 171
8208655: use JTreg skipped status in hotspot tests #387
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
01138ee
1b07e7a
1c3809a
1cb58a5
823b2a3
dee3121
313e367
ecf9eba
2608b80
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -30,6 +30,7 @@ | |
| * @bug 8000754 | ||
| * @summary Tests that a MemoryPoolMXBeans is created for metaspace and that a | ||
| * MemoryManagerMXBean is created. | ||
| * @requires vm.bits == 64 | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why? We have metaspace also on 32-bit, just no class space. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This and the other test you commented on are https://bugs.openjdk.org/browse/JDK-8213410 Both of the other tests have this restriction up to trunk as well. I think the history comes from adding I did look at backporting JDK-8204167 as well, but I don't see any issue with backporting the whole patch, given the exclusions are also there in 11+. If there is a case for running these on 32-bit, the restriction should probably be dropped in trunk and backported down for consistency. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Okay, that makes sense. Thanks for clarifying. I looked at test/hotspot/jtreg/gc/metaspace/TestMetaspaceMemoryPool.java more closely. That test could be run for 32-bit as well, but its not worth fixing. |
||
| * @library /testlibrary | ||
| * @run main/othervm -XX:+IgnoreUnrecognizedVMOptions -XX:-UseCompressedOops TestMetaspaceMemoryPool | ||
| * @run main/othervm -XX:+IgnoreUnrecognizedVMOptions -XX:-UseCompressedOops -XX:MaxMetaspaceSize=60m TestMetaspaceMemoryPool | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure about this. The flag itself exists also on 32-bit, so the test should work there; it is pointless though since the flag is never used.