-
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
executor: migrate test-infra to testify for parallel_apply_test.go #32686
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. |
Code Coverage Details: https://codecov.io/github/pingcap/tidb/commit/1d2e0cb6e3ebe3acfafbc8fa6ffa4b4e3c381c74 |
/cc @tisonkun |
/merge |
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.
NewTestKitWithInit
is somehow too much to encapsulate and I intend to avoid it but with one more line tk.MustExec("use test")
Most developers aren't aware difference between NewTestKitWithInit
and NewTestKit
but choose either randomly (what is "Init"?). I think make it explicit should help.
testkit/testkit.go
Outdated
// NewTestKitWithInit returns a new *TestKit and use test db. | ||
func NewTestKitWithInit(t testing.TB, store kv.Storage) *TestKit { | ||
tk := NewTestKit(t, store) | ||
tk.MustExec("use test") | ||
return tk | ||
} |
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.
Please remove this method.
/merge cancel |
/merge cancel |
Signed-off-by: tison <wander4096@gmail.com>
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 205ed9d
|
/run-unit-test |
@feitian124: 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 #28599
Release note