-
Notifications
You must be signed in to change notification settings - Fork 590
HDDS-4013. FLAKY-UT: TestWatchForCommit#testWatchForCommitForGroupMismatchException #1697
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanx @adoroszlai for the fix, I am able to repro this, changes seems fair enough.
Does it makes sense to
removeGroupexplicitly in caseserver.isExist(pipelineId)is true, rather than waiting? Might speed up test? We can ignore the exception fromremoveGroupin the wait and retry to counter the race conditionThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @ayushtkn for taking a look.
I'd rather avoid such "manual intervention" and let the test exercise production code paths.
I don't think keeping
removeGroupwould result in much speedup. If SCM and datanodes take too much time to execute regular flow, we could probably tweak executor intervals, etc.It might be possible to convert it to a unit test with mocks, resulting in much bigger speedup by avoiding the mini cluster.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
makes better to stay near the prod code. Thanx