Fix RestoreInProgressAllocationDeciderTests #135593
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
Use appropriate UnassignedInfo.Reason when failure count is 0
nicktindall
added
>test
elasticsearchmachine
added
Team:Distributed Coordination
|
Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination) |
nicktindall
commented
Sep 29, 2025
| if (randomBoolean()) { | ||
| failureCount = randomBoolean() ? 0 : 1; | ||
| reason = UnassignedInfo.Reason.ALLOCATION_FAILED; | ||
| reason = failureCount > 0 ? UnassignedInfo.Reason.ALLOCATION_FAILED : UnassignedInfo.Reason.NEW_INDEX_RESTORED; |
There was a problem hiding this comment.
I stole the reason from the value that appears in RestoreSnapshotIT#testExplainUnassigableDuringRestore, though I don't think the reason features anywhere in the decider logic so we could probably randomise it?
…AllocationDeciderTest # Conflicts: # muted-tests.yml
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.
Use appropriate
UnassignedInfo.Reasonwhen failure count is 0 so as to not trip assertion inUnassignedInfoconstructor.Closes #135566