Skip to content

Make the flaky fetchingStopsAtTheFirstFailure test deterministic - #29

Merged
scooper4711 merged 1 commit into
mainfrom
test/deterministic-file-status-failure
Oct 19, 2026
Merged

scooper4711 merged 1 commit into
mainfrom
test/deterministic-file-status-failure

Conversation

@scooper4711

Copy link
Copy Markdown
Owner

The test let c's failure (two requests, with the retry) race against d, e and f, which answered at once, so g was sometimes asked for. The test now holds d's lookup until it is canceled, so the failure always lands while d is running. It expects exactly a and b to be learned, c to be tried twice, and e never to be asked for. Passed 10 of 10 repeated runs; FileStatusFetcher is unchanged.

Closes #27

c fails only after a retry, two requests, while d, e and f answered at once, so at times they finished first and g was asked for. d's lookup now waits until it is canceled, so c's failure always lands while d runs, and the test expects exactly a and b, and no request for e. FileStatusFetcher itself was right: it returns what it learned before the failure.
@scooper4711
scooper4711 merged commit dc7066d into main Oct 19, 2026
2 checks passed
@scooper4711
scooper4711 deleted the test/deterministic-file-status-failure branch October 19, 2026 21:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fix the flaky fetchingStopsAtTheFirstFailure test

1 participant