2.0 KiB
2.0 KiB
REVIEW — server regression canaries phase (Adversary ledger)
Phase: server regression canaries (codified E2E self-tests)
SSOT: /srv/cc-ci/cc-ci-plan/plan-server-regression-canaries.md
Adversary loop started: 2026-06-02T01:15Z
Repo: git.autonomic.zone/recipe-maintainers/cc-ci
Adversary clone: /srv/cc-ci/cc-ci-adv
D-gate verdicts
(None yet — Builder has not claimed any gate. Watching for STATUS-regression.md → Gate: CLAIMED)
Adversary findings
(None yet)
Break-it probes log
(Break-it probes will be recorded here as they are run)
Pre-orientation findings @01:17Z
Known-bad fixture confirmed present and working:
- Branch:
recipe-maintainers/custom-html:v5-stale-docroot(SHA71e7326a99bb) - Build #81 (run 3h ago): confirmed RED —
customstage FAIL; specifically:test_content_type_html_and_txt: FAIL —ccci-e0d6e804.txt Content-Type='application/octet-stream', expectedtext/plain- All other tiers (install/upgrade/backup/restore): PASS
clean_teardown=true,no_secret_leak=true
- Implication for regression suite DoD#3: the known-bad canary correctly produces RED; the regression test must assert this outcome AND must be shown to fail if the server returns green for it (false-green detection).
Good canaries:
custom-html-tiny: build #45 GREEN (SHA4bd8416a209f, 21h ago) — simple, fastlasuite-docs: multi-service stack with DEPS=["keycloak"], DEPLOY_TIMEOUT=900s — test exists at tests/lasuite-docs/
Infrastructure state:
- Bridge (
ccci-bridge_app): running, polling 20 repos every 30s ✓ - Drone exec runner: running ✓
- Dashboard: serving at ci.commoninternet.net ✓
- Builder hasn't started regression phase: no STATUS-regression.md yet
Notes:
- Mirror phase (plan-mirror-enroll-all-recipes.md) completed DONE at 2026-06-02T01:16Z.
- This phase starts fresh: no STATUS-regression.md or tests/regression/ yet.
- Watching for Builder to create STATUS-regression.md and begin work.