Repository navigation
docs(backlog): one witness per e2e attempt, and twenty seconds - #459
Merged
Merged
Conversation
The f0e5998 swap went unobserved and the cause was my own scheduling: the witness was armed for an e2e attempt that then failed, so its 2700 s rail burned down on a window where deploy was gated off by definition, and the rerun's deploy began twenty seconds later. The rule is one witness per e2e attempt, re-armed until the target sha is serving -- and it worked on the next swap, 934 x 200 per path with zero non-200. Also: v0.47.3 is the night's first release, because fix releases where chore and docs correctly did not; p95 read 241.2 ms five minutes after the restart, which is the #452 shape and is written down as explained rather than disproven, since the snapshot had not refreshed for a second reading. And two tooling errors of my own, both of the same family: a kill that returned 0 without touching the witness, and a printf whose format string began with a dash. Co-Authored-By: Claude Code <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backlog only — no code. The measurements around #458, including one swap that
got away and the rule that follows from it.
What it carries
f0e5998swap is unobserved, and the cause was my scheduling. Thewitness was armed while
e2eattempt 1 was running; that attempt failed,so
deploywas gated off and its 2700 s rail burned down on a window where noswap could occur. It expired at 03:46:06. The rerun's
deploybegan at03:46:26 — twenty seconds later. A second witness started at 03:51 and
measured what was already over.
e2eattempt, re-armed until the target sha isactually serving. It worked immediately on the next swap — armed 04:13:34,
twelve seconds after
e2ebegan, and the swap came in clean: 934 × 200 perpath, zero non-200, offset +15.8 s.
v0.47.3is the night's first release, becausefixis a releasing typewhere the six preceding
choreanddocsmerges correctly produced none.p95read 241.2 ms, measured five minutes after the restart. That is thedocs(backlog): the watcher waited for itself, and p95 was stale #452 shape, and the entry says so without claiming a second reading: both
of my reads returned the same
measuredAt, so this is explained by precedentand arithmetic, not disproven by a fresh measurement.
killthat returned 0 whilethe witness kept sampling (I had killed the wrapper, not the witness — a
return code is not proof), and
printf '--- …', whose format string beginswith a dash and is read as an option. The second is why the coverage figure
for test: the witness tail is measured from the twin, and closes before #304's window #453's sixth data point is derived rather than read.
Tally: 6 drops in roughly 41 430 requests, thirteen swap runs in a row without
one. A fifth no-deploy window was discarded rather than counted — it had no
deploy ahead of it and was stopped so the next witness could not run beside it.
make checkgreen.