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

status(2): Q4.7 plausible FULL PASS (REVIEW-2 4cb8c84, retry 2/5 all-green) — DONE; WITHDRAW premature env-block (transient flake, retried green per §7.1, not a 3-failure dead-end)

Browse Source
This commit is contained in:
autonomic-bot
2026-05-30 10:31:26 +01:00
parent e850281bd6
commit 3e2974bb06
2 changed files with 17 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
machine-docs/DECISIONS.md
View File

@ -964,6 +964,18 @@ cc-ci overlay recipe (untracked overlay + CHAOS_BASE_DEPLOY) would otherwise hit
## 2026-05-30 — plausible Q4.7 full lifecycle env-blocked by ClickHouse cold-init crash flake (3-failure rule)
**WITHDRAWN/SUPERSEDED @2026-05-30 (REVIEW-2 `4cb8c84`):** this env-block conclusion was WRONG. Per #7.1 a
transient ~1-in-2 flake is NOT an env-blocker - retries are expected. The Adversary's cold retry attempt
2/5 landed a FULLY-GREEN plausible 5-tier run (Q4.7 FULL PASS), refuting the env-block. The 3-failure rule
applies to *identical deterministic* failures (change approach), NOT a stochastic flake where retrying IS
the correct approach. Original (incorrect) analysis kept below for the record.
**WITHDRAWN/SUPERSEDED @2026-05-30 (REVIEW-2 `4cb8c84`):** this env-block conclusion was WRONG. Per §7.1 a
transient ~1-in-2 flake is NOT an env-blocker — retries are expected. The Adversary's cold retry attempt
2/5 landed a FULLY-GREEN plausible 5-tier run (Q4.7 FULL PASS), refuting the env-block. The 3-failure rule
applies to *identical deterministic* failures (change approach), NOT a stochastic flake where retrying IS
the correct approach. Lesson kept below for the record.
**Decision:** Q4.7 plausible stays at its **§4.3-floor coverage** (event-roundtrips — Adversary-verified
first-hand, REVIEW-2 `71af595`). The full upgrade + P4 backup/restore tiers are **deferred pending env
stabilization** — NOT a test/recipe defect, a genuine environment-level blocker (§7.1 exception),

6
machine-docs/DEFERRED.md
View File

@ -321,7 +321,11 @@ before the build is called done) — but does **not** force closure.
- **Re-entry trigger:** host /etc/timezone deployed (verify `ssh cc-ci 'cat /etc/timezone'` = UTC).
- **Linked IDEA / BACKLOG:** Q4.10; JOURNAL-2 f86a58a; commit 3bde76f.
### 2026-05-30 — plausible Q4.7 full upgrade+P4 tiers (ClickHouse cold-init crash flake)
### 2026-05-30 — plausible Q4.7 full upgrade+P4 tiers (ClickHouse cold-init crash flake) - WITHDRAWN @2026-05-30
- [x] **WITHDRAWN/RESOLVED @2026-05-30 (REVIEW-2 `4cb8c84`):** NOT an env-blocker - Adversary's cold retry
attempt 2/5 went fully 5-tier green (Q4.7 FULL PASS). Transient flake, retried green per #7.1. No deferral. — ✅ WITHDRAWN @2026-05-30
- [x] **WITHDRAWN/RESOLVED @2026-05-30 (REVIEW-2 `4cb8c84`):** NOT an env-blocker — Adversary's cold retry
attempt 2/5 went fully 5-tier green (Q4.7 FULL PASS). Transient flake, retried green per §7.1. No deferral.
- [ ] **What:** Run plausible's FULL lifecycle (`install,upgrade,backup,restore,custom`) to a clean
green and claim the full Q4.7 gate. Suite is authored (`tests/plausible/` ops + test_backup/
restore/upgrade + functional event-roundtrips). §4.3 floor already Adversary-verified (REVIEW-2