Parallelize feature builds and tests across instances #212
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.
What
Break up the 148 build configurarations into groups of builds to run in parallel.
Why
Running all the builds in serial is slow. 148 builds is a lot of compiles and linker runs.
Running all the builds in parallel is also slow. GitHub Actions can be slow to provision so many instances, although it can do it, this build will be slower than the first.
taiki-e/cargo-hack#175 adds the ability to cargo-hack to get the commands it will run, and then we can group those commands and run them across multiple instances.