ec: test concurrent parity write failures - #359
Merged
Merged
Conversation
* inject a write error into each parity writer in D2 P2 encoding * verify the failing stream is reported and no checksums related to NVIDIA#358 Signed-off-by: Ferhat Elmas <elmas.ferhat@gmail.com>
ferhatelmas
force-pushed
the
ferhat/parity-writer-error
branch
from
August 26, 2026 11:47
8b2f713 to
60f8384
Compare
alex-aizman
reviewed
Sep 3, 2026
| failIndex int | ||
| }{ | ||
| {name: "first parity writer", failIndex: 0}, | ||
| {name: "second parity writer", failIndex: 1}, |
Member
There was a problem hiding this comment.
something like:
+ {name: "all parity writers", failIndices: []int{0, 1}},
would be good to have
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
related to #358