test: run the suite under pytest-xdist - #96
Merged
Conversation
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
1 participant
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.
Summary
pytest-xdistto the dev group and setaddopts = ["-n", "auto"], so the suite runs in parallel locally and in CI without changing the CI command. Every test already isolates itself viatmp_path,TDD_LEASE_DIRandTDD_LEDGER_HOME, so no test changes were needed.repofixture (git(...) if False else None) left over from an earlier edit.Measured locally (10 cores): 461 tests in ~118s serial → ~28–35s parallel. The suite's cost is per-test process spawns (a real git repo plus real
pytestandgitsubprocesses per test) rather than any individual slow test, so parallelism is the lever.Run
pytest -n0to get serial output when debugging a single test.Commits
129be14 test: run the suite under pytest-xdist; drop a no-op line in the repo fixture
Gates run
uv run pytest -q— 461 passeduv run ruff check .— cleanTest coverage note
No decision-point operators in the diff (config and lockfile changes plus a removed no-op line); pseudo-mutation analysis has nothing to cover.