diff --git a/quest/m0/interop-green/README.md b/quest/m0/interop-green/README.md index c10bbed5e4f..32a34d7b31b 100644 --- a/quest/m0/interop-green/README.md +++ b/quest/m0/interop-green/README.md @@ -1,4 +1,4 @@ -# Interop and Video pass on main +# [XS] Interop and Video pass on main ## Goal @@ -8,9 +8,7 @@ means a new break. Interop has failed every scheduled run since ## Waiting -- moq-dev/moq: a scheduled Interop run on `main` passes, once this quest's - fixture fixes, wire-compat remeasure, and 90-minute job budget have - landed. Check with +- moq-dev/moq: a scheduled Interop run on `main` passes. Check with `gh run list --repo moq-dev/moq --workflow interop.yml --event schedule`. Triage any red run, then delete this quest once one passes. @@ -29,8 +27,7 @@ port-reservation lines are negative self-tests in `interop/relay-log.test.sh` and `lib/harness.test.sh` that pass. Already owned: the intermittent media-matrix timestamp-gap cells (`cpp -> js-native-node`, `go -> c`, browser `rust -> js` timeouts) belong to -[test flakes](/quest/m0/test-flakes-2/README.md), with -[moq-dev/moq#6990](https://github.com/moq-dev/moq/pull/6990) open. So does +[test flakes](/quest/m0/test-flakes-2/README.md). So does the fallback audio stall, which hit on `moq-lite-07-wip` in [41495461904](https://github.com/moq-dev/moq/actions/runs/41495461904) and @@ -64,8 +61,11 @@ showed more causes, fixed in this quest's own PR: The P2P data-channel test timed out once, in 41668668824, and passes locally; triage it if it recurs. -Public API: none. Wire: none. - -## Required +Scheduled run +[41863118968](https://github.com/moq-dev/moq/actions/runs/41863118968) +(2026-11-04, after every fix above landed) passed the open-GOP recovery +case, P2P, and wire-compat. Its only failure was the fallback audio stall +above, on `moq-lite-07-wip` in Chromium, which the IETF22 fallback quest +owns. -- [Confirm scheduled open-GOP recovery passes](/quest/m0/interop-green/open-gop-fixture.md) - a scheduled Interop run passes the open-GOP case with the typed fixture and direct effect/page error reporting +Public API: none. Wire: none. diff --git a/quest/m0/interop-green/open-gop-fixture.md b/quest/m0/interop-green/open-gop-fixture.md deleted file mode 100644 index 2e692cbfd41..00000000000 --- a/quest/m0/interop-green/open-gop-fixture.md +++ /dev/null @@ -1,37 +0,0 @@ -# [XS] Confirm scheduled open-GOP recovery passes - -## Goal - -The scheduled Interop run's "Harness regressions" step passes the -`open-gop.browser.ts` case "software video recovery trims orphan pictures -after join and later gap" on `main` with the typed fixture and direct -reporting of effect/page exceptions. - -## Waiting - -- moq-dev/moq: a scheduled Interop run on `main` including - [moq-dev/moq#7814](https://github.com/moq-dev/moq/pull/7814) passes the - open-GOP recovery case. Check with - `gh run list --repo moq-dev/moq --workflow interop.yml --event schedule`, - then inspect its "Harness regressions" step. Delete this quest once that - case passes; the parent epic owns the whole-workflow pass. - -## Plan - -Decided 2026-11-03 (maintainer, /quest-plan of the follow-ups from -[moq-dev/moq#7715](https://github.com/moq-dev/moq/pull/7715) and -[moq-dev/moq#7716](https://github.com/moq-dev/moq/pull/7716)): milestone m0, -a child of the Interop epic, since it breaks the scheduled run. - -[moq-dev/moq#7672](https://github.com/moq-dev/moq/pull/7672) supplied the -missing broadcast name. [moq-dev/moq#7814](https://github.com/moq-dev/moq/pull/7814) -replaces the unchecked broadcast stub with a real local origin and a -manual-catalog `Broadcast`. It reuses the browser harness's existing page -and console error collection while polling recovery, so an effect exception -fails directly even when the recovery promise never settles. The recovery -assertions and 60-second deadline remain unchanged. - -Only scheduled evidence remains. Do not dispatch Nightly manually or treat -a local pass as scheduled evidence. Triage a remaining failure at its cause. - -Public API: none. Wire: none. diff --git a/quest/m0/test-flakes-2/ietf22-fallback.md b/quest/m0/test-flakes-2/ietf22-fallback.md index b7c7643087d..e7d5fc0b962 100644 --- a/quest/m0/test-flakes-2/ietf22-fallback.md +++ b/quest/m0/test-flakes-2/ietf22-fallback.md @@ -3,7 +3,7 @@ ## Goal When the newest of two live publishers withdraws, a browser `@moq/watch` -viewer on moq-transport-22, or on moq-lite in Firefox, plays the still-live +viewer on moq-transport-22 or moq-lite plays the still-live older run within the media lane's derived 1039 ms bound. It keeps its session, and its audio resumes with its video. Both failures are fixed at their cause once one recurs with enough evidence to reproduce it deterministically. @@ -30,7 +30,11 @@ after the fallback), on `old-moq-lite-07-wip`: and [2026-11-03](https://github.com/moq-dev/moq/actions/runs/41656613559/job/125988510133). [moq-dev/moq#7716](https://github.com/moq-dev/moq/pull/7716) found it -separate from the Firefox tone problem. Read those jobs' artifacts first. If +separate from the Firefox tone problem. Scheduled Interop runs hit the same +stall in Chromium, also on `old-moq-lite-07-wip`: +[41495461904](https://github.com/moq-dev/moq/actions/runs/41495461904), +[41668668824](https://github.com/moq-dev/moq/actions/runs/41668668824), and +[41863118968](https://github.com/moq-dev/moq/actions/runs/41863118968). Read those jobs' artifacts first. If they isolate the cause, the Waiting item clears. If they don't, rerun the Waiting section's command with `--media-engines firefox` and the same `RUST_LOG` filter.