-
Bug
-
Resolution: Fixed
-
P3
-
9, 11, 15, 16
-
b09
-
generic
-
generic
Stress tests nsk/stress/stack have TEST_TIMEOUT_MEANS=PASS in cfg file. This is bad because we don't detect hangs (possibly product problems) and when they do hang, execution time is wasted.
Some of tests do hang in promotion testing (but pass):
nsk/stress/stack/stack017
nsk/stress/stack/stack008
nsk/stress/stack/stack018
nsk/stress/stack/stack019
Several things need to be done:
- TEST_TIMEOUT_MEANS=PASS removed
- Investigate why hangs happen. Fix tests if it is test bug, file product bug if it is product bug.
- Investigate if it is possible to reduce test execution time (or limit it with STRESS_OPTIONS).
This is actually similiar to
Some of tests do hang in promotion testing (but pass):
nsk/stress/stack/stack017
nsk/stress/stack/stack008
nsk/stress/stack/stack018
nsk/stress/stack/stack019
Several things need to be done:
- TEST_TIMEOUT_MEANS=PASS removed
- Investigate why hangs happen. Fix tests if it is test bug, file product bug if it is product bug.
- Investigate if it is possible to reduce test execution time (or limit it with STRESS_OPTIONS).
This is actually similiar to
- relates to
-
JDK-8251490 [TESTBUG] The Java thread stack size specified is too small for nsk/stress/stack. Specify at least 448k
- Resolved
-
JDK-8208236 [TESTBUG] vmTestbase/nsk/stress/stack tests fail by timeout
- Resolved
-
JDK-8284980 Test vmTestbase/nsk/stress/except/except010.java times out with -Xcomp -XX:+DeoptimizeALot
- Resolved