When the repository gate is red on the base branch, every task for that repository runs its own baseline-fix agent against the same red baseline. 25 baseline-fix runs happened in one day for one repository, 24 tasks parked on the same failure and two more were still running a fix at the time of the snapshot (one at 4.9M tokens). Total about 8.3M tokens on parked tasks plus the running ones, all for one identical verdict.
The parked reason also carries about 30 lines of go: downloading ... ahead of the actual error, so the cause sits at the bottom of the text.
Done when
A red baseline is evaluated and fixed once per repository revision; other tasks for that revision wait on or reuse that verdict instead of starting their own fix agent.
The recorded gate output drops package-download progress lines so the failing command is first.
Verified by a test that two tasks at one revision start one baseline fix.
## What is wrong
When the repository gate is red on the base branch, every task for that repository runs its own baseline-fix agent against the same red baseline. 25 `baseline-fix` runs happened in one day for one repository, 24 tasks parked on the same failure and two more were still running a fix at the time of the snapshot (one at 4.9M tokens). Total about 8.3M tokens on parked tasks plus the running ones, all for one identical verdict.
The parked reason also carries about 30 lines of `go: downloading ...` ahead of the actual error, so the cause sits at the bottom of the text.
## Done when
- A red baseline is evaluated and fixed once per repository revision; other tasks for that revision wait on or reuse that verdict instead of starting their own fix agent.
- The recorded gate output drops package-download progress lines so the failing command is first.
- Verified by a test that two tasks at one revision start one baseline fix.
Fixed in d11a0cd2. The daemon now keeps a claim per repository, revision and gate command (worktreerpc, in memory). The first task to see the red baseline runs the baseline-fix agent. Other tasks wait on it and then park with its verdict, either its failure or 'repaired on task N's branch, retry after merge', without starting an agent. A claim that never reports back expires after 1h and a finished verdict after 15m. Gate output now drops go: downloading/finding/extracting lines before it is stored or sent to the builder, so the failing lines lead. Test: TestRedBaselineIsRepairedByOneTask (table; fails 3/3 with the ledger bypassed), task check passes.
Fixed in d11a0cd2. The daemon now keeps a claim per repository, revision and gate command (worktreerpc, in memory). The first task to see the red baseline runs the baseline-fix agent. Other tasks wait on it and then park with its verdict, either its failure or 'repaired on task N's branch, retry after merge', without starting an agent. A claim that never reports back expires after 1h and a finished verdict after 15m. Gate output now drops go: downloading/finding/extracting lines before it is stored or sent to the builder, so the failing lines lead. Test: TestRedBaselineIsRepairedByOneTask (table; fails 3/3 with the ledger bypassed), task check passes.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What is wrong
When the repository gate is red on the base branch, every task for that repository runs its own baseline-fix agent against the same red baseline. 25
baseline-fixruns happened in one day for one repository, 24 tasks parked on the same failure and two more were still running a fix at the time of the snapshot (one at 4.9M tokens). Total about 8.3M tokens on parked tasks plus the running ones, all for one identical verdict.The parked reason also carries about 30 lines of
go: downloading ...ahead of the actual error, so the cause sits at the bottom of the text.Done when
Fixed in
d11a0cd2. The daemon now keeps a claim per repository, revision and gate command (worktreerpc, in memory). The first task to see the red baseline runs the baseline-fix agent. Other tasks wait on it and then park with its verdict, either its failure or 'repaired on task N's branch, retry after merge', without starting an agent. A claim that never reports back expires after 1h and a finished verdict after 15m. Gate output now drops go: downloading/finding/extracting lines before it is stored or sent to the builder, so the failing lines lead. Test: TestRedBaselineIsRepairedByOneTask (table; fails 3/3 with the ledger bypassed), task check passes.