Repository navigation
[ci-scan] Test failure: System.Transactions.Tests.AsyncTransactionScopeTests.AsyncTSTest #130126
Description
Build Information
Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1489260
Build error leg or test failing: windows-x64 Release libraries JitStress (Helix queue windows.10.amd64.open.rt) — System.Transactions.Tests.AsyncTransactionScopeTests.AsyncTSTest
Pipeline: runtime-coreclr libraries-jitstress (AzDO definition 138) on main.
Error Details
Under the libraries-jitstress configuration the async transaction-scope test fails in its RemoteExecutor child process with an unhandled System.Exception: Test failed with events: raised from AssertTransaction:
System.Transactions.Tests.AsyncTransactionScopeTests.AsyncTSTest(variation: 54) [FAIL]
Microsoft.DotNet.RemoteExecutor.RemoteExecutionException : Remote process failed with an unhandled exception.
Stack Trace:
Child exception:
System.Exception: Test failed with events:
...
at System.Transactions.Tests.AsyncTransactionScopeTests.AssertTransaction(String txId) in /_/src/libraries/System.Transactions.Local/tests/AsyncTransactionScopeTests.cs:line 1669
Seen in build 1489260 (finished 2026-07-01) and still present in the later build 1491202, so this is not a one-off flake.
Error Message
{
"ErrorMessage": [
"System.Transactions.Tests.AsyncTransactionScopeTests.AsyncTSTest",
"Microsoft.DotNet.RemoteExecutor.RemoteExecutionException : Remote process failed with an unhandled exception.",
"System.Exception: Test failed with events:"
],
"ErrorPattern": "",
"BuildRetry": false,
"ExcludeConsoleLog": false
}Note
Auto-filed by the ci-failure-scan outer-loop CI failure scanner (detection-only; AI/Copilot-generated). Mitigation is tracked separately by ci-failure-fix. Occurrence counts are maintained automatically by Build Analysis.
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
dotnet.github.io
To allow these domains, add them to the
network.allowedlist in your workflow frontmatter:
network:
allowed:
- defaults
- "dotnet.github.io"See Network Configuration for more information.
Note
🔒 Integrity filter blocked 21 items
The following items were blocked because they don't meet the GitHub integrity level.
- #129876
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #88361
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #117370
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #50848
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #19341
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #5158
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #7096
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #5984
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #5101
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #5318
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #44158
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #5637
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #7231
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #5130
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #114222
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - #93321
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved". - ... and 5 more items
To allow these resources, lower min-integrity in your GitHub frontmatter:
tools:
github:
min-integrity: approved # merged | approved | unapproved | noneGenerated by CI Outer-Loop Failure Scanner · ● 10.4M · ◷
Report
Summary
| 24-Hour Hit Count | 7-Day Hit Count | 1-Month Count |
|---|---|---|
| 0 | 8 | 14 |
Activity
github-actions commentedon Jul 6, 2026
Workflow artifact: ci-fix
Artifact kind: handoff
Linked KBE: #130126
Root-cause analysis (read-only hand-off)
Under the JIT-stress libraries configuration (
runtime-coreclr libraries-jitstress, AzDO definition 138)System.Transactions.Tests.AsyncTransactionScopeTests.AsyncTSTest(variation: 54)fails inside its RemoteExecutor child process:The failure appears only under the JIT-stress configuration and reproduces across builds (1489260 and 1491202), so it is a stable stress failure, not a flake. An async/await transaction-scope flow that is correct under the default JIT but wrong under JIT stress points to a JIT stress-mode codegen issue in the async state machine / transaction-ambient-flow, rather than a defect in the transactions library or the test.
Per this workflow's rules, JIT codegen fixes (and codegen-stress workarounds in library/test code) are out of bounds for an automated PR, so this is a hand-off.
Evidence
windows-x64 Release libraries JitStress, Helixwindows.10.amd64.open.rt), still failing in 1491202.runtime-coreclr libraries-jitstress(def 138) onmain.Suggested reviewers / area contacts
area-CodeGen-coreclr(JIT stress codegen):@JulieLeeMSFT,@dotnet/jit-contribarea-System.Transactionscontext (test flow inAsyncTransactionScopeTests):@SamMonoRTNote
This root-cause hand-off was generated by an AI/Copilot agent (
ci-failure-fix). No code change was produced because the evidence points to JIT-stress codegen that must not be worked around in library or test code. Please verify before acting.Note
🔒 Integrity filter blocked 6 items
The following items were blocked because they don't meet the GitHub integrity level.
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:Fix ci-failure-scan failure inventory (#130188)
dotnet-policy-service commentedon Jul 7, 2026
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch
See info in area-owners.md if you want to be subscribed.
jakobbotsch commentedon Jul 10, 2026
@VSadov the assert was added in #129502. Can you take a look?
I couldn't find anything that stores
ManagedThreadId.t_currentManagedThreadIdin CoreCLR. Where is that expected to happen?jakobbotsch commentedon Jul 10, 2026
Ah, looks like the TLS field has special allocation here:
runtime/src/coreclr/vm/threadstatics.cpp
Lines 728 to 732 in 1d85f40
I looked at the dump and this looks like the same underlying issue as #130212. So this was already fixed by #130317.
JulieLeeMSFT commentedon Jul 14, 2026
@jakobbotsch, it failed on 7/11.
Failed in (1):
Console Log: Console Log
Source: runtime-coreclr libraries-jitstress-random / net11.0-linux-Release-x64-jitstress_random_2-AzureLinux.3.Amd64.Open / System.Transactions.Tests.AsyncTransactionScopeTests.AsyncTSTest
Failed tests:
jakobbotsch commentedon Jul 14, 2026
This was a duplicate of #130212 so it should be fixed by #130536 too.
Indeed, I don't see it in the latest run of libraries-jitstress.
Fix ci-failure-scan failure inventory (#130188)