Use pytest on top of unittest to allow multi-proc execution
#714
Conversation
This file contains 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.
Use
pytestfor CIDescription/Motivation/Screenshots
This PR is background work for the self-hosting CI runners that will allow to test non-x86 archs (although GH Actions only offers ARM & AARCH64 for now).
Since each unittest we do is totally independent from one another, we can massively improve the time
wastedspent in CI testing by splitting on more cores. That's exactly the point of this PR: make use ofpytest+pytest-xdiston top ofunittestto distribute the tests. New test time is (roughly) the old divided by the number of cores given.How Has This Been Tested?
make testChecklist
devbranch, notmaster.