Repository navigation
docs(backlog): the raised rail earned itself in eight minutes - #457
Merged
Merged
Conversation
e2e on main ran 38:30 and green, a new maximum, and the deploy landed 8.5 minutes after the old 1800 s witness rail would have expired. With the rail where it was this morning the measurement would have been lost the way #439 was. The lesson is not the band but distrust of it: a sampled upper bound was overtaken twice in one night. The swap itself: 2359 x 200 per path, zero non-200, offset +15.8 s with the identity read ten times rather than once. #453 gains a fifth data point and the loop's next unit, I1, is written up with the three decisions it waits on. 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 last swap of the night, and the measurement that
justifies the change made during it.
What it carries
e2eonmainran38:30 and green — a new maximum. The witness started at 01:19:26 with
WITNESS_MAX_SEC=2700; the old 1800 s rail would have expired at 01:49:26 andthe deploy came at 01:57:53. That measurement would have been lost the way
chore: bump traefik from
24841feto575fa15#439's was, for a different reason: there the runner queue sat in front of thejob, here
e2eitself is longer than the rail.overtaken twice in one night: 17:38, then 34:57, now 38:30. Start as soon as
e2eisin_progressand set the rail generously — starting early costsnothing, a short window costs the whole measurement.
a60f44c,ops.lastDeploy.at01:58:13Z, servingstartedAt01:58:28.779Z, offset +15.8 s, 2359 × 200 per path, zero non-200.
The identity was read ten times and was identical ten times — after the
twin-read finding in the entry above, it is not read once any more.
window does cover the known bug: a container swap sometimes drops one request, and two samples cannot say how often #304 offsets. Four of five do;
3b990e5with3.4 s remains the outlier.
it waits on: new
--d-boot-*tokens (the offsets cannot be hard-coded asanimation-delay—tools/check-tokens.sh:80catches that), Lenis and GSAPfor I2 against chore: initial JS is 143 KB of a 150 KB budget, before a page exists — due with L8 #237's bundle budget, and the ambient layer sitting in the
sheet's spec table while the build plan defers it to I3.
Tally: 6 drops in roughly 37 800 requests, twelve swap runs in a row without
one. #304 gains no new evidence — five witnessed swaps tonight, all clean.
make checkgreen.