fix: stabilise JDK 25 nightly flakes#2907
Merged
He-Pin merged 1 commit intoapache:mainfrom Apr 25, 2026
Merged
Conversation
337470d to
58391d3
Compare
Member
Author
|
@pjfanning I will take another run about this |
58391d3 to
9631107
Compare
Roiocam
approved these changes
Apr 25, 2026
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
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:
The JDK 25 nightly workflow run 24922457328 failed only in the JDK 25 matrix. The failures were timeout-shaped: stream TCK subscription/sequential-signal stalls, remote system-message/send-consistency timeouts, BoundedSourceQueue burst delivery, and DurableStateBehaviorStashOverflowSpec draining 20k messages. The existing minimum-runnable=4 mitigation was not enough on the GitHub runners.
References:
Modification:
Result:
The production reference configuration remains unchanged; virtual threads are enabled only by nightly workflow parameters. The selected fork-join dispatchers retain their own scheduler isolation instead of routing through the JVM-wide default virtual-thread scheduler. This targets the CI-only JDK 25 starvation symptoms while preserving local and PR-test defaults.
Tests: