Flaky test: CoderOauthService > startDesktopFlow > clears the previous catalog and never probes catalogs when the listing is forbidden (src/node/services/coderOauthService.test.ts).
Seen: Test / Unit (1/6), run 37483574408, job 112337902541, on PR #5736 head 203b95a8e6. That PR changes only two files under tests/bugbash/repros/, which the unit lanes do not run.
Failure: error: waitUntil: condition not met within timeout at coderOauthService.test.ts:96, after 2006 ms. The helper polls with a fixed 2 s budget. The other 100 tests in the file passed, and the test passed 5 of 5 locally on the same commit. The last 30 pr.yml runs on main were green.
Likely cause (not verified): the test waits on a condition with a wall-clock timeout instead of an explicit completion signal, so a loaded runner can exceed 2 s.
Fix idea: wait for the flow's own completion signal (or the awaited promise) instead of waitUntil with a fixed timeout.
Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high
Flaky test:
CoderOauthService > startDesktopFlow > clears the previous catalog and never probes catalogs when the listing is forbidden(src/node/services/coderOauthService.test.ts).Seen:
Test / Unit (1/6), run 37483574408, job 112337902541, on PR #5736 head203b95a8e6. That PR changes only two files undertests/bugbash/repros/, which the unit lanes do not run.Failure:
error: waitUntil: condition not met within timeoutatcoderOauthService.test.ts:96, after 2006 ms. The helper polls with a fixed 2 s budget. The other 100 tests in the file passed, and the test passed 5 of 5 locally on the same commit. The last 30pr.ymlruns on main were green.Likely cause (not verified): the test waits on a condition with a wall-clock timeout instead of an explicit completion signal, so a loaded runner can exceed 2 s.
Fix idea: wait for the flow's own completion signal (or the awaited promise) instead of
waitUntilwith a fixed timeout.Generated with
xum• Model:anthropic:claude-opus-5-5• Thinking:high