diff --git a/js/net/src/ietf/publisher.test.ts b/js/net/src/ietf/publisher.test.ts index 256cee7b9f4..e7d71572b2d 100644 --- a/js/net/src/ietf/publisher.test.ts +++ b/js/net/src/ietf/publisher.test.ts @@ -2663,10 +2663,10 @@ test("draft-22: a backwards range within one group serves nothing and ends the s } }); -// Quarantined: the live group intermittently resets while read. -// Investigation: quest/m0/test-flakes-2/ietf-wider-fill.md. -test.skip.each(["ascending", "descending"] as const)("draft-22: a wider fill is refused in %s order", async (order) => { +test.each(["ascending", "descending"] as const)("draft-22: a wider fill is refused in %s order", async (order) => { const fx = fixture(); + // No max age: group 9 is served live, and a zero budget would give it up mid-write once the + // live group supersedes it, racing this test's read of the refused fill. const track = fx.broadcast.createTrack("video", { timescale: Timescale.MILLI, maxAge: null }); for (const sequence of [0n, 3n, 9n]) { const group = track.createGroup(sequence); @@ -2691,7 +2691,7 @@ test.skip.each(["ascending", "descending"] as const)("draft-22: a wider fill is const fill = await nextUni(fx.uni); if (!fill) throw new Error("missing fill stream"); const served = await readFill(fill, order); - expect(served.reset).toBeDefined(); + expect(served.reset).toBeInstanceOf(StreamError); expect(served.objects).toEqual([]); const live = track.appendGroup(); live.writeFrame({ payload: new TextEncoder().encode("live"), timestamp: Timestamp.now() }); diff --git a/quest/m0/test-flakes-2/README.md b/quest/m0/test-flakes-2/README.md index 3359ece99e1..cf986d8dc97 100644 --- a/quest/m0/test-flakes-2/README.md +++ b/quest/m0/test-flakes-2/README.md @@ -100,7 +100,6 @@ Public API: none. Wire: none. ## Required - [Fallback playback](/quest/m0/test-flakes-2/ietf22-fallback.md) - a browser viewer follows a fallback within the media lane's bound without dropping its session -- [The draft-22 wider-fill refusal test is deterministic](/quest/m0/test-flakes-2/ietf-wider-fill.md) - fix its intermittent live-group reset and re-enable both ordering cases without weakening their assertions - [reload.test.ts's close-drain tests pass under load](/quest/m0/test-flakes-2/reload-close-drain.md) - the drain cases in `js/net`'s reload tests pass in loaded multi-file runs - [dispatch-query's terminate test survives load](/quest/m0/test-flakes-2/dispatch-query-terminate.md) - `test_terminating_the_run_stops_the_running_phase` passes reliably under host load, re-enabled once fixed - [Diagnose and re-enable the FFI datagram connection test](/quest/m0/test-flakes-2/ffi-datagram-roundtrip.md) - diagnose the default-connection timeout and re-enable the quarantined test diff --git a/quest/m0/test-flakes-2/ietf-wider-fill.md b/quest/m0/test-flakes-2/ietf-wider-fill.md deleted file mode 100644 index 29023600e18..00000000000 --- a/quest/m0/test-flakes-2/ietf-wider-fill.md +++ /dev/null @@ -1,35 +0,0 @@ -# [S] The draft-22 wider-fill refusal test is deterministic - -## Goal - -`draft-22: a wider fill is refused in %s order` in -`js/net/src/ietf/publisher.test.ts` passes reliably in both ascending and -descending order, alone and in the loaded suite. Find and fix why its live -group intermittently resets while being read, then remove its quarantine -without weakening the refusal or live-delivery assertions. - -## Plan - -Planned 2026-11-04 under the maintainer's rule to quarantine a known flaky -test immediately and plan its investigation. This is one fixture's flake, -so it is one child of this epic; m0 follows the epic's standing rule that a -flake fails an entire merge batch. - -- The unchanged-main reproduction recorded in - [moq-dev/moq#7860](https://github.com/moq-dev/moq/pull/7860) failed 30/200 - runs. [moq-dev/moq#7851](https://github.com/moq-dev/moq/pull/7851) already - quarantines the same named case. The socket work in - [moq-dev/moq#7883](https://github.com/moq-dev/moq/pull/7883) carries the - precise investigation reference; its absolute-start adapter correction - and controlled early-burst tests do not investigate this separate flake. -- Start from the recorded reproduction and trace the live group's reset in - both orders. Establish whether fixture ownership, clock advancement, - stream ordering, or production behavior causes it before choosing a fix. - Control the responsible clock or event when the fixture is at fault; - fix the production source when it is not. -- Restore the existing test in both orders with its assertions intact. - Neither retries, longer timeouts, nor disabling production behavior is a - fix. Record the original reproduction and loaded-suite results before - and after, including the commands and limits of that evidence. - -Public API: none expected. Wire: none.