recipe-maintainers/cc-ci
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
0115e220d2acb9e37cc50ac46ced4d8fcc4e29e4
cc-ci/machine-docs/BACKLOG-ghost.md
autonomic-bot 383868212d
Some checks failed
continuous-integration/drone/push Build is failing
Details
review(ghost-M1+M2): M1 PASS + M2 PASS — build #612 post-proxy L5/5, PR#4 operator-ready 
M1 PASS @2026-06-13T06:38Z:
- !testme on PR#4 (d88f5801) triggered 06:12:48Z, post-proxy (fix at 05:38Z)
- Drone build #612 started 06:13:02Z (Drone sqlite DB), RECIPE=ghost REF=d88f5801
- results.json level=5, all stages pass; JUnit confirms genuine execution
- clean_teardown=True, no_secret_leak=True
- Pre-proxy failures (515/517/519/557) dated 2026-06-12 — infra-confounded

M2 PASS @2026-06-13T06:38Z:
- Exactly 1 open PR: PR#4 only
- PR#3 closed, PR#5 closed (Gitea API verified)
- No ghost stacks/services/volumes on cc-ci
- Operator comment at 06:22:11Z with 5-tier pass table + infra-confound analysis
- All adversary findings A1/A2/A3 resolved

Builder may write ## DONE.
2026-06-13 06:27:57 +00:00

1.5 KiB
Raw Blame History

BACKLOG — phase ghost

Build backlog

  • Inventory PR/branch/comment/build state — done (see STATUS-ghost.md)
  • Trigger fresh post-proxy !testme on PR#4 (d88f5801) — triggered 06:12Z, PASSED build #612 level 5/5
  • Watch run, collect logs — all 5 tiers passed
  • Document infra-confounded prior failures; operator comment posted on PR#4
  • Close PR#3 (superseded) — closed with comment
  • Close PR#5 (cfold probe artifact) — closed with comment
  • Claim M1 — CLAIMED 2026-06-13T06:35Z, awaiting Adversary PASS
  • Claim M2 — CLAIMED 2026-06-13T06:35Z, awaiting Adversary PASS

Adversary findings

  • [adversary] [A1] Build #585 must NOT be used as the "clean post-proxy pass" — it ran pre-proxy (03:59Z vs proxy fix at 05:38Z) and tested PR#5 (cfold probe), not PR#4. A genuine post-proxy !testme on PR#4 is required for M1. @2026-06-13T06:22Z — CLOSED: Builder used build #612 (post-proxy, 06:13Z), not #585. M1 PASS @06:38Z
  • [adversary] [A2] update_config.monitor is likely the root cause of upgrade timing failures — builds #557 and #578 both failed with UpdateStatus=paused, NOT VIP exhaustion. @2026-06-13T06:22Z — CLOSED: Build #612 passed post-proxy confirming infra-confound. Operator comment explains MySQL timing under load. M1+M2 PASS @06:38Z
  • [adversary] [A3] PR#5 (cfold probe) should be closed once PR#4 has its verdict — not the canonical upgrade. @2026-06-13T06:22Z — CLOSED: PR#5 closed (verified). M2 PASS @06:38Z