From a90320be00a2a28a08b8bc7344fced5d9f42fc0f Mon Sep 17 00:00:00 2001 From: Bryan Van Deusen Date: Tue, 6 Oct 2026 21:43:45 -0400 Subject: [PATCH] ci: revert the forced boot-check failure; the gate was seen to block the push (rule 177) Run 8447 on b307f53: the boot check failed at the forced assertion, Push was skipped, clean-up ran, :dev stayed on sha256:718d2ca (98854d9) and no :b307f53 image exists in the registry. Co-Authored-By: Claude Opus 5.5 --- .forgejo/workflows/ci.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.forgejo/workflows/ci.yml b/.forgejo/workflows/ci.yml index f8b2c5b..1e3ec37 100644 --- a/.forgejo/workflows/ci.yml +++ b/.forgejo/workflows/ci.yml @@ -204,7 +204,7 @@ jobs: fetch /health | grep -q '"ok"' # tini is PID 1, so zombies are reaped and SIGTERM reaches Steward. - test "$(docker exec "$SMOKE-app" cat /proc/1/comm)" = "forced-failure-rule-177" + test "$(docker exec "$SMOKE-app" cat /proc/1/comm)" = "tini" # A fresh database lands on first-run setup: a real page, its assets # served by Steward itself, and no third-party host in it (rule 155).