[ci-scan] Skip stackoverflowtester under interpreter mode (refs #127899)

[github-actions]

Reasoning

The stackoverflowtester test hits a StackFrameIterator assert (m_crawl.GetCodeInfo()->IsValid()) when running under the CoreCLR interpreter. The interpreter does not produce valid CodeInfo for its frames during stack overflow unwinding, causing the process to fail-fast (exit code 0xC0000602) instead of producing the expected stack overflow exit code (0xC00000FD). This is a known interpreter-mode incompatibility, not a product bug in the non-interpreter path.

Linked KBE: #127899

Match verification (from Step 4.8):

1. Same test/family: yes — baseservices/exceptions/stackoverflow/stackoverflowtester/stackoverflowtester.cmd in runtime-interpreter pipeline
2. Same failure signature: yes — m_crawl.GetCodeInfo()->IsValid() assert followed by 0xC0000602 exit code (2 matches in failure.log)
3. Same OS: yes — Windows (KBE lists windows-x64 and windows-arm64; current failure is windows-arm64)
4. Same architecture: yes — arm64 (also x64 in prior builds)

Impact on platforms

• runtime-interpreter (def 316) / windows arm64 Checked / Windows.11.Arm64.Open / interpreter mode / exit code 1
• runtime-interpreter (def 316) / windows x64 Checked / Windows.11.Amd64.Open / interpreter mode / exit code 1

Errors log

System.Exception: Exit code: 0xC0000602, expected 0xC00000FD or 0x800703E9
   at TestStackOverflow.Program.TestStackOverflow(String testName, String testArgs, List`1& stderrLines)
   at TestStackOverflow.Program.TestStackOverflowSmallFrameSecondaryThread()
Expected: 100
Actual: 101
END EXECUTION - FAILED

First build it occurred

• Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1407440
• Finished: 2026-05-04 (per KBE [ci-scan] Known Build Error: stackoverflowtester assert m_crawl.GetCodeInfo()->IsValid() in runtime-interpreter #127899)
• Occurrences in window: 5+ (every scanned build on windows-arm64)
• Computed within the scanned window; may not be the true origin.

Linked issue

#127899

---

Filed by ci-failure-scan, which scans dnceng-public outer-loop pipelines on main and converts stable failures into KBEs and test-disable PRs. Comment here or on the workflow file to suggest changes; ci-failure-scan-feedback reads in-scope feedback daily and opens (or updates) a PR with prompt edits.

Note

🔒 Integrity filter blocked 1 item

The following item was blocked because it doesn't meet the GitHub integrity level.

• #125825 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by CI Outer-Loop Failure Scanner · ● 30.6M · ◷

[dotnet-policy-service]

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

[janvorli]

This issue needs to be understood, there is no inherent reason why the codeinfo would be invalid. The cases when it occured in the CI don't have the dumps / logs available anymore, so I don't think we should disable the test without trying to understand the problem.

[BrzVlad]

windows runtime tests was completely broken up until recently so these failures started being reported now. Here is the failure as I'm seeing it in the latest run:

BEGIN EXECUTION
 "C:\h\w\A15608B8\p\corerun.exe" -p "System.Reflection.Metadata.MetadataUpdater.IsSupported=false" -p "System.Runtime.Serialization.EnableUnsafeBinaryFormatterSerialization=true"  stackoverflowtester.dll 
Running stackoverflow test(smallframe main)
"Stack overflow."
""
"Assert failure(PID 6572 [0x000019ac], Thread: 7320 [0x1c98]): m_crawl.GetCodeInfo()->IsValid()"
""
"CORECLR! StackFrameIterator::NextRaw + 0x724 (0x00007ffc`4cdafcbc)"
"CORECLR! StackFrameIterator::Filter + 0xBB0 (0x00007ffc`4cdae6f0)"
"CORECLR! StackFrameIterator::Init + 0x258 (0x00007ffc`4cdaefd8)"
"CORECLR! Thread::StackWalkFramesEx + 0x178 (0x00007ffc`4cdb0d28)"
"CORECLR! Thread::StackWalkFrames + 0x12C (0x00007ffc`4cdb0b1c)"
"CORECLR! LogCallstackForLogWorker + 0x19C (0x00007ffc`4ce45234)"
"CORECLR! LogStackOverflowStackTraceThread + 0x10 (0x00007ffc`4ce45e70)"
"KERNEL32! BaseThreadInitThunk + 0x40 (0x00007ffc`c3028740)"
"<no module>! <no symbol> + 0x0 (0x1a3f7ffc`c6b24714)"
"    File: D:\a\_work\1\s\src\coreclr\vm\stackwalk.cpp:2289"
"    Image: C:\h\w\A15608B8\p\corerun.exe"
""
""
System.Exception: Exit code: 0xC0000602, expected 0xC00000FD or 0x800703E9
   at TestStackOverflow.Program.TestStackOverflow(String testName, String testArgs, List`1& stderrLines)
   at TestStackOverflow.Program.TestStackOverflowSmallFrameMainThread()
   at __GeneratedMainWrapper.Main()
Expected: 100
Actual: 101
END EXECUTION - FAILED

I'm also very aggressive with fixing these pipelines without disabling any tests. I would normally take a look at this next week unless you want to look into this @janvorli

[janvorli]

@BrzVlad I'll try to take a look today.