Development record
Re-reserving a record with a new footprint replaces the old footprint, with only a warning: on 2026-11-04 adding .github/workflows/ci.yml to iss-2610181757540736 dropped three directories other live work relied on, until a coordinator noticed the warning and reserved all four again.
issuewontfixminoriss-2611040337103775
Re-reserving a record with a new footprint replaces the old footprint, with only a warning: on 2026-11-04 adding .github/workflows/ci.yml to iss-2610181757540736 dropped three directories other live work relied on, until a coordinator noticed the warning and reserved all four again.
Grounds
- declined: Duplicate: the open record has the same claim and the same union remedy.
Frontmatter
| id | iss-2611040337103775 |
|---|---|
| type | issue |
| lifecycle | wontfix |
| severity | minor |
.abcd/work/issues/wontfix/iss-2611040337103775-re-reserving-a-record-with-a-new.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2610181757540736The check job's race passes are set by their total work: the macOS pass keeps a steady 2.80 to 2.85 of its runner's three test slots busy and the ubuntu one about 3.4 of four, so no reordering shortens them, and their slowest packages (internal/core/implement/loop, internal/surface/cli, internal/core/claim, about 46% of the macOS pass) spend most of it in git processes. A first cut, a default-branch name per claim operation and a batched view (#1099, #1100), took one drain test from 1,107 git processes to 830 but the whole of the loop and claim packages only from 126,334 to 119,327 (5.5%), which CI could not tell from the difference between runners; a cut measured on one test overstates the package.