relay1/2/3 pin flamenet-relay:prod, but a container keeps running the
image it STARTED with — so every deploy silently left the fleet a build
behind. It was eleven days stale when that was first noticed, answering
every health check the whole time, while the Android live suite ran
against it and reported green about a build production had already moved
off.
That is the failure worth naming: not an outage, a suite that proves the
wrong thing and says it proved the right one.
It drifted twice more today, both times within an hour of my own deploys,
which is how I know a note in a runbook would not have held.
Best-effort on purpose. The fleet is disposable and a production deploy
must not fail because a test relay would not come up — but it must not
quietly stop matching either, so the outcome is printed either way and messenger-privacy-check asserts it independently rather than trusting
this step.
relay1/2/3 pin `flamenet-relay:prod`, but a container keeps running the
image it STARTED with — so every deploy silently left the fleet a build
behind. It was eleven days stale when that was first noticed, answering
every health check the whole time, while the Android live suite ran
against it and reported green about a build production had already moved
off.
That is the failure worth naming: not an outage, a suite that proves the
wrong thing and says it proved the right one.
It drifted twice more today, both times within an hour of my own deploys,
which is how I know a note in a runbook would not have held.
Best-effort on purpose. The fleet is disposable and a production deploy
must not fail because a test relay would not come up — but it must not
quietly stop matching either, so the outcome is printed either way and
`messenger-privacy-check` asserts it independently rather than trusting
this step.
659 tests pass.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
aborted the automatic merge because the source branch was updated. Learn more.
aborted the automatic merge because the source branch was updated. [Learn more](https://gitlab.com/help/ci/pipelines/merge_trains.md#merge-request-dropped-from-the-merge-train).
added 43 commits
<ul><li>e62163bc...7e1792f6 - 42 commits from branch <code>main</code></li><li>ced401bf - The deploy now carries the test fleet with it</li></ul>
[Compare with previous version](/paulhitt/flamenet-relay/-/merge_requests/53/diffs?diff_id=2009171477&start_sha=e62163bc7fbb3f6fb44d4b271044f51bc133b99a)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
relay1/2/3 pin
flamenet-relay:prod, but a container keeps running theimage it STARTED with — so every deploy silently left the fleet a build
behind. It was eleven days stale when that was first noticed, answering
every health check the whole time, while the Android live suite ran
against it and reported green about a build production had already moved
off.
That is the failure worth naming: not an outage, a suite that proves the
wrong thing and says it proved the right one.
It drifted twice more today, both times within an hour of my own deploys,
which is how I know a note in a runbook would not have held.
Best-effort on purpose. The fleet is disposable and a production deploy
must not fail because a test relay would not come up — but it must not
quietly stop matching either, so the outcome is printed either way and
messenger-privacy-checkasserts it independently rather than trustingthis step.
659 tests pass.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com
assigned to @paulhitt
restored source branch
ops/deploy-updates-the-fleetmentioned in merge request !68
aborted the automatic merge because the source branch was updated. Learn more.
added 43 commits
mainced401bf- The deploy now carries the test fleet with itCompare with previous version
mentioned in commit
e210982b63changed the description