JDK-8142441 : Improve jtreg tests for java.util.concurrent
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util.concurrent
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2015-11-10
  • Updated: 2016-06-13
  • Resolved: 2015-11-26
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 9
9 b96Fixed
Related Reports
Duplicate :  
Description
jtreg tests can be improved:

- calls to sleep are occasionally necessary, but most should be eliminated.  They make the tests slow and flaky.
- exceptions thrown during execution should always cause test failure, which is not currently the case
- some tests were originally ported from micro-benchmarks.  Eliminate the "warmup" phase which is not sufficiently useful in a jtreg test.
- jtreg tests should never run more than about 1 second in normal execution mode.  A "stress test mode" is a fine thing to have, but the invoker of jtreg should opt-in, and there should be some kind of standard as to how such tests should be run (I'm not aware of any prior art on that).  It might be reasonable for a stress test to run until e.g. half of its allotted time is used up.
Comments
part of the great jsr166 jdk9 integration
11-11-2015