documenting reason for skipping test TestConsensus_LeaderForView
(after current epoch)
#1342
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.
This PR covers the quarantined test (see Notion doc Flaky and Skipped Tests - Quarantine for details):
flow-go/consensus/hotstuff/committees/consensus_committee_test.go
Lines 141 to 147 in c3502d1
While the test is skipped for a valid reason (it tests the behaviour of the mature protocol, which is different than the current implementation due to a temporary fallback), but this reasoning is not documented in the code.
This PR adds a comment explaining the reason for skipping the test.