-
Bug
-
Resolution: Fixed
-
P4
-
9
-
b167
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8179814 | 10 | Amy Lu | P4 | Resolved | Fixed | b07 |
This is follow up work of JDK-8169838 and JDK-8169903
For SpliteratorTraversingAndSplittingTest
Paul Sandoz wrote:
> We should be careful adding Integer.MAX_VALUE tests for BitStream as the can consume lots of memory.
>
> My suggestion is not to add them to this test and instead consider, as a follow on issue, moving spliterator testing of BitSet to BitSetStreamTest, where we can better control large memory consuming cases.
For SpliteratorTraversingAndSplittingTest
Paul Sandoz wrote:
> We should be careful adding Integer.MAX_VALUE tests for BitStream as the can consume lots of memory.
>
> My suggestion is not to add them to this test and instead consider, as a follow on issue, moving spliterator testing of BitSet to BitSetStreamTest, where we can better control large memory consuming cases.
- backported by
-
JDK-8179814 Move spliterator testing of BitSet into big memory tests BitSetStreamTest
-
- Resolved
-
- relates to
-
-
- Resolved
-
-
-
- Closed
-
-
-
- Open
-
-
-
- Resolved
-