Skip to content
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

Splitting Test Directories to Increase Test Concurrency and Optimize Cache #44940

Open
hawkingrei opened this issue Jun 26, 2023 · 0 comments · Fixed by #45001, #45020, #45833, #45834 or #46780
Open
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. type/enhancement The issue or PR belongs to an enhancement.

Comments

@hawkingrei
Copy link
Member

Enhancement

we are using Bazel's shard_count to increase test concurrency and speed up our testing process. However, in some cases, we have found that certain directories have too many tests, which can result in slower test execution times, decreased efficiency, and less optimized cache usage.

To address this issue, we need to split the test directories into smaller, more manageable chunks. This will help increase test concurrency, optimize cache usage, and ultimately improve our testing process.

@hawkingrei hawkingrei added the type/enhancement The issue or PR belongs to an enhancement. label Jun 26, 2023
@hawkingrei hawkingrei added the good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. label Jun 26, 2023
ti-chi-bot bot pushed a commit that referenced this issue Jun 27, 2023
ti-chi-bot bot pushed a commit that referenced this issue Jun 28, 2023
@hawkingrei hawkingrei reopened this Jun 28, 2023
ti-chi-bot bot pushed a commit that referenced this issue Jun 28, 2023
@hawkingrei hawkingrei reopened this Jun 30, 2023
ti-chi-bot bot pushed a commit that referenced this issue Jul 6, 2023
ti-chi-bot bot pushed a commit that referenced this issue Jul 7, 2023
ti-chi-bot bot pushed a commit that referenced this issue Jul 10, 2023
ti-chi-bot bot pushed a commit that referenced this issue Aug 11, 2023
ti-chi-bot bot pushed a commit that referenced this issue Aug 28, 2023
ti-chi-bot bot pushed a commit that referenced this issue Sep 4, 2023
ti-chi-bot bot pushed a commit that referenced this issue Sep 8, 2023
@hawkingrei hawkingrei reopened this Sep 12, 2023
ti-chi-bot bot pushed a commit that referenced this issue Sep 12, 2023
ti-chi-bot bot pushed a commit that referenced this issue Sep 12, 2023
ti-chi-bot bot pushed a commit that referenced this issue Oct 14, 2023
ti-chi-bot bot pushed a commit that referenced this issue Nov 22, 2023
@hawkingrei hawkingrei mentioned this issue Dec 1, 2023
13 tasks
ti-chi-bot bot pushed a commit that referenced this issue Dec 1, 2023
@hawkingrei hawkingrei mentioned this issue Feb 1, 2024
13 tasks
ti-chi-bot bot pushed a commit that referenced this issue Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
1 participant