[test] Fix flaky CoordinatorEventManagerTest by isolating metric group instance#3252
Merged
swuferhong merged 1 commit intoapache:mainfrom May 6, 2026
Merged
Conversation
Contributor
Author
|
Hi @wuchong, @vamossagar12. Could you take a look on this hotfix, thx. |
vamossagar12
approved these changes
May 6, 2026
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
3 participants
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.
Purpose
Linked issue: close #3245
Shared static
TestingMetricGroups.COORDINATOR_METRICSinstance causes gauge name collision across tests:AbstractMetricGroup.addMetric()rejects new gauges when a same-name gauge already exists (keeps the old one), so the test reads a stale gauge bound to a differentCoordinatorEventManagerinstance.Brief change log
Tests
API and Format
Documentation