Disable CPU overload checks for all tests#80166
Merged
Conversation
Contributor
nikitamikhaylov
approved these changes
May 13, 2025
robot-clickhouse-ci-2
added a commit
that referenced
this pull request
May 14, 2025
Cherry pick #80166 to 25.4: Disable CPU overload checks for all tests
robot-clickhouse
added a commit
that referenced
this pull request
May 14, 2025
1 task
Algunenano
added a commit
that referenced
this pull request
May 14, 2025
Backport #80166 to 25.4: Disable CPU overload checks for all tests
1 task
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
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.
CPU overload detection contributes to flakiness of tests especially on slower debug and sanitizer builds.
Let's not enable this feature by default for all tests
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
...
Documentation entry for user-facing changes