-
Bug
-
Resolution: Fixed
-
P5
-
7, 7u6
-
b27
-
generic, arm
-
generic, linux
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8018794 | 7u45 | Gary Adams | P5 | Closed | Fixed | b01 |
JDK-8007975 | 7u40 | Gary Adams | P5 | Closed | Fixed | b14 |
JDK-8010594 | 7u25 | Gary Adams | P5 | Closed | Fixed | b03 |
JDK-8008872 | 7u21 | Gary Adams | P5 | Closed | Fixed | b02 |
Line 89 of
java/util/concurrent/locks/Lock/FlakyMutex.java
reads
check(es.awaitTermination(10, TimeUnit.SECONDS));
It turns out that on very slow machines with fastdebug builds this timeout is insufficient.
For instance, vm-v100-01.sfbay is a single CPU 650 MHz sparc. If I compile the test standalone and run it, I get this:
sd208054@vm-v100-01:~ $ /java/re/jdk/7/promoted/all/b32/binaries/solaris-sparcv9/fastdebug/bin/java -d64 FlakyMutex
java.lang.Exception: Stack trace
at java.lang.Thread.dumpStack(Thread.java:1310)
at FlakyMutex.fail(FlakyMutex.java:138)
at FlakyMutex.check(FlakyMutex.java:141)
at FlakyMutex.realMain(FlakyMutex.java:89)
at FlakyMutex.main(FlakyMutex.java:146)
Passed = 75464, failed = 1
Exception in thread "main" java.lang.AssertionError: Some tests failed
at FlakyMutex.main(FlakyMutex.java:148)
Doubling the timeout fixes the issue, at least for a machine this slow.
java/util/concurrent/locks/Lock/FlakyMutex.java
reads
check(es.awaitTermination(10, TimeUnit.SECONDS));
It turns out that on very slow machines with fastdebug builds this timeout is insufficient.
For instance, vm-v100-01.sfbay is a single CPU 650 MHz sparc. If I compile the test standalone and run it, I get this:
sd208054@vm-v100-01:~ $ /java/re/jdk/7/promoted/all/b32/binaries/solaris-sparcv9/fastdebug/bin/java -d64 FlakyMutex
java.lang.Exception: Stack trace
at java.lang.Thread.dumpStack(Thread.java:1310)
at FlakyMutex.fail(FlakyMutex.java:138)
at FlakyMutex.check(FlakyMutex.java:141)
at FlakyMutex.realMain(FlakyMutex.java:89)
at FlakyMutex.main(FlakyMutex.java:146)
Passed = 75464, failed = 1
Exception in thread "main" java.lang.AssertionError: Some tests failed
at FlakyMutex.main(FlakyMutex.java:148)
Doubling the timeout fixes the issue, at least for a machine this slow.
- backported by
-
JDK-8007975 TEST_BUG: Timeout value in java/util/concurrent/locks/Lock/FlakyMutex.java is insufficient
-
- Closed
-
-
JDK-8008872 TEST_BUG: Timeout value in java/util/concurrent/locks/Lock/FlakyMutex.java is insufficient
-
- Closed
-
-
JDK-8010594 TEST_BUG: Timeout value in java/util/concurrent/locks/Lock/FlakyMutex.java is insufficient
-
- Closed
-
-
JDK-8018794 TEST_BUG: Timeout value in java/util/concurrent/locks/Lock/FlakyMutex.java is insufficient
-
- Closed
-
- relates to
-
JDK-6712206 java/util/concurrent tests fail in Xcomp with assertion in HS13b02
-
- Closed
-