Switch to 1 job per Bitcoin integration test, overcoming the GitHub Action matrix limit of 256 - #7526
Open
dhaney-stacks wants to merge 8 commits into
Open
Switch to 1 job per Bitcoin integration test, overcoming the GitHub Action matrix limit of 256#7526dhaney-stacks wants to merge 8 commits into
dhaney-stacks wants to merge 8 commits into
Conversation
…se the batch size for all other jobs
…, might speed up builds" This reverts commit b571a52.
dhaney-stacks
changed the title
Coverage Report for CI Build 32521656103Coverage decreased (-0.03%) to 86.58%Details
Uncovered ChangesNo uncovered changes found. Coverage Regressions160 previously-covered lines in 31 files lost coverage.
Coverage Stats
💛 - Coveralls |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
Switch to 1 job per Bitcoin integration test, overcoming the GitHub Action matrix limit of 256
Applicable issues
N/A
Additional info (benefits, drawbacks, caveats)
Some of our integration tests are pretty consistently slow. They also tend to run together when batched, making some test jobs take 20-30 minutes or even time out.
This PR makes every test run in its own job. And since we can run hundreds of jobs concurrently, this should significantly speed up our CI pipeline.
Checklist
N/A