JDK-8192646 : com/sun/jdi/SuspendThreadTest.java fails with timeout
  • Type: Bug
  • Component: core-svc
  • Sub-Component: debugger
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2017-11-29
  • Updated: 2017-12-08
  • Resolved: 2017-11-30
Related Reports
Duplicate :  
Description
Error occurred during test com/sun/jdi/SuspendThreadTest.java result processing - skipped, {}
java.lang.IllegalArgumentException: Unexpected line: 'Timeout signalled after 1,200 seconds'
	at com.oracle.java.trixie.parser.Jtreg$JtregTestResultExtractor.toMapEntry(Jtreg.java:667)
	at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
	at java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948)
	at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
	at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
	at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
	at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
	at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
	at com.oracle.java.trixie.parser.Jtreg$JtregTestResultExtractor.toMap(Jtreg.java:692)
	at com.oracle.java.trixie.parser.Jtreg$JtregTestResultExtractor.extractResult(Jtreg.java:510)
	at com.oracle.java.trixie.parser.Jtreg$JtregTestResultExtractor.extract(Jtreg.java:455)
	at com.oracle.java.trixie.parser.Jtreg$JtregTestResultExtractor.extract(Jtreg.java:440)
	at com.oracle.java.trixie.parser.Jtreg.addTestResult(Jtreg.java:133)
	at com.oracle.java.trixie.parser.Jtreg.readTestCasesFromSummary(Jtreg.java:220)
	at com.oracle.java.trixie.parser.Jtreg.readTestCases(Jtreg.java:276)
	at com.oracle.java.trixie.parser.Jtreg.readTestResults(Jtreg.java:386)
	at com.oracle.java.trixie.parser.Harness.doAnalysis(Harness.java:166)
	at com.oracle.java.trixie.parser.Parser.parse(Parser.java:73)
	at com.oracle.java.trixie.reporter.Main.execute(Main.java:91)
	at com.oracle.java.trixie.reporter.Main.executeCmd(Main.java:72)
	at com.oracle.java.sparky.executor.SparkyExecutorBase.reportResultsByTrixie(SparkyExecutorBase.java:485)
	at com.oracle.java.sparky.executor.SparkyExecutorBase.uploadResultsByTrixie(SparkyExecutorBase.java:539)
	at com.oracle.java.sparky.executor.jdktester.JdkJibTester.postExecution(JdkJibTester.java:108)
	at com.oracle.java.sparky.executor.SparkyExecutorRunner.run(SparkyExecutorRunner.java:109)
	at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1626)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

Comments
Interesting. So this test did fail, but and mach5 sort of seems to know that because it says the test task failed. Yet is says all tests passed, and this test shows up in neither the failed or the passed test list. So I downloaded the artifacts via one of the passing tests, and there was an hs_err file for this test. It contained: # assert(counter_changed) failed: failed dependencies, but counter didn't change So this is a known issue that was fixed by JDK-8191688. I'll close as a dup of that CR.
30-11-2017

I reran 50 times with the same binary used for PIT testing and it failed about 80% of the time, including runs on windows-x64 (in addition to linux-x64-debug). When I tested earlier, it was with the latest sources. I'll try again with a recent nightly.
30-11-2017

I ran open/test/jdk/:jdk_jdi 50 times on the failing platforms with the vm options that reproduced this failure and could not reproduce it myself.
29-11-2017