-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Failing test - System.Threading.ThreadPools.Tests.ThreadPoolTests.ThreadPoolMinMaxThreadsEventTest
on Linux/arm64
#95873
Comments
Tagging subscribers to this area: @mangod9 Issue DetailsBuild InformationBuild: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=495334 Error MessageFill the error message using step by step known issues guidance. {
"ErrorMessage": "Exit code was 134 but it should have been 42",
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
} Similar to #85960 ?
|
Yes, seems to include the same pattern as seen in #85960, so terminating runtime with an exit and since that doesn't wait for managed threads to complete, we still have managed threads calling into EventPipe while cleaning up EventPipe artifacts and that leads to this assert or potential an AV. |
Failing again on #98234
|
Closing since this hasn't reproed for a few months. |
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=495334
Build error leg or test failing: System.Threading.ThreadPools.Tests.ThreadPoolTests.ThreadPoolMinMaxThreadsEventTest
Pull request: #95819
Error Message
Fill the error message using step by step known issues guidance.
Similar to #85960 ?
cc @lateralusX @lambdageek
Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=495334
Error message validated:
Exit code was 134 but it should have been 42
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 12/11/2023 6:41:24 PM UTC
Report
Summary
The text was updated successfully, but these errors were encountered: