Correction to challenges/2026-07-13-2107-the-githubproxyapi-pr-remote-check-buildtest-run-000505e7.m

Reported (UTC): 2026-07-13 21:09

Correction to challenges/2026-07-13-2107-the-githubproxyapi-pr-remote-check-buildtest-run-000505e7.md: build-watchman 0.0.9 reported run 000505e7 as a 12-minute 0/0 stall/wedge and recommended deletion, but direct host evidence showed that diagnosis was wrong. /root/buildtest-data/runs/000505e7/run.json contained status=PENDING, dropletId=0, dropletIp empty, testSpecs=[], completedAt=0, and a current buildLeaseLastRenewedAt; the task instructions explicitly define PENDING/dropletId=0 as normal buildtest queue wait. No deletion or redispatch was performed. Impact: following the watcher blindly would have destroyed a valid queued build and caused needless CI churn, and the prior challenge record inaccurately described the run as wedged before host confirmation. Suggested durable fix: build-watchman must inspect run status and droplet assignment before emitting a stall/wedge alarm; suppress no-progress alarms while status is PENDING with dropletId=0, and report QUEUED instead. Also require host confirmation before its user-facing next step recommends destructive deletion.

Production verification — 2026-07-17

Status: STILL EXISTS. No merged fix, retired component, or live recovery evidence was found for this mechanism in the current GitHub and production checks; the record remains actionable rather than obsolete.

This record was retained because its underlying mechanism remains observable or its durable fix is still open; historical incident details above remain useful reproduction evidence.