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

journal: concurrent-CI fixes landed on cc-ci main (build 236 green)

Browse Source
This commit is contained in:
autonomic-bot
2026-06-09 22:02:08 +00:00
parent ec3e0c35dd
commit 1580738c97
1 changed files with 15 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
cc-ci-plan/JOURNAL.md
View File

@ -302,3 +302,18 @@ assistant3's lane (its verify: upgrade/backup tiers PASSED, restore post-hook fa
/postgres.dump.gz: No such file` — pre-hook never produced the dump in the snapshot) — coordinating via
tmux, not duplicating. Siblings: cc-ci-assistant3 (plausible), cc-ci-upgrader (told to review plausible
failure). Memories moved INTO this repo at memory/ (542ed0a) — auto-memory path is a symlink now.
### Event 2026-06-09 ~21:10 — Concurrent-CI fixes LANDED on cc-ci main (build 236 green)
Orchestrator (this session) landed the queue/concurrency work on cc-ci main, first green push build
since the lint drift began (~209): `9a77725` style: repo-wide lint pass (118 files — ruff format/fix,
shfmt, nixpkgs-fmt/statix/deadnix, yamllint, lasuite-docs quoting; lint PASS + 138 unit tests);
`c0df77d` fix(harness): concurrent-run safety — per-recipe flock `/run/lock/cc-ci-recipe-<recipe>.lock`
taken in main() BEFORE fetch_recipe (kernel auto-release, no stale-lock mode; same-recipe runs
serialise, different recipes parallel) + active-run registry `/run/cc-ci-active/<domain>` pidfiles with
three-way janitor (alive=never reap / dead=reap now / unknown=age fallback 2h; pid-reuse guarded via
/proc cmdline match on run_recipe_ci) + .drone.yml: concurrency.limit 1→2, CCCI_JANITOR_MAX_AGE=0
REMOVED, stale capacity=1 comments rewritten; `c828f6c` merge of assistant3's
test/plausible-upgrade-base-3.0.1 pin (UPGRADE_BASE_VERSION=3.0.1+v2.0.0). Branch push build 234 green,
main push build 236 green. /root/builder-clone fast-forwarded to c828f6c. assistant3 notified via tmux
(plausible !testme unblocked; restore-hook gzip failure is their lane). Next: immich PR #2 !testme
re-triggered alone (checkout parked clean at a92b28d) — polling to verdict.