-
Bug
-
Resolution: Fixed
-
P3
-
9
-
b138
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8347559 | 8u451 | Shivangi Gupta | P3 | Resolved | Fixed | b02 |
java/util/concurrent/ThreadPoolExecutor/CoreThreadTimeOut.java has 2 wrong assumptions:
1) test assumes that 10 tested threads won't finish in 30 milliseconds
2) test assumes that 10 tested threads will finish in 10 seconds
both assumptions are hw- and system- specific. Depending on system load and hw capabilities these time metrics might be wrong. Test needs to be re-organized to not rely on hardcoded timeouts.
1) test assumes that 10 tested threads won't finish in 30 milliseconds
2) test assumes that 10 tested threads will finish in 10 seconds
both assumptions are hw- and system- specific. Depending on system load and hw capabilities these time metrics might be wrong. Test needs to be re-organized to not rely on hardcoded timeouts.
- backported by
-
JDK-8347559 [testbug] CoreThreadTimeOut still uses hardcoded timeout
-
- Resolved
-