Parallelize pytest --collect-only in split_tests.py#171772
Merged
Merged
Conversation
cProfile showed 99.6% of split_tests.py wall time was spent in the single pytest --collect-only subprocess. Fan out the collection across ``os.cpu_count()`` workers; round-robin chunking keeps each batch roughly equal, and tests/components is expanded one level deeper so the ~1000 integration subdirectories distribute evenly. Local wall time dropped from ~132s to ~11s on an 18-core box. Bucket output is unchanged because we still parse the same pytest -qq output, just aggregated from multiple invocations.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR speeds up the CI “Split tests for full run” step by parallelizing pytest --collect-only in script/split_tests.py, fanning out large directories (notably tests/components) into smaller batches collected concurrently.
Changes:
- Run
pytest --collect-onlyacross multiple batches in parallel viaProcessPoolExecutor. - Add path fan-out logic to expand large directories one level deeper (and
tests/componentsto per-integration paths). - Aggregate multiple
pytestcollection outputs back into the existingTestFolder/bucket-splitting logic.
Only pass directories and test_*.py files to pytest --collect-only so helpers like tests/components/conftest.py and tests/components/common.py are not treated as explicit collection targets, and bail out with a clear error if no eligible paths are found instead of running pytest with no arguments.
This was referenced May 21, 2026
balloob
approved these changes
May 22, 2026
Member
Author
|
thanks |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed change
cProfile of the Split tests for full run CI step shows 99.6% of wall time is in the single
pytest --collect-onlysubprocess. Fan it out acrossos.cpu_count()workers usingProcessPoolExecutor; round-robin chunking keeps each batch roughly equal, andtests/componentsis expanded one level deeper so the ~1000 integration subdirectories distribute evenly. Bucket output is unchanged because we still parse the same pytest -qq output, just aggregated from multiple invocations.CI step time vs dev (4-core runner):
Type of change
Additional information
Checklist
ruff format homeassistant tests)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest.requirements_all.txt.Updated by running
python3 -m script.gen_requirements_all.To help with the load of incoming pull requests: