- VM options specified in a test might conflict with given by tested
- test might be OS specific
- test might require some extra resources (memory/permissions/whatever)
- test might be applicable in a certain profile.
There should be a mechanism that allows to identify not applicable tests.
Possible solution:
- some tests might declare what kind of resources they require
- jtreg before test execution pre-calculates the environment
- before a particular test execution jtreg checks if all required resources are available
- tests not being run due to resouces are be reported separately (not as passed, not as failed)
- blocks
-
JDK-8019361 [TESTBUG] Conflicting collector combinations in option list for GC tests
-
- Resolved
-
-
JDK-8042051 gc/g1/TestHumongousShrinkHeap.java: Conflicting collector combinations in option list
-
- Closed
-
-
JDK-8042265 GC flags shouldn't be passed to compiler/regalloc/C1ObjectSpillInLogicOp.java
-
- Closed
-
- duplicates
-
JDK-8044318 test applicability tool
-
- Closed
-
-
CODETOOLS-7900913 new @requires tag
-
- Resolved
-
- relates to
-
JDK-8027595 Enable BigInteger overflow tests in JTREG
-
- Closed
-
-
JDK-8042983 test/java/math/BigInteger/ExtremeShiftingTests.java needs too much heap
-
- Closed
-