[ty] Use more parallelism when running corpus tests #18711
Merged
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
Now that we've moved the corpus tests to the
ty_python_semanticcrate, runningcargo test -p ty_python_semantictakes an annoying amount of time locally. (This also hasn't been helped by the fact that we run a lot more corpus tests after #18531.) We can speed things up quite a bit by splitting the corpus tests up more, so that they run in parallel.Test Plan
On
mainlocally:On this PR branch locally:
I.e., a speedup of around 5s