Use parSequence rather than sequence in RefTests #443
Merged
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
Imho `sequence` will not catch bugs related to concurrent modifications, but `parSequence` will do.
Codecov Report
@@ Coverage Diff @@
## master #443 +/- ##
==========================================
- Coverage 89.47% 89.42% -0.05%
==========================================
Files 70 70
Lines 2005 2005
Branches 209 209
==========================================
- Hits 1794 1793 -1
- Misses 211 212 +1 |
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.
Imho
sequencewill not catch bugs related to concurrent modifications, butparSequencewill do.