runtime
runtime copied to clipboard
dotnet
Failing test - `System.Threading.ThreadPools.Tests.ThreadPoolTests.ThreadPoolMinMaxThreadsEventTest` on Linux/arm64
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: https://github.com/dotnet/runtime/pull/95819
Error Message
Fill 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 https://github.com/dotnet/runtime/issues/85960 ? cc @lateralusX @lambdageek
Known issue validation
Build: :mag_right: 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: :white_check_mark: Known issue matched with the provided build.
Validation performed at: 12/11/2023 6:41:24 PM UTC
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 4 | 37 |
Tagging subscribers to this area: @mangod9 See info in area-owners.md if you want to be subscribed.
Issue Details
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: https://github.com/dotnet/runtime/pull/95819
Error Message
Fill 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 https://github.com/dotnet/runtime/issues/85960 ? cc @lateralusX @lambdageek
| Author: | radical |
|---|---|
| Assignees: | - |
| Labels: |
|
| Milestone: | - |
Yes, seems to include the same pattern as seen in https://github.com/dotnet/runtime/issues/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 https://github.com/dotnet/runtime/pull/98234 From log:
Exiting early due to double fault.
[Inferior 1 (process 41724) detached]
System.Threading.ThreadPools.Tests.ThreadPoolTests.ThreadPoolMinMaxThreadsEventTest [FAIL]
Microsoft.DotNet.RemoteExecutor.RemoteExecutionException : Exit code was 255 but it should have been 42
Stack Trace:
/_/src/Microsoft.DotNet.RemoteExecutor/src/RemoteInvokeHandle.cs(242,0): at Microsoft.DotNet.RemoteExecutor.RemoteInvokeHandle.Dispose(Boolean disposing)
/_/src/Microsoft.DotNet.RemoteExecutor/src/RemoteInvokeHandle.cs(55,0): at Microsoft.DotNet.RemoteExecutor.RemoteInvokeHandle.Dispose()
/_/src/libraries/System.Threading.ThreadPool/tests/ThreadPoolTests.cs(1118,0): at System.Threading.ThreadPools.Tests.ThreadPoolTests.ThreadPoolMinMaxThreadsEventTest()
/_/src/mono/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.Mono.cs(22,0): at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args)
/_/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.cs(57,0): at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr)
System.Threading.ThreadPools.Tests.ThreadPoolTests.MetricsTest [SKIP]
Condition(s) not met: "IsMetricsTestSupported"
Finished: System.Threading.ThreadPool.Tests
=== TEST EXECUTION SUMMARY ===
System.Threading.ThreadPool.Tests Total: 66, Errors: 0, Failed: 1, Skipped: 1, Time: 12.072s
