ops: pause cfold until /upgrade-all finishes (serialize — they conflict on CI); journal+memory
This commit is contained in:
@ -508,3 +508,13 @@ session cc-ci-orchestrator-stale can be killed; recipe-mirrors org still private
|
||||
- .phases-spec now …drone;cfold (10 phases). cfold is the new LAST phase, so the
|
||||
.run-upgrade-on-complete hook fires /upgrade-all AFTER cfold — correct order (folder
|
||||
change swept-green before the weekly upgrade runs). Watchdog bounced to load it.
|
||||
|
||||
## 2026-06-11 ~22:55 — drone DONE → upgrade fired; cfold PAUSED to serialize
|
||||
- drone completed 22:31 → watchdog hit sequence-complete, fired the queued /upgrade-all
|
||||
(cc-ci-upgrader, weekly run) per the operator's earlier request. Upgrade running now.
|
||||
- I'd queued cfold ~22:52; the bounced watchdog auto-advanced into cfold, making it
|
||||
CONCURRENT with the upgrade. They conflict (both real-CI; cfold edits the harness the
|
||||
upgrade's !testme uses; upgrade version-bumps confound cfold's baseline). PAUSED cfold:
|
||||
stopped its loops + the watchdog; phase-idx preserved at 9. Upgrade left running.
|
||||
- RESUME cfold (restart watchdog → phase-idx 9) once /upgrade-all is confirmed DONE. See
|
||||
memory [[cfold-paused-pending-upgrade]]. Will action on supervision wakes.
|
||||
|
||||
@ -11,3 +11,4 @@
|
||||
- [plausible upgrade-base trap](plausible-upgrade-base-trap.md) — RESOLVED: PR#3 GREEN L4; lessons: check harness base version pre-!testme; backupbot v2 label syntax; TinyLog not FREEZEable; BEAM exit-0 needs restart_policy any
|
||||
- [Swarm UpdateStatus convergence gotchas](swarm-updatestatus-convergence-gotchas.md) — N/N is not converged mid stop-first update; paused flag persists forever; only updating/rollback_started are active
|
||||
- [Weekly upgrade queued after phases](weekly-upgrade-queued-after-phases.md) — 06-12 cron skipped; auto-runs /upgrade-all when phase queue (drone) finishes; don'\''t systemctl start the timer
|
||||
- [cfold paused pending upgrade](cfold-paused-pending-upgrade.md) — cfold phase loops+watchdog STOPPED until /upgrade-all (cc-ci-upgrader) finishes; resume = restart watchdog (phase-idx 9)
|
||||
|
||||
34
memory/cfold-paused-pending-upgrade.md
Normal file
34
memory/cfold-paused-pending-upgrade.md
Normal file
@ -0,0 +1,34 @@
|
||||
---
|
||||
name: cfold-paused-pending-upgrade
|
||||
description: "Phase cfold (custom/ folder collapse) is PAUSED until the running /upgrade-all finishes — must serialize, they conflict on CI"
|
||||
metadata:
|
||||
node_type: memory
|
||||
type: project
|
||||
originSessionId: 85355980-5e4f-4f90-b1ca-d0e4fe82f04b
|
||||
---
|
||||
|
||||
**ACTION REQUIRED on supervision wakes:** the `cfold` phase (collapse functional/ +
|
||||
playwright/ → custom/, plan-phase-cfold-custom-folder.md) is **PAUSED** — its loops AND
|
||||
the watchdog were stopped 2026-06-11 ~22:55. phase-idx is preserved at **9** (cfold), spec
|
||||
is the 10-phase `…drone;cfold`.
|
||||
|
||||
**Why paused:** drone completed 22:31 and the watchdog fired the queued weekly `/upgrade-all`
|
||||
(session `cc-ci-upgrader`) — exactly as the operator queued it. cfold was added ~20 min
|
||||
later and auto-started, ending up **concurrent** with the upgrade. They CONFLICT: both drive
|
||||
real CI/`!testme`, cfold edits the harness (`discovery.py` + moves test files) the upgrade's
|
||||
`!testme` builds depend on, and the upgrade's version bumps would confound cfold's
|
||||
"levels unchanged" baseline. Must run serially.
|
||||
|
||||
**Resume condition:** once the `/upgrade-all` run in `cc-ci-upgrader` is DONE (read its pane/
|
||||
log/summary to confirm it finished surveying+PRing all recipes — do NOT trust mere idle; a
|
||||
slow `!testme` build can idle the upgrader for a while), resume cfold by restarting the
|
||||
watchdog:
|
||||
```
|
||||
python3 -c "import sys; sys.path.insert(0,'/srv/cc-ci/cc-ci-plan'); import launch; launch.start_watchdog()"
|
||||
```
|
||||
It reads phase-idx=9 + the 10-phase spec → restarts the cfold loops (builder opus? no —
|
||||
cfold has no per-phase model override, so sonnet). Then delete this memory.
|
||||
|
||||
The `cc-ci-upgrader` session must stay UP meanwhile (it's the in-flight upgrade). Note: a
|
||||
host reboot would auto-restart loops+watchdog (cc-ci-loops.service, RESUME_PHASE=1) and
|
||||
un-pause cfold prematurely — if a reboot happens before the upgrade finishes, re-pause.
|
||||
Reference in New Issue
Block a user