[ci] Decrease the concurrent workers for Yugabyte' with -enable_scd_hash_lock flag test - #1659
Draft
MariemBaccari wants to merge 5 commits into
Draft
[ci] Decrease the concurrent workers for Yugabyte' with -enable_scd_hash_lock flag test#1659MariemBaccari wants to merge 5 commits into
MariemBaccari wants to merge 5 commits into
Conversation
MariemBaccari
changed the title
MariemBaccari
marked this pull request as draft
August 21, 2026 09:33
MariemBaccari
changed the title
MariemBaccari
marked this pull request as ready for review
August 21, 2026 10:06
MariemBaccari
marked this pull request as draft
August 21, 2026 11:37
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.
Following the extension of performance testing in #1618, the CI runs against Yugabyte with the
-enable_scd_hash_lockflag can face intermittent load-sensitive test failures due to the high number of concurrent workers.This PR fixes this by decreasing the
--heavy_traffic_concurrent_workersflag to 5.