-
Notifications
You must be signed in to change notification settings - Fork 399
Report actual exception when reporting ThreadErrors #4961
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
👋 Hey @p-datadog, please fill "Change log entry" section in the pull request description. If changes need to be present in CHANGELOG.md you can state it this way **Change log entry**
Yes. A brief summary to be placed into the CHANGELOG.md(possible answers Yes/Yep/Yeah) Or you can opt out like that **Change log entry**
None.(possible answers No/Nope/None) Visited at: 2025-10-08 15:03:17 UTC |
Typing analysisIgnored filesThere are 539 ignored files in the Steepfile out of 836. Ignored filesNote: Ignored files are excluded from the next sections.
|
|
✅ Tests 🎉 All green!❄️ No new flaky tests detected 🎯 Code Coverage 🔗 Commit SHA: 537cf0d | Docs | Was this helpful? Give us feedback! |
|
Thanks for fixing that! |
BenchmarksBenchmark execution time: 2025-10-08 15:33:06 Comparing candidate commit 537cf0d in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 44 metrics, 2 unstable metrics. |
Co-authored-by: Oleg Pudeyev <[email protected]>
What does this PR do?
Reports actual exception when reporting "deadlock" during configuration processing.
Motivation:
In the investigation that led to the fix in #4957, we discovered that the error was mutex not locked and not a deadlock. This could have been surfaced by the message directly, potentially leading to the issue being fixed sooner and saving us some aggravation due to flaky CI.
Change log entry
Additional Notes:
How to test the change?
Existing tests