From 432487f4e87de604253df9d9432d27248fc28dba Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Wed, 27 May 2026 09:31:49 +0100 Subject: [PATCH] M10: 5/6 recipes green via real !testme; lasuite-docs upgrade failed (retrying) Co-Authored-By: Claude Opus 4.7 (1M context) --- JOURNAL.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/JOURNAL.md b/JOURNAL.md index 061b46d..fdf3f67 100644 --- a/JOURNAL.md +++ b/JOURNAL.md @@ -689,3 +689,22 @@ Three fixes to make the real-PR path exercise the upgrade stage (mirror PR clone 3. (earlier) backup/restore already pass `-C -o`. Now firing !testme on the other recipes' open PRs (keycloak#1, matrix-synapse#1, lasuite-docs#1, n8n#1) — they queue at MAX_TESTS=1. cryptpad has no open PR → opening one next. + +--- +## 2026-05-27 — M10/D10: real !testme breadth runs — 5/6 green, lasuite-docs upgrade retry + +Fired !testme on all 6 recipe PRs (capacity=1, sequential). Results (real PR-triggered, full 3-stage): +- custom-html #84 ✅ (PR head db9a9502) +- keycloak #86 ✅ (DB realm marker survives upgrade) +- matrix-synapse #87 ✅ (postgres marker, pg_backup hook) +- n8n #89 ✅ +- cryptpad #90 ✅ (test PR #2 opened via Gitea API: branch ci/testme + .ci-testme marker) +- **lasuite-docs #88 ❌** — install ✅ + backup ✅, but UPGRADE failed: `abra app upgrade … -o` + → `FATA deploy failed` (a convergence failure during the 9-service rolling upgrade prev→latest, + not a timeout). It PASSED on the host/catalogue run, and ran right after the heavy matrix build, + so likely transient resource contention. Re-fired !testme on lasuite-docs#1 to test + transient-vs-persistent. + +So the real-!testme path + the upgrade fixes (upstream tags + `upgrade -o`) work across simple, DB, +DB+media, workflow, and stateful recipes. lasuite-docs (the object-storage/S3 category, required) +needs its upgrade to pass on the real path for the 6/6 D10 proof.