Dump forked-process threads on log-injection smoke-test timeout#11930
Draft
bm1549 wants to merge 1 commit into
Draft
Dump forked-process threads on log-injection smoke-test timeout#11930bm1549 wants to merge 1 commit into
bm1549 wants to merge 1 commit into
Conversation
bm1549
added a commit
that referenced
this pull request
Jul 13, 2026
DO NOT MERGE — temporary. Adds test_loginjection_openj9_repro (amd64 semeru8/11/17) and _arm64 (semeru11/17) jobs that build once then loop the log-injection smoke test (whose only feature method is "check raw file injection") 20x per JVM to force the traceCount=0 startup hang and capture the reinstated forked-process thread dump into the loop-output/ artifact. Delete before marking PR #11930 ready. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Contributor
|
🎯 Code Coverage (details) 🔗 Commit SHA: 5f34d40 | Docs | Datadog PR Page | Give us feedback! |
Contributor
🟢 Java Benchmark SLOs — All performance SLOs passed
PR vs. master results
Commit: Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion. |
0c59c6a to
ad11c19
Compare
On the "check raw file injection" 30s timeout, jstack the forked process so the OpenJ9/Semeru startup hang (traceCount=0, process never exits) can be diagnosed instead of a bare "Condition not satisfied". Reinstates the diagnostic from #11400 (removed in #11548), now much smaller, and distinguishes an early process exit from a genuine hang. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ad11c19 to
5f34d40
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
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.
What Does This Do
On the
"check raw file injection"smoke-test 30s timeout, jstack the forked process and attach the dump to the failure — so the OpenJ9/Semeru hang can be diagnosed instead of a bare "Condition not satisfied". Also distinguishes an early process exit from a genuine hang. Reinstates (a much smaller version of) the diagnostic from #11400, removed in #11548.Motivation
The test times out with
traceCount=0and the forked process never exiting — a startup hang, only on IBM Semeru / OpenJ9. #11509 fixed the earlierDDTraceIdclinit deadlock; this resurfaced after Semeru jobs began running on master/MQ (#11788, #11832). It couldn't be reproduced by brute force (~12k startups), so capture a thread dump when it next hangs on master/MQ.Additional Notes
Runs only on the failure path. Follow-up (separate PR):
@Flaky'sisIbm8()readsjava.vm.vendor="Eclipse OpenJ9", so it never matches Semeru — should beisJ9().Jira ticket: N/A
🤖 Generated with Claude Code