Split Travis config into jobs #43
Open
Conversation
This file contains hidden or 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
Not worth the overhead of setting up the environment when each takes a few seconds to do the important part
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.
This should allow the CI to run faster by avoiding redundant stages across Python versions (no reason to run mypy, pylint, or coverage under each Python version, so just run once under nightly) and allow better parallelisation (e.g. running coverage in parallel with unit tests).
In practice it'll require fine tuning as each job has the overhead of setting up the environment (30+ seconds).
It's also quite fiddly as the jobs matrix isn't expanded over top-level python versions, so we have to do it manually with YAML aliases.