-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
*: fix regression from FLUSH PRIVILEGES fix #28736
Conversation
[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-check_dev_2 |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: a3dfca7
|
/merge |
@morgo: Your PR was out of date, I have automatically updated it for you. At the same time I will also trigger all tests for you: /run-all-tests If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
What problem does this PR solve?
Issue Number: close #28559
Problem Summary:
The 3 tests failed because of the first failure in the
role
test, and then a failure to cleanup after the first failure.The root cause is an uncaught error, which is a regression introduced in #27958
This also removes "FLUSH PRIVILEGES" from tests where it is not required. This is done to prevent future regressions, since GRANT is expected to reload the privilege tables.
An incorrect error message is also fixed.
What is changed and how it works?
What's Changed:
A recently introduced regression is fixed (set default role for current user does not validate roles exist.)
Check List
Tests
Side effects
Documentation
Release note
No release note because the bug was introduced and fixed before a user release.