fix: Reduce Java 25 nightly stream test flakiness#2728
Merged
pjfanning merged 1 commit intoapache:mainfrom Mar 15, 2026
Merged
Conversation
Motivation: JDK 25 ForkJoinPool scheduling changes cause nightly CI stream tests to fail with timeouts — ~100+ failures per night. Modifications: - Increase timefactor from 2 to 3 for JDK 25+ in nightly CI workflow - Add 30s PatienceConfig to FlowFlatMapConcatParallelismSpec (100K elements) - Add 30s PatienceConfig to HubSpec (20K element long-stream tests) - Increase MapAsyncPartitionedSpec patience from 5s to 15s - Increase AggregateWithBoundarySpec Await timeouts from 10s to 30s Result: Timing-sensitive stream tests have sufficient timeout headroom on JDK 25, reducing false failures in nightly CI. References: apache#2573 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
JDK 25 introduced changes to
ForkJoinPoolscheduling behavior that cause ~100+ stream test failures per nightly CI run. The most affected tests are high-throughput stream tests (FlowFlatMapConcatParallelismSpec,HubSpec,MapAsyncPartitionedSpec,AggregateWithBoundarySpec) that have timing-sensitive assertions.Modification
.github/workflows/nightly-builds.yml): Addedtimefactor=3for JDK 25+ builds, scaling alldilatedtimeouts across the entire test suiteFlowFlatMapConcatParallelismSpec: Added explicitPatienceConfig(30.seconds)for high-element-count tests (100K elements)HubSpec: Added explicitPatienceConfig(30.seconds)for 20K+ element throughput testsMapAsyncPartitionedSpec: Increased patience from 5s to 15s (3x, matching timefactor)AggregateWithBoundarySpec: IncreasedAwait.resulttimeouts from 10s to 30s (3x)Result
timefactor=3in nightly CI provides a safety net for tests without explicit overridesReferences