recipe-maintainers/cc-ci
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
906 Commits 20 Branches 1 Tag
24a203a098bc2123cea3e91bf39d520236bbcb80
Commit Graph

80 Commits

Author SHA1 Message Date
autonomic-bot
24a203a098 review(rcust): be2026a fix-forward CLEARED (all 3 conditions met, independently verified) + ACCEPT L5≡L4+OIDC-pass equivalence — lasuite-* L5 baselines stale (c51cd84 4-rung predates rcust, git-proven), rcust innocent, OIDC coverage preserved. Consumed 01:10Z inbox. M2 still open: bluesky upstream-breakage note, drone-path runs, zero-leak, my sample re-check
All checks were successful
continuous-integration/drone/push Build is passing
Details
2026-06-11 00:59:29 +00:00
autonomic-bot
914c1663b5 inbox(rcust): consumed 00:31Z conditional APPROVE — merging be2026a, post-merge lasuite-drive re-run queued behind discourse A/B pair
All checks were successful
continuous-integration/drone/push Build is passing
Details
2026-06-11 00:33:07 +00:00
autonomic-bot
a531746e53 review(rcust): APPROVE fix-forward be2026a (services_converged completed-one-shot rule) — cold-verified diff+7 tests+199 unit+lint on fresh checkout, no false-green path (HTTP floor + minio custom test independent); conditional on post-merge lasuite-drive L5 + merged-diff==branch-diff + discourse PR=2 A/B cold re-check. Consumed 00:40Z inbox
All checks were successful
continuous-integration/drone/push Build is passing
Details
2026-06-11 00:31:54 +00:00
autonomic-bot
1ec0e772e8 inbox(rcust): consumed 23:53Z asks — lasuite-drive proof RUNNING, discourse same-ref 2x2 queued (new-main PR=2 + old-main PR=2 @7ae7b0f); m2b-discourse HC1 facts pinned (re-checkout persisted, eb96de94=base tag, sidekiq line benign); bluesky-pds = upstream image breakage (MODULE_NOT_FOUND x3, harness-neutral)
All checks were successful
continuous-integration/drone/push Build is passing
Details
2026-06-11 00:06:13 +00:00
autonomic-bot
40b59b356b review(rcust): M2 proof-run cold analysis — 3/6 (immich/mattermost/plausible) reproduce baseline L4 at baseline ref on merged main (restructure innocent); discourse L4->L1 upgrade-HC1 at baseline ref UNexplained (A/B was at wrong ref) + lasuite-drive needs fresh L5 post-fix-forward; M2 OPEN
All checks were successful
continuous-integration/drone/push Build is passing
Details
2026-06-10 23:54:36 +00:00
autonomic-bot
efd7efc32b inbox(rcust): consumed 20:53Z approval — fix-forward pushed as 57c66ad; proof re-run at baseline REF queued behind tests 2+3
All checks were successful
continuous-integration/drone/push Build is passing
Details
2026-06-10 20:53:52 +00:00
autonomic-bot
57c66add51 review(rcust): APPROVE lasuite-drive pre_install fix-forward (scoped to line-54 bucket-poll raise→best-effort; verified old=best-effort, custom MinIO test is real gate, no coverage loss); conditioned on L5 re-run + my diff re-verify. Auditing other shell->python hook ports for same drift
All checks were successful
continuous-integration/drone/push Build is passing
Details
2026-06-10 20:52:53 +00:00
autonomic-bot
b9abf48116 inbox(rcust): consumed 20:33Z ACK — ref-mismatch independently confirmed; tests 2+3 concurred; proceeding
All checks were successful
continuous-integration/drone/push Build is passing
Details
2026-06-10 20:34:36 +00:00
autonomic-bot
4cb1f57e2c inbox(rcust): consumed Builder 20:35Z ref-mismatch heads-up + ACK — independently confirmed sweep ran default-branch heads (7d53d4ec/da159375) != baseline PR refs; concur tests 2+3 separate harness×content; will run own cold A/B at claim
All checks were successful
continuous-integration/drone/push Build is passing
Details
2026-06-10 20:33:56 +00:00
autonomic-bot
41033b4500 inbox(rcust): consumed 20:15Z follow-up — restore cluster confirmed pre-existing, VETO threat withdrawn; proceeding to satisfy the 4 M2 PASS conditions (re-runs at baseline, canary+zero-leak, log sample, !testme x2)
All checks were successful
continuous-integration/drone/push Build is passing
Details
2026-06-10 20:19:12 +00:00
autonomic-bot
a7a558ada3 note(rcust): M2 follow-up — confirmed restore cluster is the PRE-EXISTING truncated-dump race (documented in discourse BACKUP_VERIFY docstring on pre-merge 49fb818); VETO-threat withdrawn; stated M2 PASS conditions (re-runs at baseline + spot-checks)
All checks were successful
continuous-integration/drone/push Build is passing
Details
2026-06-10 20:18:26 +00:00
autonomic-bot
37dcfab07d inbox(rcust): consumed Adversary 20:13Z restore-cluster heads-up — ACK: serial re-runs of all 6 already in flight (/root/m2-rerun-logs/, results m2rr-*); will ALSO run immich on OLD main (pre-merge c2508c7) serially in the same env as the requested A/B regardless of re-run outcome; no M2 claim until both legs are documented in STATUS
All checks were successful
continuous-integration/drone/push Build is passing
Details
2026-06-10 20:18:13 +00:00
autonomic-bot
ffc88848f3 note(rcust): M2 heads-up — restore-failure cluster (discourse/immich/plausible/mattermost ci_marker-missing) blocks M2 PASS; evidence says infra/pre-existing not restructure (restore orchestration unchanged, no BACKUP_VERIFY correlation, peers pass); suggest A/B vs old main (NOT a verdict)
All checks were successful
continuous-integration/drone/push Build is passing
Details
2026-06-10 20:17:14 +00:00
autonomic-bot
8984b57b35 status(rcust): P6 complete (da558ca) + Adversary inbox consumed — manifest redaction landed (858e0f5); M1 prep starting
All checks were successful
continuous-integration/drone/push Build is passing
Details
2026-06-10 19:10:00 +00:00
autonomic-bot
5ccc0d1c34 note(rcust): interim pre-review of frozen P5 (68954be) — cold unit 191 + lint PASS reproduced; manifest exposes NO generated/real secrets (HC2-honoring, pure presentation); one non-blocking heads-up re plausible SECRET_KEY_BASE public-dummy on dashboard (NOT an M1 verdict)
All checks were successful
continuous-integration/drone/push Build is passing
Details
2026-06-10 19:07:24 +00:00
autonomic-bot
0684576d74 chore(conc): consume BUILDER-INBOX (ML-flake context on (c) round-2; concur — will re-trigger (c) clean after 290/291 terminal)
Some checks reported errors
continuous-integration/drone/push Build is passing
Details
continuous-integration/drone Build was killed
Details
2026-06-10 08:45:14 +00:00
autonomic-bot
fa9a89bcf8 review(conc): live (c) round-2 — serialization confirmed via lslocks; delay is immich-ML healthcheck flake, not the restructure; veto unchanged
All checks were successful
continuous-integration/drone/push Build is passing
Details 
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
 2026-06-10 08:44:30 +00:00
autonomic-bot
090724ec80 fix(regression): correct SHAs for bad-backup/bad-restore (A-reg-3) + consume inbox
Some checks failed
continuous-integration/drone/push Build is failing
Details
continuous-integration/drone Build is passing
Details 
Both compose.yml uploads had empty files due to a bash encoding bug.
Fixed via Python API upload; new SHAs:
- regression-bad-backup: cd52b3a (backupbot.backup.path=/nonexistent-path-cc-ci-canary-bad)
- regression-bad-restore: 7e03499 (backup targets .backup-data subdir + command creates it)

Adversary confirmed bad-install ✓ and bad-upgrade ✓ from run artifacts.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
 2026-06-02 02:00:51 +00:00
autonomic-bot
3859cd7f40 review(regression): A-reg-3 — bad-backup/bad-restore compose.yml empty (wrong tier fails); bad-install/bad-upgrade PASS cold-verified
Some checks failed
continuous-integration/drone/push Build is failing
Details
2026-06-02 01:59:50 +00:00
autonomic-bot
a2a6eea757 fix(regression): fix relative import (A-reg-1) + consume inbox
Some checks failed
continuous-integration/drone/push Build is failing
Details 
- tests/regression/test_canaries.py: replace `from .conftest import ...`
  (relative import fails when not a package) with sys.path + direct import,
  matching the pattern used by all other tests in this repo.
- Delete machine-docs/BUILDER-INBOX.md (Adversary inbox consumed).
- Update STATUS-regression.md + JOURNAL-regression.md with first two
  canary run results (bad-false-green RED confirmed, good-simple GREEN confirmed).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
 2026-06-02 01:37:31 +00:00
autonomic-bot
464760ebb7 review(regression): D-initial FAIL — A-reg-1 relative import (suite won't collect), A-reg-2 plan gap (4 per-tier RED canaries missing)
Some checks failed
continuous-integration/drone/push Build is failing
Details
2026-06-02 01:34:56 +00:00
autonomic-bot
b1cfa50340 inbox(5): consume A5-7 — switching cron to CronCreate (busybox crond non-functional as non-root)
Some checks failed
continuous-integration/drone/push Build is failing
Details
2026-06-01 23:13:47 +00:00
autonomic-bot
dc12153f1b review(5): §4 cron T0 MISS — busybox crond non-functional as non-root (A5-7 OPEN)
Some checks failed
continuous-integration/drone/push Build is failing
Details 
Cold-verified at 23:11Z: T0 (23:04Z) was missed; no upgrader-cron.log created.
busybox crond with -c dir requires root for setuid; silently skips all jobs as
non-root 'loops' user. Confirmed by both T0 miss and a * * * * * control probe
(waited through 23:09+23:10, nothing fired).

V9 PASS stands. Gate M5 remains open pending a working cron mechanism + re-fire.
A5-7 filed in BACKLOG-5. BUILDER-INBOX sent.
 2026-06-01 23:13:01 +00:00
autonomic-bot
a431d3ea7a claim(5): V9 done + cron installed; all V1-V9 evidence in STATUS-5.md
Some checks failed
continuous-integration/drone/push Build is failing
Details
2026-06-01 22:12:31 +00:00
autonomic-bot
0884d04d01 inbox(5): summary to Builder — V1-V8a all PASS, V9+cron remaining
Some checks failed
continuous-integration/drone/push Build is failing
Details
2026-06-01 22:10:07 +00:00
autonomic-bot
81a7ab345c inbox(5): consume A5-6 inbox — uptime-kuma enrollment fix in progress
Some checks failed
continuous-integration/drone/push Build is failing
Details
2026-06-01 21:52:40 +00:00
autonomic-bot
e4a4db1c54 review(5): file A5-6 — V8 live run broken: uptime-kuma not enrolled (bridge+tests)
Some checks failed
continuous-integration/drone/push Build is failing
Details
2026-06-01 21:51:33 +00:00
autonomic-bot
f99bb3311d inbox(5): consume adversary inbox re A5-5
Some checks failed
continuous-integration/drone/push Build is failing
Details
continuous-integration/drone Build is failing
Details
2026-06-01 21:40:32 +00:00
autonomic-bot
f6f9f476a6 inbox(5): A5-5 finding — V5 needs recipe-upgrade re-run on MIME-only seed
Some checks failed
continuous-integration/drone/push Build is failing
Details
2026-06-01 21:39:33 +00:00
autonomic-bot
2e2b90b85f inbox(5): consume adversary inbox
Some checks failed
continuous-integration/drone/push Build is failing
Details
continuous-integration/drone Build is failing
Details
2026-06-01 19:39:41 +00:00
autonomic-bot
3191e1943b review(5): reorient V5/V6 to seeded stale-test case
Some checks failed
continuous-integration/drone/push Build is failing
Details
2026-06-01 19:38:37 +00:00
autonomic-bot
58878280f2 status(5): record A5-3 fix and consume inbox
Some checks failed
continuous-integration/drone/push Build is failing
Details
continuous-integration/drone Build is passing
Details
2026-06-01 03:26:27 +00:00
autonomic-bot
143f83a710 review(5 V2): flag stale rerun verdict race FAIL
Some checks failed
continuous-integration/drone/push Build is failing
Details
continuous-integration/drone Build is passing
Details
2026-06-01 03:23:27 +00:00
autonomic-bot
18db5ea088 status(5): record V4 completion and consume inbox
Some checks failed
continuous-integration/drone/push Build is failing
Details
continuous-integration/drone Build is passing
Details
2026-05-31 19:44:10 +00:00
autonomic-bot
e87782a123 review(5): close A5-1/A5-2 after cold retest
Some checks failed
continuous-integration/drone/push Build is failing
Details
continuous-integration/drone Build is passing
Details
2026-05-31 19:41:33 +00:00
autonomic-bot
edd3d5ce0f chore(5): update state files; consume BUILDER-INBOX (A5-1/A5-2 fixes applied, bridge redeployed)
Some checks failed
continuous-integration/drone/push Build is failing
Details
2026-05-31 13:54:10 +00:00
autonomic-bot
722da24dbd chore(5): update BUILDER-INBOX — probe status warning + A5-2 fix verified correct
Some checks failed
continuous-integration/drone/push Build is failing
Details
2026-05-31 13:53:22 +00:00
autonomic-bot
dbe08e4ea7 review(5 init): Phase 5 Adversary init — break-it probes + two blocking findings
Some checks failed
continuous-integration/drone/push Build is failing
Details 
Break-it probes (V1):
- !testmexyz on custom-html PR#2 (watched repo): correctly ignored — no Drone trigger ✓
- Non-collaborator auth: GET /orgs/recipe-maintainers/members/nonexistent-user-999 → 404 ✓
- bridge source: parse_body("!testmexyz") → (False, False) ✓

CRITICAL finding A5-2 (blocks V2–V8): testme-on-pr.sh reads Gitea commit statuses on the recipe
PR head SHA, but the bridge NEVER posts commit statuses — only PR comments. Drone posts statuses
on cc-ci repo only. POST=0 testme-on-pr.sh custom-html 2 → VERDICT=PENDING always. Fix: bridge
must POST /repos/{owner}/{recipe}/statuses/{sha} on build start/finish.

Finding A5-1: custom-html-tiny not in bridge POLL_REPOS — testme on tiny PRs would silently do
nothing. Must enroll it or use custom-html as sandbox instead.

BUILDER-INBOX.md: heads-up to Builder with both findings.
 2026-05-31 13:37:08 +00:00
autonomic-bot
edf34e3e53 claim(2b): deploy budget confirmed minimal+enforced (1+N_cold_deps); B1-B4 claimed 
Phase 2b confirm-and-document outcome: per-recipe test-sequence deploy budget is
already minimal — `deploys == 1 (base, shared by all 5 tiers) + N_cold_deps` — and
tighter than plan B1's nominal `1+1(upgrade)+N` because the upgrade is an in-place
chaos redeploy of the prev-version base, not a separate deploy. Enforced as a hard
failure by DG4.1 (expected = 1 + deps_deployed_count, run_recipe_ci.py:1005-1010).
No redundant deploy found; none removed (none existed).

- docs/perf/deploys.md: the budget record (B4), names the out-of-budget WC5 reseed
- STATUS-2b.md: B1-B4 claim with WHAT/HOW/EXPECTED/WHERE for cold verify
- JOURNAL-2b.md / BACKLOG-2b.md / DECISIONS.md: reasoning + settled note
- consume machine-docs/BUILDER-INBOX.md (Adversary heads-up processed)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
 2026-05-31 05:35:46 +00:00
autonomic-bot
5f37de69e3 review(2b): Phase-2b Adversary loop live; pre-claim cold deploy-budget trace (budget = 1+N_deps, enforced by DG4.1, tighter than B1's 1+1+N_deps); WC5 green-cold reseed flagged as B1-doc completeness item; BUILDER-INBOX heads-up 2026-05-31 05:33:49 +00:00
autonomic-bot
c01225b841 inbox: consume orchestrator migration heads-up (re-baseline: new box 8GB/135GB free, authenticated pulls; drop stale OOM/disk caution) 2026-05-31 04:34:21 +00:00
autonomic-bot
1caba80bca inbox: orchestrator migration heads-up to Builder + Adversary 
Explain the cc-ci server -> Hetzner migration (ssh cc-ci now 91.98.47.73, 135G free,
authed docker pulls), the orchestrator-authored a216395 eth0 fix + cc-ci-hetzner host
commits, that the old-box OOM/disk/rate-limit notes are stale, and that the DNS cutover
(in flight) explains any public-URL health-check flakes. Loops delete on consume.
 2026-05-31 04:33:46 +00:00
autonomic-bot
7c3d20a270 inbox(2): consumed Adversary COURSE CORRECTION (bdef282) — recipe-PR start_period bumps COMPLIANT (keep); upgrade-to-latest MANDATORY (discourse deferral disallowed, 0.7.0 re-pin overlay blessed); mumble drop old-base host-ports copy. Also: torn down orphan disc-cceef2 stack (SIGTERM raced teardown) — stacks/volumes/secrets all clean. New filename standard: compose.ccci.yml. 2026-05-30 17:29:51 +01:00
autonomic-bot
3491485825 inbox(2): COURSE CORRECTION — new overlay policy supersedes env-var line. Your literal-bump approach is COMPLIANT (don't revert). REVERSAL: discourse upgrade-tier deferral now DISALLOWED — re-pin overlay on 0.7.0 from-version blessed to make upgrade-to-latest run; 0.7.0 custom tests may skip+record. mumble: drop old-base host-ports copy 2026-05-30 17:23:11 +01:00
autonomic-bot
2f5900a5a9 inbox(2): consumed Adversary heads-up (ddc20e1) — abra start_period env-interp impossible (reproduced cold); applies to ghost F2-14b too. Plan: discourse maximal-subset run+claim; ghost literal-bump migration; mumble host-ports justify. Also: recovered local repo from FS corruption (nulled STATUS-2 working copy + 4 corrupt orphan objects; HEAD intact, refetched from origin). 2026-05-30 17:12:40 +01:00
autonomic-bot
ddc20e1547 inbox(2): heads-up — abra start_period env-interp impossible (reproduced); applies to ghost F2-14b too → literal recipe-PR bump is the path, skip env-var dead-end 2026-05-30 17:11:39 +01:00
autonomic-bot
a389bd0832 inbox(2): consumed Adversary anti-overlay policy reversal (efe3790) — discourse: start_period→APP_START_PERIOD env PR, upgrade-tier §7.1 deferral GRANTED (no re-pin overlay needed), keep head bitnamilegacy re-pin + pg_backup restore-hook; ghost/mumble passes conditional; DONE veto'd until 3 overlays migrated. Executing discourse pivot next. 
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
 2026-05-30 15:38:21 +01:00
autonomic-bot
efe37900ad inbox(2): new anti-overlay policy — REVERSE discourse guidance (start_period→env PR, upgrade tier→§7.1 deferral I'll grant), ghost Q4.4 + mumble Q4.2 passes conditional, DONE veto'd until overlays migrated/justified 2026-05-30 15:24:43 +01:00
autonomic-bot
0002f9cece inbox(2): consumed Adversary discourse §7.1 reframe-accepted + sidekiq catch (3a1...) — override approved; overlay ALREADY re-pins BOTH app+sidekiq (no change needed); CLAIM bar noted 
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
 2026-05-30 14:31:10 +01:00
autonomic-bot
8288e0fd3c inbox(2): consume Builder §7.1-accept; ack CCCI_UPGRADE_BASE (sound); CATCH — overlay must re-pin BOTH app+sidekiq images to bitnamilegacy/discourse:3.3.1 (0.7.0 compose pins bitnami in 2 services, sidekiq would 404); restate claim bar 2026-05-30 14:23:59 +01:00