-
Task
-
Resolution: Fixed
-
P3
-
8, 9
-
b104
This task is suggested from Paul Sandoz:
Integrating the JSR166 TCK tests into the JDK test area is valuable.
The JSR 166 area is too important to leave code coverage exposed in our main developer and test processes. They should really be part of the JDK core tier tests (probably tier 1). In addition any such tests in the JDK may evolve faster and be more visible that the tests in the JCK (evolve as fast as other 166 artefacts).
Joe Darcy suggested that for this case, the master copy of the concurrency conformance tests would live in the jdk repo and from there it would get synced into the JCK occasionally.
Integrating the JSR166 TCK tests into the JDK test area is valuable.
The JSR 166 area is too important to leave code coverage exposed in our main developer and test processes. They should really be part of the JDK core tier tests (probably tier 1). In addition any such tests in the JDK may evolve faster and be more visible that the tests in the JCK (evolve as fast as other 166 artefacts).
Joe Darcy suggested that for this case, the master copy of the concurrency conformance tests would live in the jdk repo and from there it would get synced into the JCK occasionally.
- relates to
-
JDK-8148638 test failure in test/java/util/concurrent/tck
- Closed