Skip to content

[ci-scan] Test failure: stackoverflowtester — Exit code: 0x0000008B, expected 0x00000086 #130182

Closed
Closed
[ci-scan] Test failure: stackoverflowtester — Exit code: 0x0000008B, expected 0x00000086#130182
Assignees
mangod9
Labels
Known Build ErrorUse this to report build issues in the .NET Helix tabagentic-workflowsarea-VM-coreclrblocking-clean-ci-optionalBlocking optional rolling runs
Milestone
Future

Description

@github-actions
github-actions
bot
opened on Jul 3, 2026

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1484415
Build error leg or test failing: coreclr linux arm64 checked (jitstress2-jitstressregs) — baseservices/exceptions/stackoverflow/stackoverflowtester/stackoverflowtester.cmd

Error Details

Under the runtime-coreclr jitstress2-jitstressregs configuration (AzDO definition 111) on main, the stackoverflowtester test fails on linux arm64. In TestStackOverflowSmallFrameMainThread, the child process that intentionally overflows its stack terminates with exit code 0x0000008B (139, SIGSEGV) instead of the expected 0x00000086 (134, SIGABRT fail-fast):

BEGIN EXECUTION
corerun ... stackoverflowtester.dll ''
Running stackoverflow test(smallframe main)
"Stack overflow."
System.Exception: Exit code: 0x0000008B, expected 0x00000086
   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

First observed in build 1474511 (20260621.1, 2026-06-21); the immediately preceding build 1473990 (2026-06-20) passed. Still failing in source build 1484415 (2026-06-27) and its follow-up build 1484851 (2026-06-28), so this is a stable failure rather than a one-off stress flake.

Previously tracked as #126502 (arch-arm32, closed 2026-04-14 as completed); this is a post-close recurrence of the same signature on linux arm64 under JIT stress. Related: #126502.

Error Message

{
  "ErrorMessage": [
    "Running stackoverflow test(smallframe main)",
    "Exit code: 0x0000008B, expected 0x00000086"
  ],
  "ErrorPattern": "",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Note

Auto-filed by the ci-failure-scan outer-loop CI failure scanner (detection-only; AI/Copilot-generated). Occurrence counts are maintained by Build Analysis from the JSON signature above. Mitigation (fix or JIT-owner hand-off) is handled separately by the ci-failure-fix workflow.

Note

🔒 Integrity filter blocked 19 items

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

  • #72905 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #33993 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #129897 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #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".
  • #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".
  • #44158 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".
  • #5158 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".
  • #127541 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".
  • #107239 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • #110173 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
  • ... and 3 more items

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 · ● 12.6M · ◷

Report

Summary

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

Activity

  1. github-actions
    added
    blocking-clean-ci-optionalBlocking optional rolling runs
    Known Build ErrorUse this to report build issues in the .NET Helix tab
    agentic-workflows
    on Jul 3, 2026
  2. dotnet-policy-service
    added
    untriagedNew issue has not been triaged by the area owner
    on Jul 3, 2026

  3. github-actions commented on Jul 6, 2026

    @github-actions
    github-actionsBot
    on Jul 6, 2026 – with GitHub Actions
    ContributorAuthor

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

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

    Under runtime-coreclr jitstress2-jitstressregs (AzDO definition 111) on linux arm64, baseservices/exceptions/stackoverflow/stackoverflowtester fails in TestStackOverflowSmallFrameMainThread:

    Running stackoverflow test(smallframe main)
"Stack overflow."
System.Exception: Exit code: 0x0000008B, expected 0x00000086

    The child process that intentionally overflows its stack terminates with 0x8B (139, SIGSEGV) instead of the expected 0x86 (134, SIGABRT fail-fast). In other words, under JIT stress-regs the stack-overflow probe/handling no longer converts the overflow into the controlled fail-fast path and instead takes a raw segfault. That is a JIT/VM codegen + stack-probe interaction (stress-only), not a test defect.

    Per this workflow's rules JIT/VM codegen fixes are out of bounds for an automated PR, so this is a hand-off.

    Evidence

    • Failing build: 1484415, still failing in follow-up 1484851.
    • First failing build in window: 1474511 (2026-06-21); the prior build 1473990 (2026-06-20) passed — a tight, bisectable regression window.
    • Affected pipeline: runtime-coreclr jitstress2-jitstressregs (def 111), linux arm64.
    • Possibly related: stackoverflowtester Exit code: 0x0000008B, expected 0x00000086 #126502 (same stackoverflowtester signature previously tracked on arch-arm32, closed 2026-04-14) — this is a recurrence on linux arm64 under JIT stress.

    Suggested reviewers / area contacts

    • area-CodeGen-coreclr (JIT stress-regs): @JulieLeeMSFT, @dotnet/jit-contrib
    • area-VM-coreclr (stack-overflow probe / fail-fast): @agocke

    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 a JIT/VM stack-probe codegen issue under stress that must not be worked around in 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.

    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 Fixer · ● 9.2M · ◷

  4. JulieLeeMSFT
    assigned
    mangod9
    on Jul 7, 2026
  5. JulieLeeMSFT
    added
    area-VM-coreclr
    on Jul 7, 2026
  6. github-project-automation
    added this to AppModelon Jul 7, 2026

  7. JulieLeeMSFT commented on Jul 7, 2026

    @JulieLeeMSFT
    JulieLeeMSFT
    on Jul 7, 2026
    Member

    @mangod9, PTAL.

  8. dotnet-policy-service commented on Jul 7, 2026

    @dotnet-policy-service
    dotnet-policy-serviceBot
    on Jul 7, 2026 – with Dotnet Policy Service
    Contributor

    Tagging subscribers to this area: @agocke
    See info in area-owners.md if you want to be subscribed.

  9. mangod9 commented on Jul 8, 2026

    @mangod9
    mangod9
    on Jul 8, 2026
    Member

    doesnt seem like the job has any relevant dumps with the stackoverflow failure. The dumps collected are for other unrelated tests.

  10. steveisok
    removed
    untriagedNew issue has not been triaged by the area owner
    on Jul 25, 2026
  11. steveisok
    added this to the Future milestone on Jul 25, 2026
  12. kotlarmilos
    closed this as completedon Oct 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Known Build ErrorUse this to report build issues in the .NET Helix tabagentic-workflowsarea-VM-coreclrblocking-clean-ci-optionalBlocking optional rolling runs

Type

No type

Projects

  • AppModel
    Status
    No status

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions