From 536a3595b9bea0ff9238a7874bdec73cdb026a15 Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Wed, 10 Jun 2026 08:50:26 +0000 Subject: [PATCH] =?UTF-8?q?journal(conc):=20M2(c)=20PASS=20round=202=20?= =?UTF-8?q?=E2=80=94=20290+291=20both=20green,=20block=20line=20visible,?= =?UTF-8?q?=20zero=20leakage;=20(a)=20re-run=20triggered?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- JOURNAL-conc.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/JOURNAL-conc.md b/JOURNAL-conc.md index 11fe9a5..759e426 100644 --- a/JOURNAL-conc.md +++ b/JOURNAL-conc.md @@ -127,3 +127,17 @@ All four commits: tests/unit 138 passed + lint PASS before each. Next: tests/con secrets/server-envs all 0. Zero leakage. (d) satisfied by 287 (full green immich e2e on the final harness code). - (c) round 2 triggered 08:22:13Z: comments 14303+14304 on immich#2 (same domain immi-ad3e33). + +## 2026-06-10 — M2(c) PASS round 2 (builds 290+291) + (a) re-run triggered + +- (c) round 2: builds 290 (08:22:30→08:46:05) + 291 (08:22:33→08:49:23) BOTH success. + 291 log: "== app lock: another run of immi-ad3e33... in flight — waiting ==" at +1s, + "acquired" at +1411s = exactly 290's exit. Both: deploy-count = 1 (expect 1), level=4. + Slowness was an immich-ML healthcheck flake (Adversary cross-confirmed live via lslocks: + one holder pid 739163, one waiter pid 739341 on the same lock inode — serialization observed + in the kernel lock table); ML converged inside the 1500s window, both runs green anyway — + no clean re-run needed. +- After both: no harness procs (pgrep run_recipe_c[i] empty), 0 immi/plau services/volumes/ + secrets/server-envs. Unheld lockfile remains by design (tidy-swept at next janitor probe). +- (a) re-run on fixed harness: !testme immich#2 comment 14307 @08:50:02Z; will cancel mid-run + via drone API once the deploy is in flight, then check pid/lock/leakage + janitor reap.