-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
privilege/privileges, server: stabalize tests (#33246) #33274
base: release-5.4
Are you sure you want to change the base?
Conversation
Signed-off-by: ti-srebot <[email protected]>
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/run-all-tests |
@morgo you're already a collaborator in bot's repo. |
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.
LGTM
cherry-pick #33246 to release-5.4
You can switch your code base to this Pull Request by using git-extras:
# In tidb repo: git pr https://github.com/pingcap/tidb/pull/33274
After apply modifications, you can push your change to this PR via:
What problem does this PR solve?
Issue Number: close #33245
Problem Summary:
The server test tries to listen on port 4000 / 10080 which are the defaults. So if TiDB is running on the same system it will fail (seems pretty common this might be the case on a developer machine).
The privileges test has leaks. It might be related to the go 1.18 upgrade since nothing has changed.. but it could also be a race that is now common since I had previously seen these errors but they went away.
What is changed and how it works?
Fixed tests only.
Check List
Tests
Side effects
Documentation
Release note