Parallelized the running of tests using rayon. #600
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
This adds an unnecessary dependency, which is pretty bad for base, so we should either: - Feature-gate - Move this to cargo concordium (I prefer this) - Parallelize with native std functions - Remove
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.
This adds an unnecessary dependency, which is pretty bad for base, so we should either:
Purpose
Tests ought to be run in parallel, instead of sequentially.
In the same vein, we might also consider printing results incrementally, such that the end user sees each test finish, instead of seeing them all by the end. This would give more feedback about what tests take a long time to run and it would also allow the user to see smaller tests fail much faster. This is not implemented in this draft.