JDK-8148928 : java/util/stream/test/**/SequentialOpTest.java timed out intermittently
  • Type: Bug
  • Component: core-libs
  • Sub-Component: java.util.stream
  • Affected Version: 8,9
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2016-02-03
  • Updated: 2019-09-04
  • Resolved: 2016-02-05
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.
JDK 8 JDK 9 Other
8u212Fixed 9 b105Fixed openjdk8u212Fixed
Related Reports
Relates :  
JDK-8076458 - java/util/stream/test/org/openjdk/tests/java/util/stream/FlatMapOpTest.java timeout
Description
java/util/stream/test/org/openjdk/tests/java/util/stream/SequentialOpTest.java

Observed this test timed out intermittently, with high frequently. Please note that this is tier1 test !

From log:
Error. Program `/scratch/jenkins/workspace/9-dev-tier1-solaris-sparc/build/jdk/bin/java' timed out\!

Similar issue also happened to some other *OpTest, and one of them has been fixed in JDK-8076458. It seems that same DataProvider is used in both test and might run into same issue.
Comments
Fix Request This patch should be backported to make 8u tests pass cleanly, along with JDK-8076458. Patch applies to 8u with reshuffling after JDK-8044047 and JDK-8076458 backports and passes java/util tests.
27-02-2019
RFR: 8148928: java/util/stream/test/**/SequentialOpTest.java timed out intermittently http://mail.openjdk.java.net/pipermail/core-libs-dev/2016-February/038605.html
04-02-2016
Root Cause: as amy pointed out, this should be due similar cause as JDK-8076458: the test data set is too big, it takes too long time to finish on busy system, it's understandable. And, similar call stacks can be caught by using jstack on a successfully finished test. This should not be the similar issue as JDK-8077392 which is block on a wait, but this one is running at Unsafe.unpark(..) Suggested solution: use mini data set for test SequentialOpTest.testMixedSeqPar(...). before fix, 85.839 seconds, after fix, 8.764 seconds
04-02-2016