Skip to content

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

Draft
github-actions[bot] wants to merge 2 commits into
mainfrom
ci-scan/disable-stackoverflowtester-interpreter-dc74daefb8cec02e
Draft

[ci-scan] Skip stackoverflowtester under interpreter mode (refs #127899)#128793
github-actions[bot] wants to merge 2 commits into
mainfrom
ci-scan/disable-stackoverflowtester-interpreter-dc74daefb8cec02e

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

Reasoning

The stackoverflowtester test triggers a native assert m_crawl.GetCodeInfo()->IsValid() when running under the CoreCLR interpreter. During stack overflow handling, the StackFrameIterator encounters an interpreter frame whose CodeInfo is invalid. This is a known interpreter-mode stack-walker incompatibility — the test itself is correct but the interpreter cannot handle the scenario yet.

Adding <InterpreterIncompatible>true</InterpreterIncompatible> is the standard mechanism used by other tests (e.g., DefaultStackCommit, ForeignThreadExceptions, ObjectStackAllocationTests) to opt out of interpreter-mode execution.

Linked KBE: #127899

Match verification (from Step 4.8):

  1. Same test/family: yes — baseservices/exceptions/stackoverflow/stackoverflowtester matches exactly
  2. Same failure signature: yes — m_crawl.GetCodeInfo()->IsValid() assert failure
  3. Same OS: yes — Windows (both x64 and arm64)
  4. Same architecture: yes — x64 and arm64

Impact on platforms

  • runtime-interpreter (def 316) / windows-arm64 Checked / exit code 1 (assert failure)
  • runtime-interpreter (def 316) / windows-x64 Checked / exit code 1 (assert failure)

Errors log

Running stackoverflow test(smallframe main)
"Stack overflow."
"Assert failure(PID 11148 [0x00002b8c], Thread: 9372 [0x249c]): m_crawl.GetCodeInfo()->IsValid()"
END EXECUTION - FAILED

First build it occurred

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 2 items

The following items were blocked because they don't meet the GitHub integrity level.

  • #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".

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 · ● 37.9M ·

The test triggers an assert failure (m_crawl.GetCodeInfo()->IsValid())
when running under the CoreCLR interpreter due to invalid CodeInfo on
interpreter frames during stack overflow handling.

Refs #127899

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@dotnet-policy-service
Copy link
Copy Markdown
Contributor

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

@BrzVlad
Copy link
Copy Markdown
Member

BrzVlad commented May 30, 2026

@kotlarmilos the bot resubmitted this PR although I closed #128737

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant