[ci-scan] Test failure: JIT/Regression/CLR-x86-JIT/V1-M12-Beta2/b65423 crashes on browser-wasm with `strerror` called after runt [Content truncated due to length]

[github-actions]

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1541935
Build error leg or test failing: coreclr Pri1 Runtime Tests Run browser wasm checked - JIT/Regression/CLR-x86-JIT/V1-M12-Beta2/b65423/b65423/b65423.cmd

Error Details

The b65423 JIT regression test fails on the runtime-coreclr outerloop browser-wasm checked leg. After catching the expected TypeLoadException (exit 100), the wasm runtime aborts during shutdown because strerror is invoked after the runtime has exited. The test then reports Expected 100 / Actual 1.

Caught TypeLoadException exception: 100
Aborted(Assertion failed: native function `strerror` called after runtime exit (use NO_EXIT_RUNTIME to keep it alive after main() exits))
(wasm/redacted)

RuntimeError: unreachable
    at abort (corerun.js)
    at assert (corerun.js)
    at strError (corerun.js)
    at new ErrnoError (corerun.js)
    at Object.getStreamChecked (corerun.js)
    at Object.getStreamFromFD (corerun.js)
    at _fd_write (corerun.js)
Expected: 100
Actual: 1
END EXECUTION - FAILED
02:10:36.782 Failed test: JIT/Regression/CLR-x86-JIT/V1-M12-Beta2/b65423/b65423/b65423.cmd

Observed in build 1541935 (2026-08-06) and reproduced in follow-up build 1542249 on the same leg.

Error Message

{
  "ErrorMessage": [
    "Aborted(Assertion failed: native function `strerror` called after runtime exit (use NO_EXIT_RUNTIME to keep it alive after main() exits))",
    "Failed test: JIT/Regression/CLR-x86-JIT/V1-M12-Beta2/b65423/b65423/b65423.cmd"
  ],
  "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 here to loop in owners — it never disables the test.

Note

This issue was generated by an AI agent (ci-failure-scan Copilot workflow).

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 Scanner · 554.9 AIC · ⌖ 12.2 AIC · ⊞ 18.3K · ◷

Report

Build	Repository	Test	Pull Request
1543347	dotnet/runtime	JIT/Regression/CLR-x86-JIT/V1-M12-Beta2/b65423/b65423/b65423.cmd	#131866
1543091	dotnet/runtime	JIT/Regression/CLR-x86-JIT/V1-M12-Beta2/b65423/b65423/b65423.cmd

Summary

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

[dotnet-policy-service]

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

[dotnet-policy-service]

Tagging subscribers to 'arch-wasm': @lewing, @pavelsavara
See info in area-owners.md if you want to be subscribed.

[JulieLeeMSFT]

@pavelsavara, PTAL.
cc @dotnet/wasm-contrib.