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

review(2): Q4.7 plausible §4.3 floor NOW FIRST-HAND GREEN — my cold run (adv-plausible-cold2) install+custom pass, deploy-count=1, BOTH *_event_roundtrip PASSED (ClickHouse events_v2 read-back), clean teardown; prior readiness-404 was a transient ClickHouse-boot flake; Q4.7 first-hand-evidence obligation CLEARED; note: ClickHouse boot intermittently flaky 1/2 on single node

Browse Source
This commit is contained in:
autonomic-bot
2026-05-30 04:08:04 +01:00
parent 1770b0c3e6
commit 71af595915
1 changed files with 23 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
machine-docs/REVIEW-2.md
View File

@ -1714,3 +1714,26 @@ round-trips cleanly (a genuine recipe difference from the postgres recipes, born
**Isolation note:** verdict from the plan (P1–P8) + the test code (_p4.py / ops.py / test_{restore,
backup,upgrade}.py / functional/{test_account_and_post,test_session_auth}.py) + the STATUS Gate-Q4.3
verification info + my own cold full-lifecycle run. JOURNAL-2 not consulted before this verdict.
## Q4.7 plausible — §4.3 floor NOW FIRST-HAND GREEN (break-it probe, my cold run) @2026-05-30T02:05Z
Settled my OWN long-pending first-hand confirmation (the prior `/root/adv-q47-plausible-cold.log` had
FAILED at install readiness — `/api/health` 404, a transient ClickHouse-boot miss). Re-ran cold from
`/root/adv-verify`: `RECIPE=plausible PR=0 STAGES=install,custom cc-ci-run runner/run_recipe_ci.py`
→ `/root/adv-plausible-cold2.log`. This time ClickHouse (events_db) booted and the run is GREEN:
- RUN SUMMARY: `deploy-count = 1`; `install : pass`, `custom : pass`.
- `tests/plausible/functional/test_event_tracking.py::test_pageview_event_roundtrip PASSED` (53s) +
`::test_custom_event_roundtrip PASSED` — the genuine create-event→ClickHouse-`events_v2`-read-back
on a unique pathname (non-vacuous; a broken ingestion path raises→FAILS). `test_plausible_root_serves
PASSED`. Clean teardown: post-run no plau stack; 0 plau secrets/volumes/networks.
- (The prepull `service "app" depends on undefined service "events_db"` warning is benign — it's the
prepull config-probe, which doesn't include the events compose file; the real deploy includes it and
ClickHouse booted, as the 53s read-back tests prove.)
**Upgrade to my Q4.7 verdict:** the §4.3 event-roundtrip FLOOR is now confirmed GREEN by my own cold
run, not just Builder logs — the earlier readiness 404 was a transient ClickHouse-boot flake, not a
structural failure. Q4.7's only open item (first-hand green evidence) is CLEARED. Plausible's full
upgrade/backup/restore tiers were not in this scoped run (install,custom only) — P4/upgrade for
plausible still ride the normal gate path if/when claimed; this probe targeted the §4.3 floor that was
my standing obligation. No VETO. NOTE: ClickHouse boot is intermittently flaky on the single node
(1-in-2 here) — a real env-fragility worth a retry/readiness margin if plausible runs go in CI rotation.