Issue #14904 - Stabilize virtual thread tracking dump test - #15647
Open
DragonFSKY wants to merge 1 commit into
Open
Issue #14904 - Stabilize virtual thread tracking dump test#15647DragonFSKY wants to merge 1 commit into
DragonFSKY wants to merge 1 commit into
Conversation
DragonFSKY
force-pushed
the
fix-14904-tracking-dump
branch
4 times, most recently
from
August 26, 2026 01:44
4e4576d to
0f02b5e
Compare
DragonFSKY
force-pushed
the
fix-14904-tracking-dump
branch
from
September 3, 2026 03:03
37d34b0 to
e2ff8d7
Compare
Signed-off-by: Dongliang Xie <dragonfsky@gmail.com>
DragonFSKY
force-pushed
the
fix-14904-tracking-dump
branch
from
September 3, 2026 03:41
e2ff8d7 to
b5c2784
Compare
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.
Fixes #14904.
testTrackingDump()signaled task startup before the blocking virtual thread necessarily reachedWAITING, and its 10-second timeout allowed tracked tasks to finish before both dumps completed.Use one blocking task and one spinning task. Wait for the blocking task to reach
WAITINGbefore starting the spinner, and keep both alive until both dumps are complete. This preserves the assertions for waiting and runnable states, carrier information, and detailed stack frames without assuming multiple scheduler carriers.Tests:
VirtualThreadPoolTest#testTrackingDumpVirtualThreadPoolTest#testTrackingDumpwith-Djdk.virtualThreadScheduler.parallelism=1jetty-utiltest suite (2963 tests, 0 failures, 0 errors)AI disclosure
I used OpenAI GPT-5.6 and Kimi K3 to assist with issue analysis and drafting the implementation and tests. I reviewed and verified the final changes.