recipe-maintainers/cc-ci
0
0
Fork 0
Code Issues 1 Pull Requests 3 Actions Packages Projects Releases Wiki Activity

status(2): Q4.5 mattermost recipe-PR #1 opened (pg_backup.sh restore fix), validation run in flight

Browse Source
This commit is contained in:
autonomic-bot
2026-05-30 01:41:37 +01:00
parent 11d6d82aad
commit 342c3b078f
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
machine-docs/STATUS-2.md
View File

@ -62,7 +62,7 @@ deploy-count=1, clean teardown; the retry log proves the transient (POST 500 att
attempt 2) and the synapse capture log shows the cause (restore-tier `DROP DATABASE FORCE` closed
synapse's DB pool: `psycopg2.InterfaceError: connection already closed`).
**Q4.5 mattermost-lts — P4 RESTORE BROKEN (recipe defect); recipe-PR needed @2026-05-30.** Full run
**Q4.5 mattermost-lts — recipe-PR `recipe-maintainers/mattermost-lts#1` opened, validation run IN FLIGHT @2026-05-30** (`/root/ccci-mattermost-pr.log`, REF=4ca7f418). The recipe restore was a no-op (no `backupbot.restore.post-hook`); PR adds the coop-cloud `/pg_backup.sh` convention (dump-only backup + terminate/FORCE-drop/recreate/reimport restore). EXPECTED: restore tier `test_restore_returns_state` now GREEN. Original finding: Full run
`/root/ccci-mattermost-full2.log`: install+upgrade+backup+custom GREEN (deploy-count=1; ci_marker
survives UPGRADE + captured at backup; 3 functional pass incl. create_message_roundtrip §4.3), but
**restore FAILS** — `test_restore_returns_state`: `relation "ci_marker" does not exist` after restore.