A spec-test attempt discarded at 22 min for an npm install the brief forbids, then a cold retry and a merge conflict on the shared vitest config line #384
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What happens
agent.write-spec-tests[game-presentation]in run 172 took 40 min for 14 tests. Attempt 1 reasoned "Infrastructure work (allowed: ... dependencies into manifests)", the opposite of the brief ("When a test needs more (a dependency...), leave that test out"), rannpm install -D jsdom @testing-library/...at 12.6 min, spent 2.5 min debugging jsdom'slocalStorageunder Node 26, and was rejected bytests-onlyat 22.2 min forpackage.json/package-lock.json. Attempt 2 opened in a new session and spent 10 min re-reading everything, then rewrote all four files DOM-free with a 168-line regex-over-HTML helper. Then a merge conflict: game-rooms had added*.test.tsand presentation*.test.{ts,tsx}to the same line ofvitest.config.ts(1.1 min).Fix
npm install/uv pip installand edits to manifests in a tests-only step), instead of discovering them at the end.*.test.{ts,tsx}) and a Node 26localStorageshim in the scaffold the apply step writes, so parallel test steps stop editing the same line.Done when
A tests-only step cannot spend 20 min on a change its check will reject, and a retry starts from what the first attempt read. ~32 min on run 172 (braid#376 covers what the tests should be).
From the run 172 transcript review (Scratch on vLLM + MTP k=4, 2026-11-04; report in the owner's
~/repos/vLLM/reports/). Related: braid#378, braid#379.Shipped in PR #390, production
ddd4b6b.Evidence:
tests/agent/test_path_guard.py, and simspec-tests-edit-restorednow expects the fork. None of the three Free replays of the spec-test step tried to add a dependency, so the refusal did not fire there and rests on its test.