Bug: https://bugs.openjdk.java.net/browse/JDK-8133611
Webrev: http://cr.openjdk.java.net/~dholmes/8133611/webrev/
Patch inline below.
Now the hotspot fix is in place the test can be removed from the problem
list and need not be marked "intermittent".
Thanks,
David
-----
--- old/test/ProblemList.txt 2015-09-09 00:34:56.091794570 -0400
+++ new/test/ProblemList.txt 2015-09-09 00:34:54.719717019 -0400
@@ -363,10 +363,6 @@
# 8062512
java/util/spi/ResourceBundleControlProvider/UserDefaultControlTest.java
generic-all
-# 8029453
-java/util/concurrent/locks/ReentrantLock/TimeoutLockLoops.java linux-all
-
-
############################################################################
# jdk_instrument
---
old/test/java/util/concurrent/locks/ReentrantLock/TimeoutLockLoops.java
2015-09-09 00:35:00.104021348 -0400
+++
new/test/java/util/concurrent/locks/ReentrantLock/TimeoutLockLoops.java
2015-09-09 00:34:58.715942891 -0400
@@ -35,7 +35,6 @@
* @test
* @bug 4486658 5031862
* @run main TimeoutLockLoops
- * @key intermittent
* @summary Checks for responsiveness of locks to timeouts.
* Runs under the assumption that ITERS computations require more than
* TIMEOUT msecs to complete, which seems to be a safe assumption for
