From dfa5c8b9eecf5ca85e27c24a36bc6317aa7aa065 Mon Sep 17 00:00:00 2001 From: autonomic-bot Date: Wed, 10 Jun 2026 04:47:19 +0000 Subject: [PATCH] journal(conc): M2(a) cancel-mid-run PASS evidence; (b) parallel runs triggered --- JOURNAL-conc.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/JOURNAL-conc.md b/JOURNAL-conc.md index b75c328..49a9777 100644 --- a/JOURNAL-conc.md +++ b/JOURNAL-conc.md @@ -62,3 +62,16 @@ All four commits: tests/unit 138 passed + lint PASS before each. Next: tests/con - cases 5-12 stub teardown_app (recording) — janitor probe/reap ordering is what's under test, not teardown internals (covered by Phase-1 e2e + M2 live checks). - M1 claimed at e8e52cf; full verification recipe in STATUS-conc.md (WHAT/WHERE/HOW/EXPECTED). + +## 2026-06-10 — M2: merge + live verification (a) + +- Merge: bb5eb3d (--no-ff) pushed; push build 266 (self-test lint+hello) SUCCESS. +- (a) cancel-mid-run: !testme on immich#2 → build 267 (custom) running on the NEW harness — + log shows the setsid/trap wrap + "== per-run ABRA_DIR: /var/lib/cc-ci-runs/267/abra =="; + lock /run/lock/cc-ci-app-immi-ad3e33...lock held by pid 636902; 4 immich services up. + Canceled via drone API 04:42:07Z (HTTP 200, build status "killed"). Result: harness pid + GONE (no leaked python — the old §8.1 gap is closed), immich services 0, volumes 0, + secrets 0, .env 0 — the SIGTERM funnel ran the run's own teardown (better than the plan's + minimum, which allowed the janitor to do the reaping). Lock RELEASED (lockfile present but + unheld — tidy-swept by the next janitor, to be observed during (b)). +- (b) triggered 04:46:53Z: !testme immich#2 (comment 14287) + plausible#3 (14288) in parallel.