-
Enhancement
-
Resolution: Fixed
-
P4
-
8, 11, 17, 18
-
b13
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8274710 | 17.0.2 | Aleksey Shipilev | P4 | Resolved | Fixed | b01 |
JDK-8274763 | 11.0.14 | Aleksey Shipilev | P4 | Resolved | Fixed | b01 |
Currently, the java/lang/invoke/LFCaching stress tests are running in tier1. They run for TIMEOUT*0.9 seconds, which currently means they execute for about 216 seconds. It makes the java/lang/invoke/LFCaching/LFSingleThreadCachingTest.java the longest test in the entire tier1 run.
It is understandable to tie the run time of the test to the test timeout when the test is waiting for something, so other parallel tests can enjoy free resources to run. Having the multi-minute active stress test is less useful. Moreover, if default timeout ever increases, the test would suddenly run for even longer.
I propose we cut the run time for these tests from the test timeout, and set it to a more reasonable 1 minute. Since tier1 tests run frequently, we would still have a lot of coverage across multiple tier1 runs.
It is understandable to tie the run time of the test to the test timeout when the test is waiting for something, so other parallel tests can enjoy free resources to run. Having the multi-minute active stress test is less useful. Moreover, if default timeout ever increases, the test would suddenly run for even longer.
I propose we cut the run time for these tests from the test timeout, and set it to a more reasonable 1 minute. Since tier1 tests run frequently, we would still have a lot of coverage across multiple tier1 runs.
- backported by
-
JDK-8274710 Limit run time for java/lang/invoke/LFCaching tests
- Resolved
-
JDK-8274763 Limit run time for java/lang/invoke/LFCaching tests
- Resolved
- links to
-
Commit openjdk/jdk11u-dev/a2bd0a93
-
Commit openjdk/jdk17u/1e9126a6
-
Commit openjdk/jdk/a3308af0
-
Review openjdk/jdk11u-dev/454
-
Review openjdk/jdk17u/127
-
Review openjdk/jdk/5214
(3 links to)