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

review(2): CORRECTION — retract garbled host specifics in 977b01f dashboard probe (no /var/lib dir; dashboard pulls Drone builds API filtered by RECIPE); verified fact 'no recipe runs yet' + Q5/DONE criterion stand; rewrite inbox accurately

Browse Source
This commit is contained in:
autonomic-bot
2026-05-30 13:35:34 +01:00
parent a0e82f4a71
commit dd00934b4f
2 changed files with 44 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
machine-docs/BUILDER-INBOX.md Normal file
View File

@ -0,0 +1,16 @@
## @2026-05-30T12:35:34Z — Adversary heads-up (non-gate, CORRECTED): live dashboard shows no runs — settle before Q5/DONE
(Supersedes my earlier inbox note whose host specifics were garbled — disregard the "/var/lib/ccci-dashboard
0 records / mtime 06:01Z" details; those were wrong. Corrected below from dashboard/dashboard.py source.)
VERIFIED: `https://ci.commoninternet.net/` → HTTP 200, "no recipe runs yet". The dashboard
(dashboard/dashboard.py) is read-only and lists **Drone builds** for recipe-maintainers/cc-ci filtered by
the `RECIPE` param/message — so an empty page means no recent RECIPE-tagged Drone builds. Phase-2 recipes
were validated via host `cc-ci-run` (not `!testme`→Drone), so they don't appear; Phase-1's have aged out.
Not a veto, not blocking your discourse/plausible work. But before `## DONE` for Q5, please resolve ONE:
(a) drive the Phase-2 recipe set (or a representative sample) through the real `!testme`→Drone path so
the dashboard shows them (satisfies P1 "a full green `!testme` run" + D7 results-UX), OR
(b) put an operator-blessed statement in STATUS-2 that host `cc-ci-run` validation satisfies P1
(trigger is recipe-agnostic, proven once in D10) AND that an empty live dashboard is OK for DONE.
Flag your choice in STATUS-2 so I can sign the Q5/DONE handshake. Detail: REVIEW-2.md "## CORRECTION @2026-05-30T12:35:34Z".
— Adversary