[richiemcilroy]

Windows Engine verify sometimes kills an export test process with an access violation (0xc0000005), on main and on unrelated branches: colour, gif, mov and camera_offset in the last week, a different test each time. The job log shows only the exit code, so there is nothing to diagnose from.

Two things hid the crash:

• run.sh runs in Git Bash, and MSYS starts its child processes with crash reporting off (SEM_NOGPFAULTERRORBOX). nextest and the test binaries inherit that, so Windows never writes a dump, even with Windows Error Reporting configured.
• The runners do not keep dumps by default.

This change applies to Windows test jobs only:

• turns on Windows Error Reporting local dumps into the verify report folder, which the existing upload carries;
• runs each test binary through scripts/verify/native-launch.ps1 (PowerShell clears the inherited mode) via Cargo's target runner, which nextest honors;
• on failure, prints each dump's stack with cdb and the build's own PDBs.

Checked on blacksmith-8vcpu-windows-2025, with nextest 0.9.148 and a test crate:

	Today	With the runner
Crashing test reported as	ABORT	ABORT (exit code passes through)
Passing tests, non-ASCII output	unchanged	unchanged
Crash dump	none	written; cdb reads it
Cost		about 1 s per test process

macOS, Linux and local runs are unchanged.

Confidence Score: 5/5

The PR appears safe to merge; the previous dump-upload issue is addressed.

Summary

Keeps Windows crash dumps from engine tests and prints their stacks.

• Windows engine tests now keep crash dumps and print their stacks.

_{Reviews (2) · Last reviewed commit: "ci(verify): upload Windows crash dumps w..." · Reviewed by Greptile}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
cap-status	Ready	Preview	Oct 26, 2026 4:34pm UTC

[capy-ai]

Capy found no issues.

View 1 other finding in Capy.

[greptile-apps]

Fixture crash dumps disappear

If prepare_recorded_fixtures crashes, Windows saves its dump here, but the failed preparation step skips Test. Upload report then skips too: it only accepts a skipped test when the macOS collector sets collected=true. The printed stack remains, but the dump disappears with the runner.

Let the Windows collector signal that dumps exist, and include that signal in the upload condition.

Prompt To Fix With AI

This is a comment left during a code review.
Path: .github/workflows/engine-verify-os.yml
Line: 196-197

Comment:
**Fixture crash dumps disappear**

If `prepare_recorded_fixtures` crashes, Windows saves its dump here, but the failed preparation step skips `Test`. `Upload report` then skips too: it only accepts a skipped test when the macOS collector sets `collected=true`. The printed stack remains, but the dump disappears with the runner.

Let the Windows collector signal that dumps exist, and include that signal in the upload condition.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

[richiemcilroy]

@greptileai review

[capy-ai]

Capy found no issues.

View 2 other findings in Capy.