Repository navigation
Test failure: System.Threading.ThreadPools.Tests.ThreadPoolTests.FileStreamFlushAsyncThreadPoolDeadlockTest #127895
Description
Failed in: runtime-coreclr libraries-jitstress 20260506.1
Failed tests:
net11.0-linux-Release-x64-no_tiered_compilation-AzureLinux.3.Amd64.Open
- System.Threading.ThreadPools.Tests.ThreadPoolTests.FileStreamFlushAsyncThreadPoolDeadlockTest
Error message:
Microsoft.DotNet.RemoteExecutor.RemoteExecutionException : Half-way through waiting for remote process.
Timed out at 5/6/2026 7:59:07 AM after 60000ms waiting for remote process.
Process ID: 3372
Handle: 127015638209024
Name: dotnet
MainModule: /datadisks/disk1/work/B0CD08E4/p/dotnet
StartTime: 5/6/2026 7:58:07 AM
TotalProcessorTime: 00:00:01.4300000
Stack trace:
at Microsoft.DotNet.RemoteExecutor.RemoteInvokeHandle.Dispose(Boolean disposing) in /_/src/arcade/src/Microsoft.DotNet.RemoteExecutor/src/RemoteInvokeHandle.cs:line 225
at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args) in /_/src/coreclr/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.CoreCLR.cs:line 37
at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr) in /_/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.cs:line 57
Known Issue Error Message
DO NOT USE JSON BELOW IF THIS IS A BUILD BREAK otherwise build analysis will allow pull requests to merge that break the build worse. For a build break, do not use this issue form. Make a regular new issue.
Fill the error message using step by step known issues guidance.
{
"ErrorMessage": ["ThreadPoolTests.FileStreamFlushAsyncThreadPoolDeadlockTest [FAIL]","Timed out"],
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}Known issue validation
Build: 🔎
Result validation:
Validation performed at: 8/4/2026 10:30:57 PM UTC
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 1 | 6 |
Activity
dotnet-policy-service commentedon May 7, 2026
Tagging subscribers to this area: @JulieLeeMSFT, @VSadov
See info in area-owners.md if you want to be subscribed.
jakobbotsch commentedon Jun 26, 2026
Failed in a Mono run in https://dev.azure.com/dnceng-public/public/_build/results?buildId=1482978&view=logs&jobId=f4616eca-4cb2-53ea-b86a-d7a1235a32a0&j=f4616eca-4cb2-53ea-b86a-d7a1235a32a0&t=31583cee-4aa0-5a17-ffcf-2c561f437bdf.
jkotas commentedon Jun 30, 2026
Failed in #129424
VSadov commentedon Jul 3, 2026
should see if this reproduces again and whether it reproduced on other platforms.
VSadov commentedon Aug 4, 2026
This may be just because the test is too stressful to run with JIT stress, Debug, Mono, etc..
There were no failures for nearly a month. I will remove blocking-clean-ci.
This also does not seem to be a blocker for net11. If reproduces, we may just block it on JIT stress/debug/etc..