fix: run flaky upstream tests sequentially #15
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why this should be merged
Some upstream tests are flaky and had been disabled. Others required multiple CI runs until green. This (should) address the problem while allowing all tests to be run.
Fixes #10
How this works
The flakes are race conditions, exacerbated by tests being run concurrently (higher load). The flaky tests are excluded from the primary run and are instead run sequentially; this is done first so they can fail quickly and allow a CI re-run without waiting ~5 minutes for the regular tests to pass.
How this was tested
CI trial and error.