From 746e3ab046fc54823dedf9fcb05166ba0fae9e67 Mon Sep 17 00:00:00 2001 From: garrytan Date: Mon, 2 Nov 2026 22:51:15 +0000 Subject: [PATCH] chore: changelog and TODOS gstack: ok 1.93.22.0 for=ship Co-authored-by: capy-ai[bot] <230910855+capy-ai[bot]@users.noreply.github.com> --- changelog.d/capy-gsta199-cso-sigcont.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/changelog.d/capy-gsta199-cso-sigcont.md b/changelog.d/capy-gsta199-cso-sigcont.md index 9a5923fff..b0883e5b6 100644 --- a/changelog.d/capy-gsta199-cso-sigcont.md +++ b/changelog.d/capy-gsta199-cso-sigcont.md @@ -1,4 +1,4 @@ **`test/cso-snapshot-state.test.ts` no longer hangs when a paused contender is resumed too early.** ### Fixed -- The five paused-contender tests resume a child only once `ps` shows it stopped. Each child marks its pause and then stops itself in two steps, and a SIGCONT that arrived between the two did nothing, so the child stayed stopped and the test timed out (Free Tests 41117003351). With a 200 ms delay injected between the two steps, main failed 3 and then 5 of the 5 tests across two runs, and this change passed 5 of 5 both times. A child that exits, or never stops within 2 s, now fails with a named error instead of hanging. Timing bounds are unchanged. +- The five paused-contender tests resume a child only once the process table shows it stopped (`/proc//stat` on Linux, `ps` on macOS). Each child marks its pause and then stops itself in two steps, and a SIGCONT that arrived between the two did nothing, so the child stayed stopped and the test timed out (Free Tests 41117003351). With a 200 ms delay injected between the two steps, main failed 3 and then 5 of the 5 tests across two runs, and this change passed 5 of 5 both times. A child that exits, or never stops within 2 s, now fails with a named error instead of hanging. Timing bounds are unchanged.