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

status+journal(redfix): M2 — mattermost-lts FIXED (run #901 all green, restore fixed); discourse #4 green; bluesky PR #4 created (promote-path verify next)
Some checks failed
continuous-integration/drone/push Build is failing
Details

Browse Source
This commit is contained in:
autonomic-bot
2026-06-18 01:30:57 +00:00
parent abfbe8b0aa
commit c3854a9bcc
2 changed files with 22 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
machine-docs/JOURNAL-redfix.md
View File

@ -291,3 +291,23 @@ Surveyed open PRs on all 6 mirrors before doing redundant work:
M2 plan refined: VERIFY discourse #4 (re-!testme fresh) + mattermost #1 (!testme); CREATE recipe PRs
for bluesky (unique alias) + gitea (app.ini writable); HARNESS fixes for mumble (handshake stab) +
keycloak (collision-free canonical_domain + enroll). Starting with mattermost #1 !testme.
## 2026-06-18T01:30Z — M2: mattermost-lts FIXED (verified) + discourse already green + bluesky PR created
- **mattermost-lts**: !testme on PR #1 `ci/pg-restore` (@4ca7f418) → run #901 ALL tiers green
(install/upgrade/backup/restore/custom, every junit failures=0 skipped=0). The M1-failing
`restore__cc-ci__test_restore.py::test_restore_returns_state` now PASSES — the pg_backup.sh restore
post-hook (terminate conns + DROP DATABASE WITH FORCE + createdb + reimport dump) round-trips
postgres state. **FIXED + verified.** (Nothing merged — operator merges.)
- **discourse**: PR #4 `discourse-official-image` already !testme-green @53ba0910 (run #849, today
16:36Z) — the official-image migration makes the upgrade overlay pass. Will re-verify fresh for
current evidence before the M2 claim.
- **bluesky-pds**: created mirror PR #4 `ci/warm-routing-alias` (unique `pds` alias on internal +
caddy reverse_proxy/ask → pds:3000; service stays `app`). compose validated (`docker compose config`
rc=0). VERIFICATION NOTE: bluesky's 000 is warm-promote-only (cold path always green), so !testme
(cold) won't reproduce/verify it — I'll verify by running the FIXED recipe through the promote path
(cold-on-latest with the fix checked out) → warm-bluesky-pds should serve 200 (vs M1's 000), then
tear down the phantom canonical.
Remaining M2: bluesky promote-verify, gitea recipe PR (app.ini writable), keycloak harness
(collision-free canonical_domain + enroll), mumble harness (handshake stabilization).

4
machine-docs/STATUS-redfix.md
View File

@ -82,8 +82,8 @@ deploys (Adversary done with M1).
| Recipe | Fix type | PR/branch | Status |
|---|---|---|---|
| mattermost-lts | recipe PR (pg_backup.sh + restore.post-hook) | mirror PR #1 `ci/pg-restore` (exists, correct) | !testme triggered @01:24Z — verifying restore green |
| bluesky-pds | recipe PR (unique internal alias for caddy→app) | — | pending |
| mattermost-lts | recipe PR (pg_backup.sh + restore.post-hook) | mirror PR #1 `ci/pg-restore` @4ca7f418 | **DONE — !testme run #901 ALL tiers green** (restore__cc-ci failures=0 skipped=0; the M1-failing test_restore_returns_state now PASSES) |
| bluesky-pds | recipe PR (unique `pds` internal alias for caddy) | mirror PR #4 `ci/warm-routing-alias` | PR created; verifying on PROMOTE path (warm-bluesky-pds → expect 200 vs M1 000; !testme cold-only won't reproduce) |
| gitea | recipe PR (app.ini → writable volume) | — | pending |
| keycloak | harness (collision-free canonical_domain) + enroll | — | pending |
| mumble | harness (handshake readiness/retry stabilization) | — | pending |