Bug ID: JDK-8172015 ConcurrentQueues/OfferRemoveLoops.java fails

Type: Bug
Component: core-libs
Sub-Component: java.util.concurrent
Affected Version: 9

Priority: P4
Status: Resolved
Resolution: Cannot Reproduce

Submitted: 2016-12-26
Updated: 2024-04-03
Resolved: 2024-04-03

After merging the latest Hotspot changes and Dev java/util/concurrent/ConcurrentQueues/OfferRemoveLoops.java started failing (on all platforms):

----------messages:(4/142)----------
command: main OfferRemoveLoops 300
reason: User specified action: run main OfferRemoveLoops 300 
Mode: othervm
elapsed time (seconds): 51.895
----------configuration:(0/0)----------
----------System.out:(3/30)----------
Passed = 983672, failed = 1

----------System.err:(24/1061)----------
LinkedBlockingQueue
LinkedBlockingQueue
LinkedBlockingDeque
LinkedBlockingDeque
ArrayBlockingQueue
PriorityBlockingQueue
ConcurrentLinkedDeque
ConcurrentLinkedQueue
Hung thread: remover
LinkedTransferQueue
java.lang.AssertionError: Some tests failed
	at OfferRemoveLoops.instanceMain(OfferRemoveLoops.java:187)
	at OfferRemoveLoops.main(OfferRemoveLoops.java:183)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:538)
	at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:110)
	at java.base/java.lang.Thread.run(Thread.java:844)

JavaTest Message: Test threw exception: java.lang.AssertionError: Some tests failed
JavaTest Message: shutting down test

STATUS:Failed.`main' threw exception: java.lang.AssertionError: Some tests failed

We can't reproduce this failure.
19-02-2017
Such a failure has not been observed on mach5 indicating this is not urgent (so downgrading to P4), nor can i reproduce locally with the "exotic" HotSpot flags, but such failures are still occurring in our system running with those "exotic" flags. This needs some focused effort to run the test repeatedly on an identified machine to sufficiently reproduce, then point a HotSpot engineer at it to debug.
02-02-2017
All we have is: Hung thread: remover which basically indicates a timeout - the remover thread had not terminated by the time the main thread was done waiting for completion. But there is no stack dump for the hung thread if (thread.isAlive()) { System.err.printf("Hung thread: %s%n", thread.getName()); failed++; for (StackTraceElement e : thread.getStackTrace()) System.err.println(e); thread.interrupt(); } How can that be? The test execution parameters were: -Xcomp -Xcomp -XX:MaxRAMFraction=8 -XX:+CreateCoredumpOnCrash -ea -esa -XX:CompileThreshold=100 -XX:+UnlockExperimentalVMOptions -server -XX:-TieredCompilation -XX:+IgnoreUnrecognizedVMOptions -XX:+DeoptimizeALot which may suggest a compiler deopt issue.
26-12-2016
Testing team needs to do more work to isolate the problem, so assigning back to Dmitry.
26-12-2016
As typically happens, I cannot reproduce this failure (on linux-amd64). Perhaps it's actually a hotspot bug due to the recent integration? Please try harder to characterize the failures and bisect to the failing commit. One possibility is the recent AOT work, which my jdk isn't using (due to missing libelf).
26-12-2016