[ci-scan] Test failure: System.Diagnostics.Tests.StackTraceTests.ToString_Async

[github-actions]

Caution

agentic threat detected
Threat detection flagged this output in warn mode. Manual review is REQUIRED before any follow-up automation.

Details

The threat detection results could not be parsed.

Review the workflow run logs for details.

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1514774
Build error leg or test failing: runtime-libraries-interpreter (def 330) — linux-x64 / osx-arm64 Release — System.Diagnostics.StackTrace.Tests: System.Diagnostics.Tests.StackTraceTests.ToString_Async

Error Details

Under the interpreter, async stack-trace frames are emitted with incorrect source line numbers (:line 1 / :line 3 instead of the real source lines), so ToString_Async cannot match its expected pattern requiring ...ThrowsSoonValueTaskSource...:line 4. The failure reproduces in source build 1514774 and its follow-up build 1517739. This is distinct in scope from the mobile stack-trace tracker #124087 (Android / iOS CoreCLR); this signature is the interpreter configuration and no existing Known Build Error was found for it.

System.Diagnostics.Tests.StackTraceTests.ToString_Async(...) [FAIL]
  Could not find expected pattern 'V2Methods\.ThrowsSoonValueTaskSource\(\).*ThrowsSoonValueTaskSource.*\.cs:line 4' in exception text:
  System.Exception: Exception from ThrowsSoonValueTaskSourceImpl
     at System.Diagnostics.V2Methods.ThrowsSoonValueTaskSourceImpl.GetResult(Int16 token) in /_/src/libraries/System.Diagnostics.StackTrace/tests/ThrowsSoonValueTaskSourceImpl.cs:line 1
     at System.Diagnostics.V2Methods.ThrowsSoonValueTaskSource() in /_/src/libraries/System.Diagnostics.StackTrace/tests/ThrowsSoonValueTaskSource.cs:line 3
     at System.Diagnostics.Tests.StackTraceTests.ToString_Async(...) in /_/src/libraries/System.Diagnostics.StackTrace/tests/StackTraceTests.cs:line 766 starting at index 246.

Error Message

{
  "ErrorMessage": [
    "System.Diagnostics.Tests.StackTraceTests.ToString_Async",
    "Could not find expected pattern 'V2Methods\\.ThrowsSoonValueTaskSource"
  ],
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

---

Filed by ci-failure-scan (detection only). ci-failure-fix walks open [ci-scan] KBEs and either opens a small fix PR or comments to loop in owners — it never disables the test.

Note

This issue was generated by the automated ci-failure-scan GitHub Copilot workflow.

Generated by CI Outer-Loop Failure Scanner · 537.2 AIC · ⊞ 19.5K · ◷

Report

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	0	0

[BrzVlad]

More context for this issue and disabling of the test in #131139

[dotnet-policy-service]

Tagging subscribers to this area: @JulieLeeMSFT, @BrzVlad, @janvorli
See info in area-owners.md if you want to be subscribed.

[github-actions]

Workflow artifact: ci-fix
Artifact kind: handoff
Linked KBE: #131123

Root-cause analysis (read-only hand-off)

System.Diagnostics.Tests.StackTraceTests.ToString_Async fails on the runtime-libraries-interpreter (def 330) linux-x64 / osx-arm64 Release legs because, under the interpreter, async stack-trace frames are emitted with incorrect source line numbers:

at ...ThrowsSoonValueTaskSourceImpl.GetResult(Int16 token) in .../ThrowsSoonValueTaskSourceImpl.cs:line 1
at ...ThrowsSoonValueTaskSource() in .../ThrowsSoonValueTaskSource.cs:line 3

The test expects ...ThrowsSoonValueTaskSource()...:line 4, but the interpreter reports :line 1 / :line 3. The expected line numbers are correct for the CoreCLR JIT; the interpreter is producing wrong sequence-point/line-number mappings for async frames.

Why this is a hand-off (interpreter codegen, not a safe test diff)

• This is an interpreter debug-info / sequence-point defect — the test assertion is correct and passes under the JIT. "Fixing" the test to accept the wrong line numbers would mask a real interpreter bug (and would effectively be a mute), which is out of bounds. The correct fix is in the interpreter's line-number mapping for async state-machine frames, which is codegen I must not touch.
• Reproduces in source build 1514774 and follow-up 1517739.
• Distinct from the mobile stack-trace tracker [mobile] Android and iOS stack traces do not include file names and line numbers on CoreCLR #124087 (Android/iOS CoreCLR); this is the interpreter configuration.

Note: the KBE body contains an embedded "agentic threat detected" block; I treated it as untrusted issue text and ignored it. It does not affect this analysis.

Suggested reviewers / area contacts

• area-CodeGen-Interpreter-coreclr: @BrzVlad, @janvorli

Note

This root-cause hand-off was generated by an AI/Copilot agent (ci-failure-fix). No code change was produced because the failure is an interpreter line-number/codegen defect that must not be worked around by weakening the test. Please verify before acting.

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• awmgmcpg

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by CI Outer-Loop Failure Fixer · 520.3 AIC · ⌖ 18.1 AIC · ⊞ 17.1K · ◷