fix erasure tests #592
Closed
fix erasure tests #592
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
dryajov
force-pushed
the
fix-erasure-tests
branch
from
a3ce00d to
407a1f3
Compare
dryajov
force-pushed
the
fix-erasure-tests
branch
from
407a1f3 to
87e3806
Compare
|
closing in favor of #618 |
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.
Fix some issues with erasure tests, where under some K+M configurations you get some out of bounds errors. This only manifests under some specific number of blocks, K and M settings.
Furthermore, we should fuzz the implementation and also run tests with different block lengths, K and M parameters.