Split tutorial CI into multiple jobs #375
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Tutorials tend to take a lot of time. Splitting the CI into multiple jobs, one per tutorial, should make this faster. This also makes it easier to catch dependency errors in the tutorials; for instance, this PR revealed two tutorials were missing tqdm installation.
Since this does introduce many more jobs, we also cut back on regular test jobs, only running on 3.11 instead of 3.8-3.11. We do this as several other jobs like pin and benchmarks already run on Python 3.8, so it is less essential to test on 3.8 again. Furthermore, we have never found errors in only the intermediate versions (between lowest supported and highest supported).
TODO
Questions
Status
CONTRIBUTING.md
yapfpytestpylintHISTORY.md