[3.2] switch parallel tests to new runner type #172
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
heifner
approved these changes
Sep 15, 2022
heifner
changed the title
|
The test failure is: #174. I'll have a fix up shortly. |
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 is a cost/efficiency change in preparation for more tests to be run in CI shortly (such as pinned builds & ARM builds). The parallel tests will now run on the lesser "hightier" runner which doesn't slow down total test time at all because even with the reduced number of CPUs we have to wait around for the
test_monitor_looptest which is a minute longer than anything else.The current configuration, always subject to change if need be,
1: This was 224GB until very recently. Last couple days started to see some runs exhaust memory so was bumped up.