-
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
util/logutil: migrate to testify #26322
Conversation
No release note, Please follow https://github.com/pingcap/community/blob/master/contributors/release-note-checker.md |
There are several places I redefine variable assert := assert.New(s.T()) It will trigger a warning of goland, but the documentation of testify do so. If I redefine the variable to something else like Which way is more proper? |
About the CI failure:
I checked Maybe I shouldn't use the same name as the original suite, would |
Thanks for submitting this PR @ofey404 . You may take a looks at this comment #26318 (comment) and we'd better avoid suite usage of testify. The check script is for gocheck test-infra, you may modify it, work around it, or remove it if necessary. But since suite of testify suffers #26082 (comment), you may think of avoiding it. |
Also, |
There is a buffer seems never used in the test, except in In current commit I just simply remove it, but I'm not quite sure if it's OK to do so. |
The test has some goroutine leak, I'm finding out where it is. |
@ofey404 I've created a patch for you tisonkun@852979f that you can make use of. Today I updated some notes about best practices when migrating tests #26022 , which you may take a look at. |
|
Thank you very much! I know this is gonna sound really stupid, but how can I make use of this patch? It looks similar to what I've commit... |
Oh! I understand what happened! |
@ofey404 thanks for your updates! I provide the patch for I think code express quickly :P |
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
@tisonkun: Thanks for your review. The bot only counts approvals from reviewers and higher roles in list, but you're still welcome to leave your comments. In response to this:
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. |
[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. |
This pull request has been accepted and is ready to merge. Commit hash: c987ef2
|
About the unit test failure, what should I do?
|
/run-all-tests |
/merge |
@tisonkun: In response to this:
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. |
/run-unit-test |
1 similar comment
/run-unit-test |
@ofey404 it seems data race happen on this PR change set. Please take a look. |
As log in TiDB used as global variable, we may not run in parallel. What do you think @xhebox @tiancaiamao ? |
Fine. |
There are many global variables like that, it's one of the reason some test suite can not run parallel. |
…which causes data race Signed-off-by: tison <[email protected]>
@tiancaiamao @xhebox I push a commit to run these tests serially. Please re-trigger @xhebox among tests, it may set |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 6250f70
|
/cherry-pick release-5.1 |
Signed-off-by: ti-srebot <[email protected]>
cherry pick to release-5.1 in PR #28137 |
@qw4990 Why cherry pick this PR? |
@xhebox I think it is because we'd like to port #27238 to 5.1 and @xuyifangreeneyes & @qw4990 decided that we can bring also all previously PRs. |
What problem does this PR solve?
Issue Number: close #26154
What is changed and how it works?
What's Changed: Removed
pingcap/check
forutils/logutil
, moved to testify.Release note