JDK-6829636 : test/java/util/logging/LoggingDeadlock2.java is flaky
- Type: Bug
- Component: core-libs
- Sub-Component: java.util.logging
- Affected Version: 7
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2009-04-13
- Updated: 2010-05-11
- Resolved: 2009-06-22
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.
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 7 | Other |
|---|---|
7 b62Fixed  |
OpenJDK6Resolved |
Related Reports
|
Relates :
|
Description
The reg test java/util/logging/LoggingDeadlock2.java has been failing intermittently for quite a while, at least since jdk7-b44. It calls System.exit, which a jtreg test is not allowed to do (at least not directly; it must run the test in a subprocess). jtreg notices this if the timing is just right.
Comments
|