-
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
bazel: optimizate the bazel test #39414
bazel: optimizate the bazel test #39414
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. |
26dc17f
to
1f1aa7b
Compare
Signed-off-by: Weizhen Wang <[email protected]>
Signed-off-by: Weizhen Wang <[email protected]>
8dadc7b
to
2d6a850
Compare
/run-all-tests |
/check-issue-triage-complete |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 2d6a850
|
/run-check_dev_2 |
/run-all-tests |
5 similar comments
/run-all-tests |
/run-all-tests |
/run-all-tests |
/run-all-tests |
/run-all-tests |
TiDB MergeCI notify✅ Well Done! New fixed [1] after this pr merged.
|
Signed-off-by: Weizhen Wang [email protected]
What problem does this PR solve?
Issue Number: close None
Problem Summary:
What is changed and how it works?
Why do I put some test cases into a new folder?
because test cases is too much in the
executor
. bazel allows 50 shards of the test case to run into difference threads. if too many test cases are to run more time in a thread. it will slow down the CI.Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.