Declare b14 and b9, which are now built and promoted - #275
Merged
Conversation
Both worker images are built, smoke-passed and promoted on the cluster -- current now resolves to 710eb85f42e9 for standard and fed9cf7727eb for integration, with b13 and b8 as the exact N-1 rollback. These constants still named b13 and b8, which is the last thing standing between the estate and a pin advance, since estate validation compares them against the provider image contract. b9 is the publish that failed three times in #265 and succeeded on the fourth attempt with no change to the publish path. The earlier failures were not reproduced and no cause was established, so the issue stays open for the cause even though the image now exists.
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.
Both worker images are built, smoke-passed and promoted on the cluster:
The constants here still named b13 and b8, which is the last thing standing between the estate and a pin advance — estate validation compares them against the provider image contract.
b9 is the publish that failed three times in #265. It succeeded on the fourth attempt with no change to the publish path. I am not claiming a fix: the earlier failures were not reproduced and no cause was established, so #265 stays open for the cause even though the image now exists.
--preserve-failed-builderfrom #274 was armed and not needed.b9's smoke: docker 29.1.3 on overlayfs with the systemd cgroup driver, non-root access ok, chromium 151.0.7922.34 launches, host and metadata routes blocked, public egress ok, ssh absent and masked, cold-only startup, and the full toolchain set (bun 1.3.14, go 1.26.6, node 22/24/25, pnpm 11.22.0, rust 1.97.1, uv 0.11.30, yarn 4.18.0).
make verifygreen.https://claude.ai/code/session_01NpzpgiRaxi5mHVTMoRYndt