JDK-6765623 : [TESTBUG] closed/runtime/4860981/Test.java does not deal with spurious wakeups
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: hs14
  • Priority: P4
  • Status: Resolved
  • Resolution: Duplicate
  • OS: solaris
  • CPU: generic
  • Submitted: 2008-10-30
  • Updated: 2023-08-04
  • 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
9Resolved
Related Reports
Duplicate :  
JDK-8032988 - [TESTBUG] Nightly testing cleanup: remove obsolete and nonfunctioning jtreg runtime tests from closed repo
Relates :  
JDK-6691507 - test hs/runtime/4860981 failed sometimes on Solaris 9
Description
closed/runtime/4860981/Test.java expects that Object.wait(30000) will stop thread execution for at least 30000 milliseconds if no notifications are sent. However this is not guaranteed and should not be expected
Comments
I concur. The test as it stands today is bogus as Object.wait does allow spurious wakeups (though it took us far too long to get that into the spec). I must confess I have no idea why the test does the Process exec/waitfor/destroy. It is also a Solaris only test.
31-07-2013
We should just remove this test from hs25.
30-07-2013