---
name: test-profile-pool-outgrows-the-disk-floor
description: "A cold nextest leg on hfenduleam wrote ~55 GiB past the 32 GiB floor read and filled the disk mid-suite — a 109 GB test-profile pool; treat the floor as a refusal line, not headroom, and reap before the nextest leg"
metadata: 
  node_type: memory
  type: project
  originSessionId: 0f1cd318-0505-4e70-8849-c30b62254099
  modified: 2026-09-07T01:56:50.241Z
---

Measured 2026-09-07 (W1 #249, tip 8d980fdf, hfenduleam): the driver's floor read before the
nextest leg said `free_gib=55` (floor 32) and PASSED; the test-profile build then grew the pool
`.worktrees/ws272-w1/target` to **109 GB** and the disk hit 0.5 GB free at test 1127/3026. The
suite died inside tests with `No space left on device` (git worktree add, temp homes), no
Summary line, and the driver could not even write `nextest.exit` — a VOID leg with 5 reds that
were all disk. `ws272-w0/target` (my finished W0 lane) sat beside it at 83.6 GB.

**Why:** `xtask disk-floor` is the same 32 GiB floor at every leg; it guards the CURRENT read,
not the leg's own footprint. A cold `nextest` of the four-package population costs ~60–70 GB on
top of the dev-profile prebuild, so a PASS at 55 GiB is a fill in waiting.

**How to apply:** before the nextest leg, want ~80 GB free, not 32: reap the previous lane's
pool first (classify: outbound kind, inbound reparse sweep, live procs by exe path, measure
before/after), or refuse the leg. Two lanes' pools on one box (~190 GB) is the shape that fills
a 250 GB drive. Infra fix belongs in INFRA-REGISTER (a per-leg floor; the nextest leg's own).
Related: [[kitsubito-remote-launch-traps]] (the Linux side has 400+ GB and never sees this).