Bryan Helmkamp 2348a1e483 test(harness): use advisory locks for peer presence ... Replace PID-based liveness probing in `live_marker_count` with flock advisory-lock presence detection. Each test process opens `<session_root>/clients/<pid>` once, holds LOCK_SH for the lifetime of any live TestContext in the process, and releases it explicitly when `cleanup_session_root` fires at refcount zero. Reapers probe with LOCK_EX | LOCK_NB: success means the previous owner is gone (normal exit, panic, SIGKILL, or zombie — the kernel releases advisory locks at process exit in every case) and the stale marker is removed. Compared to the PID check this was replacing: - Handles PID recycling correctly (the new holder does not inherit the previous owner's advisory lock). - Handles zombies correctly without shelling out to `ps`. - Costs one open + one flock per peer, ~50 us on macOS. The marker handle is stored in a process-scoped `Mutex<Option<(PathBuf, File)>>` so it can be released and reacquired across the drop-to-zero / rise-from-zero cycles that `session_refs` already implements. Storing the path alongside the handle enables a debug assertion that the process never drifts between session roots. `ClientMarker` and its serde plumbing are removed; the marker file is now empty, its existence and lock state carrying the signal. Full workspace wall-clock after A+B+C: 13.3–13.6 s, down from 20–25 s on HEAD before the fix and comparable to the 14 s Friday baseline despite the intervening +85 tests. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-20 16:33:53 -04:00
..
crates	test(harness): use advisory locks for peer presence	2026-04-20 16:33:53 -04:00
packages/fabro-api-client	Merge remote-tracking branch 'origin/main'	2026-04-20 09:47:47 -04:00