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
6 changes: 6 additions & 0 deletions quest/m0/test-flakes-2/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -153,6 +153,11 @@ skipped the timing report. A TERM landing after a lane forked but before
hung. The exit trap now waits again, and cancellation reads the job table,
fixed by [moq-dev/moq#8138](https://github.com/moq-dev/moq/pull/8138).

Added 2026-11-07 (maintainer, /quest-complete): `js/net`'s
http:// fingerprint tests, whose slow real fetch lets the WebTransport hedge
timer fire on the host clock, seen in
[moq-dev/moq#8163](https://github.com/moq-dev/moq/pull/8163)'s CI.

Added 2026-11-07 (maintainer, /quest-complete): `js/net`'s lite-07
relative-start integration test, which failed once on main in
[moq-dev/moq#8165](https://github.com/moq-dev/moq/pull/8165)'s baseline run.
Expand All @@ -170,5 +175,6 @@ Public API: none. Wire: none.

- [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
- [moq-gst's sink-restart pad test survives load](/quest/m0/test-flakes-2/gst-sink-restart-pads.md) - `a_moqsink_restart_keeps_pads_when_caps_arrive_at_different_times` keeps its pads under load
- [The http:// fingerprint tests survive a slow fetch](/quest/m0/test-flakes-2/fingerprint-host-clock.md) - a fingerprint fetch slower than the 500 ms hedge no longer trips the host-clock guard
- [A lite-07 relative start resolves to the publisher's start every time](/quest/m0/test-flakes-2/lite07-relative-start.md) - `js/net`'s frameless-newest-group integration test stops reading a start of 0, and its `test.skip` is removed
- [A lite-07 reply FINs instead of resetting when the subscriber FINs mid-write](/quest/m0/test-flakes-2/lite07-reply-fin.md) - `js/net`'s empty-window reply test passes under `--rerun-each 200`, fixed in the publisher
30 changes: 30 additions & 0 deletions quest/m0/test-flakes-2/fingerprint-host-clock.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
# [XS] The http:// fingerprint tests survive a slow fetch

## Goal

`js/net/src/connection/connect.test.ts`'s http:// fingerprint tests pass
under load: a fingerprint fetch slower than `hedgeWebTransport`'s 500 ms
hedge no longer fires a host-clock timer that the `bun test` guard fails.

## Plan

Planned 2026-11-07 (maintainer, /quest-complete), a follow-up of
[moq-dev/moq#8163](https://github.com/moq-dev/moq/pull/8163), whose CI run
[42402778685](https://github.com/moq-dev/moq/actions/runs/42402778685/job/128493969468)
failed `test js` on a PR that doesn't touch `js/net`. The failing test,
"an http:// fingerprint longer than a SHA-256 is refused without reading
the rest" (`connect.test.ts:176` at the time), took 894 ms: its connect
arms the hedge timer before `connectWebTransport` fetches the fingerprint
from a real `Bun.serve` server, the fetch outlasted 500 ms, and the timer
fired on the host clock inside that same test. `timeout` already disarms
when its dial settles (`js/clock/src/timer.ts`), so no timer outlives its
test.

The three http:// fingerprint tests at `:147`, `:176`, and `:208` talk to a
real HTTP server but lack the `hostTime(); // a real HTTP server` opt-out
their sibling at `:230` carries, which the mock-clock epic's rules allow for
real I/O. Decide in the PR between adding that opt-out and arming the hedge
only after the fingerprint resolves, so a slow fetch can't start a second
dial. Prove it by delaying the fingerprint response past the hedge.

Public API: none. Wire: none.