Repository navigation
Closed
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabarea-System.Transactionsblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
Description
Build Information
Build: https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=1234474
Build error leg or test failing: System.Transactions.Local.Tests.WorkItemExecution
Pull request: #122425
Error Message
Fill the error message using step by step known issues guidance.
{
"ErrorMessage": "'System.Transactions.Local.Tests' END OF WORK ITEM LOG: Command timed out, and was killed",
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}Known issue validation
Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1234474
Error message validated: ['System.Transactions.Local.Tests' END OF WORK ITEM LOG: Command timed out, and was killed]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 12/17/2025 9:40:16 PM UTC
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 1 | 9 | 21 |
Reacted by Copilot
Metadata
Metadata
Assignees
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabUse this to report build issues in the .NET Helix tabarea-System.Transactionsblocking-clean-ciBlocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
Activity
[-]System.Transactions.Local.Tests timeout[/-][+]System.Transactions.Tests.OleTxTests.Recovery timeout[/+]dotnet-policy-service commentedon Dec 17, 2025
Tagging subscribers to this area: @roji, @SamMonoRT
See info in area-owners.md if you want to be subscribed.
JulieLeeMSFT commentedon Mar 5, 2026
Failed in:
Failed tests:
danmoseley commentedon Mar 20, 2026
The
Recovery()test inOleTxTestshas a structural issue that likely causes the work item timeout.The test spawns a remote process via
RemoteExecutor.Invokewith aCrashingEnlistment. That remote process doesThread.Sleep(Timeout)whereTimeout = TimeSpan.FromMinutes(1)— it unconditionally burns a full minute staying alive. If MSDTC is slow or unresponsive on the CI machine, the main process also blocks onWaitOne(Timeout)calls (up to 1 minute each, and there are several). These add up and can push the entire test work item past its time limit.The core problem is that nothing bounds the wall-clock time of a hung MSDTC interaction — if MSDTC never delivers the commit notification, both the remote process and the main test thread block until their respective 1-minute timeouts expire, and
RemoteInvokeHandle.Dispose()also blocks waiting for the remote process to exit.Suggested fix: Add a
TimeOuttoRemoteInvokeOptionsso that a hung remote process gets killed rather than blocking indefinitely:Optionally also add
[Fact(Timeout = 180_000)]to the test method so that if the main thread is stuck on aWaitOne, xunit marks the test as failed and moves on rather than letting it burn the entire work item budget. A leaked threadpool thread is a small price compared to killing the whole work item.jakobbotsch commentedon Mar 30, 2026
@danmoseley This failed again in #126169. I opened a new issue #126304 since I didn't realize this one existed.