Fix flaky test 03221_merge_profile_events#96964
Merged
alexey-milovidov merged 1 commit intomasterfrom Feb 15, 2026
Merged
Conversation
Remove the `ProfileEvents['UserTimeMicroseconds'] > 0` check from all three queries. This counter comes from `getrusage` which has coarse resolution (typically 1-4 ms on Linux). For small/fast merges (20000 rows), the operation completes so quickly that user time rounds down to zero, causing sporadic failures. The higher-resolution `OSCPUVirtualTimeMicroseconds` check (via `clock_gettime(CLOCK_THREAD_CPUTIME_ID)`) is retained. #85891 Co-Authored-By: Claude Opus 4.6 <[email protected]>
Contributor
zvonand
pushed a commit
to Altinity/ClickHouse
that referenced
this pull request
Feb 18, 2026
…erge-profile-events Fix flaky test 03221_merge_profile_events
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.
Remove the
ProfileEvents['UserTimeMicroseconds'] > 0check from all three queries in the test. This counter comes fromgetrusagewhich has coarse resolution (typically 1-4 ms on Linux). For small/fast merges (20000 rows), the operation completes so quickly that user time rounds down to zero, causing sporadic failures.The higher-resolution
OSCPUVirtualTimeMicrosecondscheck (viaclock_gettime(CLOCK_THREAD_CPUTIME_ID)) is retained.Fixes #85891
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):
...
🤖 Generated with Claude Code