Development record
TestHandBackPushesToWIPBranchThroughTheHook missed its first push twice in three runs while the machine's load was about 128 just after a reboot: origin held nothing on the work-in-progress branch. The test printed none of hand-back's output then, so the cause is unknown; 31 later runs at load 20 to 50 passed. The test now prints hand-back's output when that push misses, so a recurrence shows its cause.
issueresolvedminoriss-2610161458469092
TestHandBackPushesToWIPBranchThroughTheHook missed its first push twice in three runs while the machine's load was about 128 just after a reboot: origin held nothing on the work-in-progress branch. The test printed none of hand-back's output then, so the cause is unknown; 31 later runs at load 20 to 50 passed. The test now prints hand-back's output when that push misses, so a recurrence shows its cause.
Grounds
- pursued: a work-in-progress push no longer fails on how tar reads its input; a recurrence would now print the read's own error in the refusal, which would show this wrong
Frontmatter
| id | iss-2610161458469092 |
|---|---|
| type | issue |
| lifecycle | resolved |
| severity | minor |
.abcd/work/issues/resolved/iss-2610161458469092-testhandbackpushestowipbranchthroughtheh.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2610170220118643TestHandBackScrubLeavesNoDomain failed once on the merge queue's macOS race run (Actions run 38991791855, 2026-10-17T02:10Z) for a docs-only pull request: the comment's 'Why the push failed' section carried the pre-push hook's refusal but no 'remote:' line, so the test stopped at cloud_handback_test.go:754 before checking the scrub. The same package's TestHandBackPushesToWIPBranchThroughTheHook has a recorded load-related miss (iss-2610161458469092); this is a second hand-back test whose push output arrives incomplete.