JDK-8032850 : [TESTBUG] Race condition in test runtime/threads/IntSleep still exists
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 7,8
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2012-05-22
  • Updated: 2024-04-16
  • Resolved: 2014-02-06
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
9Fixed
Related Reports
Relates :  
JDK-6546236 - Thread interrupt() of Thread.sleep() can be lost on Solaris due to race with signal handler
Description
Test runtime/threads/IntSleep still timesout due to the same issue described in CR 6921060. 
With big timeout inserted before interrupt calls test passed.
I was able to reproduce issue only on some Windows hosts (stt-39,stt-67.ru.oracle.com).
Test uses synchronization based on thread state. That way is error-prone.
Synchronization algorithm for this test should be adjusted to avoid such hangs.

Log example:
http://vice.russia.sun.com/results/1.6.0_33/b03/vm/win2008-x64-64_vm.runtime.testlist/ResultDir/IntSleep/IntSleep.log
Comments
Is this test actually useful? This seems like something that the JCK covers.
27-01-2014