-
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
Flaky test: TestShowGrantsForCurrentUserUsingRole #27651
Comments
Another occurence https://ci.pingcap.net/blue/organizations/jenkins/tidb_ghpr_check_2/detail/tidb_ghpr_check_2/30304/pipeline/62/
|
@unconsolable added. @karuppiah7890 thanks for reporting this. We regard unstable tests as bugs - and should be fixed in time seriously. @morgo could you please take a look? |
Please check whether the issue should be labeled with 'affects-x.y' or 'backport-x.y.z', |
test unstable, affects master, fixed in master |
Enhancement
The test
TestShowGrantsForCurrentUserUsingRole
is flaky. I was trying to run all the unit tests in the repo and noticed theTestShowGrantsForCurrentUserUsingRole
test fail like this -But later while running the same test standalone to check the error properly (as the full unit test log was too long and I didn't search for TestShowGrantsForCurrentUserUsingRole properly) the test passed
Looks like it's a case of a flaky test where the ordering of a query's result rows are causing the test to fail at times. In the above error it shows that
[GRANT SELECT ON test.* TO 'joe'@'%']
came prior toGRANT UPDATE ON role.* TO 'joe'@'%']
but the expected was for it to come laterDoes ordering of the query results matter in this case? I was assuming it doesn't but I don't know for sure. But if query result row order doesn't matter, we can write the test in such a way that order is ignored as part of the assertion
Let me know what you folks think!
The text was updated successfully, but these errors were encountered: