Skip to content

docs(quest): record TS duration reproduction evidence #5217

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
kixelated wants to merge 3 commits into from
Closed

docs(quest): record TS duration reproduction evidence #5217

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
08e5545
quest: claim TS duration fidelity investigation
kixelated Oct 10, 2026
654abe6
docs(quest): record TS duration reproduction evidence
kixelated Oct 10, 2026
d439fe7
docs(quest): keep investigation within plan section
kixelated Oct 10, 2026
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
14 changes: 14 additions & 0 deletions quest/m1/test-flakes-2/ts-duration-fidelity.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,3 +18,17 @@ without it. No longer timeout and no lower duration threshold.
Check against #5147 (export ts follows announcements), which may change how an export ends.

Public API: none expected. Wire: none expected.

Investigation (2026-10-10):

On 2026-10-10, an isolated `nix develop --command just test ts` against
main at `6559065b8` captured 20.47 s of the 20.06 s source (ratio 1.021).
The publisher exited 0 and duration-fidelity passed. The run failed a separate
T-STD check (PID 257 held over one second); its subscriber log also contained
missed-deadline drops. That does not reproduce the reported 3.3 s capture.

The capture remains bounded by the existing harness timeout, and no duration
threshold or timeout was changed. #5147 still owns the export announcement/end
lifecycle, while #5175 owns groups left in flight when a relay track ends.
A truncating capture with both process exit statuses and relay/publisher/
subscriber logs is still needed to distinguish these paths before a fix.
Loading