Repository navigation
fdev host hygiene: browser-run concurrency and /tmp headroom in the capacity probe, disk-backed test temp, dead-run /tmp cleanup #5240
Description
Parent Outcome: #4730
Work level: Delivery · Track: Active delivery · Intended Status: In progress
Owner
Root/fdev assigns.
Done when
From the 2026-11-02 progress report, process problem 4. On fdev the quiet-host bench probe never admitted for 60 minutes (load 5–9), /tmp (a 16 GB tmpfs) filled and caused 38 spurious SDD test failures, and many concurrent browser smokes ran.
-
scripts/fdev-lane-capacity.py(Process fixes from the 2026-11-01 progress report: load-ceiling lane admission, review-finding triage, push before stop #5172) holds when:- Browser runs: at least 2 browser-smoke runs are active. Classify a headless Chromium main process (Playwright or a CDP-driven
chromewith--headlessand--remote-debugging-*), not its renderer or GPU children. /tmpspace: free space on/tmpis below a threshold, default 3 GiB, reported separately from disk.
Both are configurable, with fixture tests in the existing style.
- Browser runs: at least 2 browser-smoke runs are active. Classify a headless Chromium main process (Playwright or a CDP-driven
-
Disk-backed test temp by default:
~/.local/bin/fdev-chromium-env, and documented guidance for .NET test runs, setTMPDIRto a disk path (for example~/.cache/fsgg-tmp) unless already set. Keep it short enough for Unix-socket paths (the SDD socket test failed under a long TMPDIR). Document it in the fdev ops doc. -
Dead-run cleanup, one owner: a script removes
/tmpandTMPDIRentries matching known harness patterns (fsgg-sdd-tests-<pid>-*,fsgg-gate-*, Playwright profile dirs) only when their PID is dead and they are older than 1 h, with a dry-run mode. It runs from the existing board-tend user units (fdev: board-tend user units, post-merge trigger, empty enable file and 7-day observation (Refs #5136) #5205) on a timer. Never delete a live run's files. -
Tests for the probe additions and the cleanup matcher (a fixture tree; live-PID dirs are kept).
Current deliverable
None.
Next action
Dispatch.
Blocked on
Nothing.
Acceptance evidence
None yet.
Activity
EHotwagner commentedon Nov 2, 2026
Root/fdev install of the merged #5242 (
acfe0b8d) on fdev, followingdocs/coordination/fdev-host-hygiene.md:~/.local/bin/fdev-chromium-envis kept asfdev-chromium-env.pre-5240.8cbc5e15…).fdev-chromium-env --print-tmpdirprints/home/developer/.cache/fsgg-tmp.fdev-tmp-cleanup.py(sha2566fcb5fe6…) plus thefsgg-tmp-cleanup.{service,timer}user units. The timer is enabled; its first run is 2026-11-02 08:38 CET, then hourly.apply_blocked: false, 0 unreadable processes.admit, browsers 0,/tmpfree 6.15 GiB.Acceptance pending: the first timer run's journal line. Root closes this after reading it back.
EHotwagner commentedon Nov 2, 2026
Root/fdev acceptance. The first live timer run (2026-11-02 08:38 CET) of
fsgg-tmp-cleanup.serviceended withResult=successand exit 0. Its JSON line:mode: apply,apply_blocked: false, 367 processes read;failed: 0;/tmpwent from 61% to 40% used (6.2 GB used, 9.6 GB free).Every Done-when item is met:
/tmpunder 3 GiB, verified live in review.TMPDIRviafdev-chromium-env, installed.Closing as completed. The non-blocking review notes are recorded in #5242's merge comment.