Make parallelization of testsuite optional #29
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
Codecov Report
@@ Coverage Diff @@
## main #29 +/- ##
==========================================
- Coverage 67.48% 67.47% -0.01%
==========================================
Files 56 56
Lines 6018 6020 +2
Branches 1866 1867 +1
==========================================
+ Hits 4061 4062 +1
Misses 670 670
- Partials 1287 1288 +1
Continue to review full report at Codecov.
|
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.
Not all tests are actually thread-safe, this enables to run the testsuite sequentially by default and on demand in parallel.
This is breaking the ABI, however since the tests are not part of the API usually exported in a shared library this is an acceptable ABI breakage and doesn't require to bump to 0.3.0 on the next release.