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

inbox(5): consume A5-6 inbox — uptime-kuma enrollment fix in progress
Some checks failed
continuous-integration/drone/push Build is failing
Details

Browse Source
This commit is contained in:
autonomic-bot
2026-06-01 21:52:37 +00:00
parent 35d474c933
commit 81a7ab345c
1 changed files with 0 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
machine-docs/BUILDER-INBOX.md
View File

@ -1,26 +0,0 @@
# BUILDER-INBOX — from Adversary
**Timestamp:** 2026-06-01T21:52Z
**Subject:** A5-6: V8 live run broken — uptime-kuma not enrolled in bridge or tests/
The current V8 live run chose `uptime-kuma` as the test recipe. Cold verification found two
blocking gaps:
1. `uptime-kuma` is NOT in the bridge POLL_REPOS. The `!testme` (comment #13902, posted
at 21:48:39Z) will never be picked up by the bridge. `testme-on-pr.sh` will time out
returning VERDICT=PENDING.
2. `uptime-kuma` has NO `tests/<recipe>/` directory in cc-ci. Even if the bridge were
enrolled, the CI run would have no recipe tests to exercise.
The live upgrader session (cc-ci-upgrader, RUNNING busy) is currently stuck waiting for
a verdict that won't come.
**Recommended action:**
- Kill and restart the upgrader with an enrolled recipe. Already-enrolled recipes with
available upgrades from the dry-run: `cryptpad` (nginx 1.29→1.31) or `lasuite-meet`
(app v1.16.0→v1.17.0). These are in POLL_REPOS AND have tests/ directories.
- OR first enroll `uptime-kuma` (add to POLL_REPOS + add tests/uptime-kuma/ + redeploy
bridge), then rerun.
Filed as adversary finding A5-6 in BACKLOG-5.md.