-
Bug
-
Resolution: Fixed
-
P4
-
9
-
b158
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8175746 | 10 | Amy Lu | P4 | Resolved | Fixed | b02 |
The test java/util/Spliterator/SpliteratorTraversingAndSplittingTest.java contains a large number of test cases that leverage some general spliterator testing methods.
Those methods are also duplicated in:
java/util/Spliterator/SpliteratorCollisions.java
java/util/stream/SpliteratorTestHelper.java
Those methods could be refactored into a separate library for reuse.
Such testing is required for BitSet for large memory configurations when the Integer.MAX_VALUE bit is set. If such cases are included in the SpliteratorTraversingAndSplittingTest.java test it can induce out of memory errors (seeJDK-8169838)
Those methods are also duplicated in:
java/util/Spliterator/SpliteratorCollisions.java
java/util/stream/SpliteratorTestHelper.java
Those methods could be refactored into a separate library for reuse.
Such testing is required for BitSet for large memory configurations when the Integer.MAX_VALUE bit is set. If such cases are included in the SpliteratorTraversingAndSplittingTest.java test it can induce out of memory errors (see
- backported by
-
JDK-8175746 Refactor spliterator traversing tests into a library
-
- Resolved
-
- relates to
-
JDK-8174171 Move spliterator testing of BitSet into big memory tests BitSetStreamTest
-
- Resolved
-
-
JDK-8169838 java/util/Spliterator/SpliteratorTraversingAndSplittingTest.java failed intermittently
-
- Closed
-