JDK-8250546 : Expect changed behaviour reported in JDK-8249846
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util.concurrent
  • Affected Version: openjdk8u265,openjdk8u272
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2020-07-24
  • Updated: 2020-07-29
  • Resolved: 2020-07-24
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.
Other
openjdk8u265 b01Fixed
Related Reports
Relates :  
JDK-8249846 - Change of behavior after JDK-8237117: Better ForkJoinPool behavior
Relates :  
JDK-8249677 - Regression in 8u after JDK-8237117: Better ForkJoinPool behavior
Description
As described in JDK-8249846, the behaviour of ForkJoinPool worker threads changed in OpenJDK 8u262.

The test added to resolve JDK-8249677 checks the behaviour and fails if it detects current 8u262 behaviour. Until there is a fix for JDK-8249846 (if there ever is), we should expect the current behaviour instead and pass the test.
Comments
URL: https://hg.openjdk.java.net/jdk8u/jdk8u/jdk/rev/323008dfe93e User: andrew Date: 2020-07-24 21:55:41 +0000
24-07-2020
Fix request (8u) I'd like to have this fix in 8u. The test introduced by 8249677 to 8u does not reflect the current expected behaviour, so it's mistakenly failing. Risk is minimal as only a test case is affected by this change. Review: https://mail.openjdk.java.net/pipermail/jdk8u-dev/2020-July/012271.html
24-07-2020