Files
deepseek-harness/scripts
turtle1999 b66aa70051 test(coverage): scope the fork exit ordering claim to the clean exit report
Vitest reports an unexpected worker exit either as "Worker exited unexpectedly"
from the exit event or as "Worker coverage-forks emitted error" when the channel
closes under a send. The record describes the exit, and the error is logged
before it, so only the first form can order the record ahead of the report. The
previous assertion named one hardcoded message; #5900 widened it to whichever
form appeared and so claimed an order the error form cannot satisfy.

The case name no longer claims that order, and the report lookup relies on the
assertion above it instead of repeating the check.

Refs #5813
2026-10-10 13:32:36 +08:00
..
2026-08-13 02:29:17 +08:00
2026-09-08 22:31:16 +08:00
…