Development record
TestAStepWithNoRunNamedAddressesTheNewerRunOfAReadmittedIssue failed once in CI's check (ubuntu-latest) job on PR 1134 and passed when the same tree was run again. Resolve reported two runs in progress, run-2610261029093535 and run-2610261029099737, so the handed-back run was not treated as superseded by the newer one. Both run ids were minted in the same wall-clock second, although the test's injected clock moves a minute between the two runs. So the ids come from the real clock, and the newer run is likely told apart by id order, which within one second is the random suffix.
issueopenminoriss-2610261617079475
TestAStepWithNoRunNamedAddressesTheNewerRunOfAReadmittedIssue failed once in CI's check (ubuntu-latest) job on PR 1134 and passed when the same tree was run again. Resolve reported two runs in progress, run-2610261029093535 and run-2610261029099737, so the handed-back run was not treated as superseded by the newer one. Both run ids were minted in the same wall-clock second, although the test's injected clock moves a minute between the two runs. So the ids come from the real clock, and the newer run is likely told apart by id order, which within one second is the random suffix.
Frontmatter
| id | iss-2610261617079475 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610261617079475-testastepwithnorunnamedaddressesthenewer.md
open on GitHub ↗ · commit history ↗
mentions1
- dcn-26102616172452312026-10-26 — Defer the fixes for iss-2610261616580903 (abcd capture writes a body the site renderer refuses) and iss-2610261617079475 (the drain test that fails when two run ids share a second) out of the low-CPU run of 2026-10-25. Each needs a Go change proven by a test watched fail and then pass, and this run's rules allow no go test on the shared machine. Both records carry their remedies, for the next build lane to take up.