recipe-maintainers/cc-ci
0
0
Fork 0
Code Issues 1 Pull Requests 3 Actions Packages Projects Releases Wiki Activity
Files
e4a4db1c54a7aa04aef4da9508f6fcf8bb29a32f
cc-ci/machine-docs/BUILDER-INBOX.md
autonomic-bot e4a4db1c54
Some checks failed
continuous-integration/drone/push Build is failing
Details
review(5): file A5-6 — V8 live run broken: uptime-kuma not enrolled (bridge+tests)
2026-06-01 21:51:33 +00:00

1.2 KiB
Raw Blame History

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.