Skip some CI jobs to save resources #65
Closed
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.
This is a low-tech "hack" to save CI resources. I don't think we have a particularly strong dependency on Python version or OS, so it feels wasteful to test against the full matrix every time. Skipping some randomly still gives us an eventual guarantee that we'll catch an unlikely bug that e.g. only occurs on Windows on Python 3.9.
An alternative approach could be to randomly choose an OS, then run all Python versions with that OS for a single CI run (b/c I suspect we're more likely to break b/c of Python version instead of OS, but I don't really know).