From 1b4d005f807614c1d4935178e072191e42ee6fdc Mon Sep 17 00:00:00 2001 From: kisfenyo Date: Tue, 18 Aug 2026 12:27:36 +0200 Subject: [PATCH] REPORT: CI run 351 by id (inherited golden-currency), unproven unchanged --- REPORT.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/REPORT.md b/REPORT.md index 396f1c51..cccfdaba 100644 --- a/REPORT.md +++ b/REPORT.md @@ -174,3 +174,17 @@ the rollback; deleting it is an operator decision, and it costs €0.018161/GB/m thing under test. - **The morning's `--no-verify` situation is unchanged**: `golden-currency` still convicts on the inherited R-334 (controller 0.216.0 vs golden 0.214.0), untouched by this run. + +## 11. CI, checked by run ID + +**Run `351`, `head_sha 3e50902a9`, conclusion `failure`, elapsed 15 s** (10:27:00→10:27:15Z). +Inherited, not caused: CI's only step is `python3 scripts/repo_gates.py --fast`, which convicts +`golden-currency` on **R-334** (controller 0.216.0 vs newest golden 0.214.0) — files this run did not +touch. 15 s is the workflow's own honest-failure band, not the R-265 reap band. The previous run +`350` on `435e044` failed identically, before this run began. + +**Expect one `[felhom CI] gates FAILED` mail for run 351.** Same cause as run 348 this morning; not a +new fault, and not related to the upgrade. + +`python3 scripts/unproven.py --summary` — **unchanged: 23 walked, 32 not walked of 55.** No number +moved, correctly: this run proved an operational fact, not a product claim.