*: enable more flaky test, enable more shard_count and update bazel config

[hawkingrei]

Signed-off-by: Weizhen Wang [email protected]

What problem does this PR solve?

Issue Number: ref #35247

Problem Summary:

What is changed and how it works?

• enable more flaky test
• enable more shard_count
• split test cases into subdirectories to speed up the build and the test.

Why are test cases speed up by being splited into subdirectories?

1、execute has too many test cases in the same folder. If we change one of the test cases, we need to rebuild all of it. It will take many times.
2、bazel limit 50 shard_count. it can not run parallel, too many test cases run at slow speed.
3、test cases run in the shard. it is isolated by the sandbox. so it can not suffer from the other test cases. the test will run more stable.

Check List

Tests

• Unit test
• Integration test

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• Yisaer
• tisonkun

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[sre-bot]

Code Coverage Details: https://codecov.io/github/pingcap/tidb/commit/e766a4c8dd26324880dcb1f7ab0118f45ec94242

[tisonkun]

@hawkingrei stream.go removed without modifying the BUILD.bazel file. It seems not quite smooth from my perspective. Is it possible that we keep sync between the file tree and bazel files? Or we must defer the sync until someone trigger bazel config updates manually?

[hawkingrei]

@hawkingrei stream.go removed without modifying the BUILD.bazel file. It seems not quite smooth from my perspective. Is it possible that we keep sync between the file tree and bazel files? Or we must defer the sync until someone trigger bazel config updates manually?

First, in the cockroach or other open source community, the bazel config is updated by the developers. so I will open it to the developers. But now developers are not similar to bazel. so it needs some time. but I hope it can be implemented as soon as possible.
Second, I think the bazel config is generated by the tools. so we can do it with a robot. it can pass to merge as soon as possible.

[Yisaer]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: e766a4c

[sre-bot]

TiDB MergeCI notify

🔴 Bad News! New failing [1] after this pr merged.
These new failed integration tests seem to be caused by the current PR, please try to fix these new failed integration tests, thanks!

CI Name	Result	Duration	Compare with Parent commit
idc-jenkins-ci-tidb/common-test	🟥 failed 2, success 10, total 12	12 min	New failing
idc-jenkins-ci-tidb/integration-common-test	🔴 failed 2, success 9, total 11	21 min	Existing failure
idc-jenkins-ci/integration-cdc-test	🟢 all 35 tests passed	29 min	Existing passed
idc-jenkins-ci-tidb/tics-test	🟢 all 1 tests passed	12 min	Existing passed
idc-jenkins-ci-tidb/integration-ddl-test	🟢 all 6 tests passed	8 min 50 sec	Existing passed
idc-jenkins-ci-tidb/sqllogic-test-1	🟢 all 26 tests passed	8 min 6 sec	Existing passed
idc-jenkins-ci-tidb/sqllogic-test-2	🟢 all 28 tests passed	7 min 48 sec	Existing passed
idc-jenkins-ci-tidb/mybatis-test	🟢 all 1 tests passed	3 min 7 sec	Existing passed
idc-jenkins-ci-tidb/integration-compatibility-test	🟢 all 1 tests passed	2 min 55 sec	Existing passed
idc-jenkins-ci-tidb/plugin-test	🟢 build success, plugin test success	4min	Existing passed