-
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
ddl: speedup test case TestModifyColumnTime #24469
ddl: speedup test case TestModifyColumnTime #24469
Conversation
f9fa804
to
e20c345
Compare
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.
Could you add a description of how long the tests were executed before and after this PR?
ddl/db_test.go
Outdated
c.Assert(err, IsNil, Commentf("%+v", t)) | ||
var wg sync.WaitGroup | ||
wg.Add(len(tests)) | ||
for i, t := range tests { |
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.
I don't think it's necessary to drive so many goroutines.
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.
I think so :-)
d7f654b
to
8b9c2fe
Compare
@jianzhiyao Could you use the same trick as in #24487 ? Testcases in this test are actually standalone. I think splitted tests are better than shooting goroutines. Of course, only if it is indeed faster. |
8b9c2fe
to
a5e7098
Compare
/dissmiss |
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.
Rest LGTM
variable.SetDDLErrorCountLimit(limit) | ||
tk.Se.GetSessionVars().EnableChangeColumnType = enableChangeColumnType | ||
tk.Se.GetSessionVars().TimeZone = originalTz | ||
}() | ||
|
||
for _, t := range tests { | ||
tk.MustExec("drop table if exists t_mc") |
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.
Tablename duplicated for cases, plz fix.
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.
According to the result of check_dev
and check_dev_2
, seems tablename can be the same in different test case.
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.
Testcases could be paralleled, under which case it will fail... But I'll give you LGTM anyway.
PTAL again after test passed |
/lgtm |
[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 writing |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 1b1975c
|
/run-all-tests This bot automatically retries jobs that failed on can merge PRs (send feedback to hi-rustin). Silence the bot with the |
1 similar comment
/run-all-tests This bot automatically retries jobs that failed on can merge PRs (send feedback to hi-rustin). Silence the bot with the |
/run-common-test |
/run-integration-common-test |
/run-common-test |
/run-unit-test |
/run-all-tests |
/run-integration-ddl-test |
/run-tics-test |
@jianzhiyao: 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: #24459
Problem Summary:
What is changed and how it works?
split testDBSuite1.TestModifyColumnTime into many parts
build & test time
Comparing with pr: #24460, test time is reduced about 50s
Check List
Tests
Side effects
Release note