Skip to content

fleet infra: laptop /home at 100% (5.6M free) — cargo verification fails with os error 28 #3372

Open

Description

@dezren39

Fleet infra — laptop (amd-6) /home is 100% full; local build/test verification is broken.

Evidence (2026-11-01 ~06:28Z, queue task 5073 shift, via ~/tools/laptop-ssh.sh):

  • df -h /home/user: /dev/nvme0n1p2 3.3T 3.2T 5.6M 100% /home
  • cargo test --lib petname in a fleet worktree (~/git/fleet/5073/pkgs/id) failed across many crates with No space left on device (os error 28) writing to target/debug/deps — a disk failure, not a test failure. PR fix(id): petname skeleton — capital-I class and 8->b, labels() skeleton collisions (#2069) #3360 was merged on other verified evidence (Codex re-review clean); this issue is about the verification capability, not that PR.

Impact: every fleet lane that verifies on the laptop (the standing rule: builds/tests run on the laptop or CI, never the sandbox) can silently lose its local verification path; failures look like compile errors unless the os error 28 line is spotted.

Acceptance:

  • Identify the top space consumers under /home (du report attached to this issue).
  • Free space safely — candidates named explicitly before any removal; no recursive/wildcard deletes of shared trees (standing delete guardrail); Drew approves anything not obviously disposable (stale target/ dirs in dead worktrees, caches).
  • Confirm with a fresh df (<90%) and one successful targeted cargo test in a fleet worktree.
  • If a recurring consumer is found (e.g. unbounded target/ growth across ~/git/fleet worktrees), add a bounded cleanup or alert so this is caught before 100%.

Activity

  1. added
    kind/bugSomething isn't working (prefixed form of the classic bug label)
    priority/normalOrdinary priority (the default)
    on Nov 1, 2026
  2. dezren39 commented on Nov 1, 2026

    @dezren39
    MemberAuthor

    Update 2026-11-01 ~06:40Z (lane D, task 2663 shift): fresh df -h /home on the laptop now shows /dev/nvme0n1p2 3.3T 2.0T 1.2T 63% — ~1.2T free, recovered from 5.6M free at 06:28Z. Cause of the recovery is unknown to this lane (no cleanup was run by this shift). The 100%-full observation and the os error 28 cargo failures at 06:28Z were real; the remaining acceptance is the root-cause / recurring-consumer item — what filled it and what consumed/freed ~1.2T — so the next fleet infra pass can prevent a recurrence.

  3. dezren39 commented on Nov 1, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · update

    • Agent: queue worker (repo-worker-code), lane A
    • Session / ID: queue task 4925, repo-queue-worker-shift lane A 2026-11-01 01:04 CDT
    • Found via: hit the same disk-full during task 4925 verification, then observed recovery
    • Update: At 06:23Z a write in the fleet worktree failed with ENOSPC and df showed /home 100% (0 free), matching this issue. At ~06:25Z the laptop's ~/.local/share/Trash (measured 1.2T minutes earlier) was emptied — not by this lane — and df -h /home at 06:25Z showed 63% used / 1.2T free. Laptop builds/tests then ran fine (bun suite executed 06:27–06:30Z). The immediate blockage has cleared; the underlying cause (Trash growing to 1.2T) remains worth addressing, so leaving the issue open for Drew's call on trash retention/purge policy.
  4. added
    queue/queuedHas a queued task in the Supabase agent queue
    source/creatorFiled by the new-issue-creator job
    task/triageQueue packet kind: verify, reproduce, and route this item
    on Nov 3, 2026
  5. developing-today commented on Nov 3, 2026

    @developing-today
    Contributor

    agent-note:v1
    state: triaged (coverage pass)
    Coverage pass 2026-11-03: reviewed in the fleet-wide per-issue pass (drift / overlap / already-handled / stale / blockers / ordering). Verdict: still live; queued in repo-health-code-pilot as triage at priority 40 (priority/normal). If this is already handled at current main, the triage closes it with evidence; if it needs splitting, the triage files the split.
    Found via: coverage pass 2026-11-03

  6. added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 3, 2026
  7. 58 remaining items

  8. added
    queue/queuedHas a queued task in the Supabase agent queue
    and removed
    work/assignedQueue worker lifecycle state
    on Nov 8, 2026
  9. dezren39 commented on Nov 8, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

    • Agent: fleet monitor
    • Session / ID: task 13577 (repo-fleet-monitor run 2026-11-08 16:12 CST)
    • Found via: monitor reconciliation
    • Task: Claim evaporated — task 13577 is queued and unclaimed (no live lease) while the issue still carried claimed labels. Labels reset to the truth: queue/queued + status/needs-triage. Checkpoint stage at evaporation: triage_verification_running.
    • Expectation: s — a lane re-claims task 13577 and posts a fresh pickup note.
    • Links: task 13577
  10. added
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 8, 2026
  11. dezren39 commented on Nov 8, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · state: picked up

  12. dezren39 commented on Nov 8, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · state: done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

app/idPackage/app: id (pkgs/ or apps/ in this repo)kind/bugSomething isn't working (prefixed form of the classic bug label)priority/normalOrdinary priority (the default)source/creatorFiled by the new-issue-creator jobstatus/triagedTriaged and routed (see agent note)task/triageQueue packet kind: verify, reproduce, and route this item

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions