[DX-3452] try R6 runners with CRE system tests#21617
Closed
Conversation
…ifyTriggerEventACKs()
Contributor
|
✅ No conflicts with other open PRs targeting |
Base automatically changed from
dx-3449-parallel-cre-regression-tests
to
dx-3386-parallel-cre-tests
March 20, 2026 12:56
|
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
1 participant
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.
(20m 7s) Runner: cpu=8/ram=32/family=m6i+m5.*
(22m 34s) Runner: cpu=8+16/ram=32+64/family=c6id+m6id+m6idn
(23m 43s) Runner: cpu=48/ram=96/family=c6i
(24m 14s) Runner: cpu=16/ram=128/family=r6i.*
Verdict: unless we can guarantee that there are no laggers, when scheduling matrix test jobs, then using more powerful runners makes no sense. In any case gains seem to marginal relative to costs.