Dogfood: Tier 4 deploy canary (long-lived — do not merge or close) - #13
Open
RollNuts wants to merge 1 commit into
Open
Dogfood: Tier 4 deploy canary (long-lived — do not merge or close)#13RollNuts wants to merge 1 commit into
RollNuts wants to merge 1 commit into
Conversation
Carries a movable head SHA for the post-deploy Tier 4 smoke. Placed in this repository rather than veripsa-dev because the durable inbox drains per-account round-robin: a canary sharing an account with the busiest repositories waits behind their traffic, and the deploy's own restart deepens that queue -- so Tier 4 timed out on deploys that had actually succeeded. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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
1 participant
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.
Purpose
Long-lived infrastructure PR. Do not merge. Do not close.
It exists so the post-deploy Tier 4 smoke check has a pull request whose head SHA can be moved cheaply. The smoke sends a synthetic
check_suitefor this head and then waits for aVeripsacheck to appear on that exact SHA.Why it lives here instead of
RollNuts/veripsa-devThe durable webhook inbox drains per-account round-robin. The previous canary shared an account with the busiest repositories, so its synthetic delivery waited behind that account's traffic — and a deploy's own restart deepens that queue. The result was Tier 4 timing out on deploys that had actually succeeded (Tier 1 confirmed the target serving 7/7 samples, Tiers 2/2b/3 green, then a rollback triggered purely by the canary).
Moving the canary to a different account gives it its own fairness turn, so Tier 4 measures the deployed build rather than the owner's unrelated push volume.
Operating notes
docs/dogfood/tier4-canary.md, a marker with no product meaning.