Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions quest/m1/interop-js-tone.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,3 @@ covers a false "wrong tone" under CPU starvation.
Decided 2026-10-23 (maintainer): its own quest, ranked above the load flakes.

Public API: depends on the cause. Wire: depends on the cause.

## Related

- [Interop timestamp gap](/quest/m1/test-flakes-2/interop-timestamp-gap.md) - the load-only audio flake, a different symptom
1 change: 0 additions & 1 deletion quest/m1/test-flakes-2/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,5 +43,4 @@ Public API: none. Wire: none.
- [Media resource instrumentation](/quest/m1/test-flakes-2/resource-instrumentation.md) - the media test stops seeing a playing player report nothing to release
- [Tone check grace](/quest/m1/test-flakes-2/tone-grace.md) - the interop tone check charges its grace only for audible playback, so a refilling ring under CPU starvation is not a failure
- [IETF22 fallback](/quest/m1/test-flakes-2/ietf22-fallback.md) - an IETF22 browser viewer follows a fallback within the media lane's bound, keeping its session and its audio
- [Interop timestamp gap](/quest/m1/test-flakes-2/interop-timestamp-gap.md) - `rust -> js-native-node` audio has no gap under load
- [Go reservation grant](/quest/m1/test-flakes-2/go-reservation-grant.md) - the Go reservation test waits for its grant
17 changes: 0 additions & 17 deletions quest/m1/test-flakes-2/interop-timestamp-gap.md

This file was deleted.

3 changes: 2 additions & 1 deletion test/interop/clients/js-native/subscribe.ts
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,8 @@ const MAX_DELAY = Milli(1000);

// Audio is checked for gaps, which a reader skipping behind live would cause itself: the matrix
// starts every subscriber at once, and a runtime starved by the others can fall a second behind.
// That is this reader's speed, not the delivery under test, so it gets a wider budget.
// That is this reader's speed, not the delivery under test, so it gets a wider budget. A track's
// max-age caps it, so interop.sh's Rust publisher keeps its media at least this long.
const AUDIO_MAX_DELAY = Milli(5000);

const { positionals, values } = parseArgs({
Expand Down
11 changes: 8 additions & 3 deletions test/interop/interop.sh
Original file line number Diff line number Diff line change
Expand Up @@ -1001,11 +1001,16 @@ run_publisher() {
client_flags "$lang"
case "$lang" in
rust)
# A finished import stays up for its max-age; `stop_publisher` allows 10 s to close.
# The wire-compat FETCH lanes keep the video-only Annex-B input.
# A finished import stays up for its linger (a released CLI: its max-age);
# `stop_publisher` allows 10 s to close. The wire-compat FETCH lanes keep the
# video-only Annex-B input.
if [[ "$AUDIO" -eq 1 ]]; then
# The max-age caps every reader's max delay, so it covers the longest, the native
# JS audio readers' 5 s. Each 1 s fragment lands as one burst, so with a 1 s
# max-age the oldest group a joining reader is served goes stale as soon as the
# next group lands, cutting it mid-read and failing the gap check.
ffmpeg_fmp4 "$tone" "$(publisher_codecs rust)" | RUST_LOG="$CLI_LOG" "$MOQ" --connect "$url" --connect-version "$(cell_version rust)" \
--broadcast "$broadcast" import --max-age 1s fmp4
--broadcast "$broadcast" import --max-age 5s fmp4
else
ffmpeg_h264 | RUST_LOG="$CLI_LOG" "$MOQ" --connect "$url" --connect-version "$(cell_version rust)" \
--broadcast "$broadcast" import --max-age 1s avc3
Expand Down
Loading