Randomize validator index in partial withdrawal test #3892
Merged
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.
Background
Raised by @pk910 in discord that Lodestar forked off in devnet 2 on partial withdrawals. After debugging, it was because Lodestar incorrectly checks validator with index
state.next_withdrawal_index
instead ofwithdrawal.index
for partial withdrawal eligibility inget_expected_withdrawals
.See discord discussion for detail.
This bug is not caught by partial withdrawal spec test because every test case uses fixed validator index
validator_index = spec.get_active_validator_indices(state, current_epoch)[0]
which is 0 and it coincides with the default value of
state.next_withdrawal_index
which is 0 as well.Proposal
Make each test pick validator index at random ie.