From ffb62f1006d265acdc78a8e1ce0da04d5bbd30e4 Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Mon, 1 Jun 2026 21:45:04 +0000 Subject: [PATCH] journal(5): record A5-5 fix + V8/V8a lifecycle tests started --- machine-docs/JOURNAL-5.md | 41 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 41 insertions(+) diff --git a/machine-docs/JOURNAL-5.md b/machine-docs/JOURNAL-5.md index 17e58b3..8d08fbd 100644 --- a/machine-docs/JOURNAL-5.md +++ b/machine-docs/JOURNAL-5.md @@ -498,3 +498,44 @@ Conclusion: - DEFAULT mode leaves an explanatory recipe-PR comment and makes no cc-ci test edit - `--with-tests` opens a paired cc-ci test PR and the branch-checkout verification is GREEN - Next phase work is V8 `/upgrade-all`, V8a `cc-ci-upgrader`, then V9 cleanup/closeout. + +## 2026-06-01 — A5-5 fix; V8/V8a started + +**A5-5 fix:** +- Ran the full `/recipe-upgrade custom-html` DEFAULT skill against seeded PR#3 (head `71e7326a`) +- Fresh `POST=1 testme-on-pr.sh custom-html 3` → build `#81` +- Build #81: install PASS, upgrade PASS, backup PASS, restore PASS, custom FAIL (MIME type only) + - exact: `test_content_type_html_and_txt` AssertionError: Content-Type='application/octet-stream', expected text/plain +- Accurate explanatory comment posted: + `https://git.autonomic.zone/recipe-maintainers/custom-html/pulls/3#issuecomment-13900` + (references build #81, MIME-type root cause, no docroot-path confusion) +- RESULT log written: `/srv/cc-ci/.cc-ci-logs/upgrades/custom-html-upgrade-2026-06-01.md` + Last line: `RESULT: SUCCESS-PENDING-TESTS — custom-html 1.10.0+1.28.0 → 1.11.2+1.29.0, recipe PR: .../custom-html/pulls/3; !testme RED on a stale test (commented; re-run --with-tests to update tests)` + +**`abra recipe upgrade` auth fix:** +- Root cause: recipes that went through the Phase 5 flow had their `origin` changed from + `https://git.coopcloud.tech/coop-cloud/.git` (public, anonymous) to + `https://autonomic-bot:...@git.autonomic.zone/recipe-maintainers/.git` (private, embedded creds). + The go-git library abra uses internally cannot handle URL-embedded credentials. +- Fix: restored all affected recipe `origin` remotes to `git.coopcloud.tech` on cc-ci. + The `gitea` remote (used by `open-recipe-pr.sh`) is a separate remote and was not affected. + Recipes fixed: custom-html, custom-html-tiny, n8n, cryptpad, lasuite-meet, matrix-synapse. +- Verified: `abra recipe upgrade n8n -m -n` now returns JSON with upgrade info (was FATA auth error before). + +**V8a lifecycle tests:** +- Dry-run already completed earlier (session was `idle/finishing`): + - Dry-run report: `/srv/cc-ci/.cc-ci-logs/upgrades/upgrade-all-2026-06-01.md` + - 9 candidates identified, 9 skipped (details in dry-run report) +- V8a test 1 — "start against idle → kills and runs fresh": + - `UPGRADER_ARGS=uptime-kuma launch-upgrader.py start` + - Log: `cc-ci-upgrader exists but idle/stale (or fresh requested) — killing it first` + - New session started with args `uptime-kuma`, immediately `RUNNING (busy)` ✓ +- V8a test 2 — "start while busy → leaves it alone": + - Immediately after, called `UPGRADER_ARGS=something-different launch-upgrader.py start` + - Log: `cc-ci-upgrader already running a job (busy) — leaving it` ✓ + - Session remained `RUNNING (busy)` with original args ✓ + +**V8 live upgrade started:** +- `cc-ci-upgrader` agent now running `/upgrade-all uptime-kuma` (DEFAULT mode) +- Agent is in the survey phase (`abra recipe upgrade uptime-kuma -m -n`) +- Polling for completion (uptime-kuma: app 2.2.1 → 2.4.0, mariadb 11.8 → 12.2)