diff --git a/quest/m1/test-flakes-2/README.md b/quest/m1/test-flakes-2/README.md index f95604acd21..5933d4b2893 100644 --- a/quest/m1/test-flakes-2/README.md +++ b/quest/m1/test-flakes-2/README.md @@ -41,7 +41,6 @@ Public API: none. Wire: none. - [Interop close code](/quest/m1/test-flakes-2/interop-close-code.md) - adopt that release so the browser reliably sees `unauthorized` for a refused session - [Auth refresh mocks time](/quest/m1/test-flakes-2/auth-refresh-mock-time.md) - moq-relay's auth refresh and fixed-lease tests measure a grant's life on one mocked clock - [uring teardown close](/quest/m1/test-flakes-2/uring-teardown-close.md) - moq-uring's published-close teardown test holds under load, fixed at its cause -- [Auth serve signals](/quest/m1/test-flakes-2/auth-serve-signals.md) - moq-cli's auth serve signal tests hold under load - [js -> go rewind](/quest/m1/test-flakes-2/js-go-rewind.md) - the `js -> go` interop cell never reads a frame below the previous group's start, fixed on the side that produced it ## Related diff --git a/quest/m1/test-flakes-2/auth-serve-signals.md b/quest/m1/test-flakes-2/auth-serve-signals.md deleted file mode 100644 index 685a169fbc1..00000000000 --- a/quest/m1/test-flakes-2/auth-serve-signals.md +++ /dev/null @@ -1,22 +0,0 @@ -# [S] moq-cli auth serve signal tests hold under load - -## Goal - -`moq-cli`'s `auth_serve_stops_on_sigint` and `auth_serve_stops_on_sigterm` -(`rs/moq-cli/tests/auth_serve.rs`) pass under a loaded `just check`, fixed at -their cause. They still prove that a signal exits `auth serve` cleanly. - -## Plan - -Seen 2026-10-13 on #5458 and #5481 at load averages near 47 on 24 cores. -Each test timed out and passed alone. Each test spawns a real `moq auth serve` and -bounds two waits with a 10 s `TIMEOUT`: the "auth server listening" log line, -which only gates setup, and the exit after the signal, which is the property. - -Reproduce under load first and record which wait expired. The exit wait must -stay bounded so an ignored signal fails at its assertion instead of hanging -CI. Find what in the expired interval is slow under load and fix it, or move -the check to a deterministic in-process test if the process boundary isn't -what it proves. Never widen a timeout or add a retry. - -Public API: none. Wire: none.