test: skip flaky sentinel_status_slash on merge-train/spartan#23443
Draft
AztecBot wants to merge 1 commit into
Draft
test: skip flaky sentinel_status_slash on merge-train/spartan#23443AztecBot wants to merge 1 commit into
AztecBot wants to merge 1 commit into
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
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.
Summary
Skip
sentinel_status_slash.parallel.test.tsto unblockmerge-train/spartan.Failure
Merge-train CI run http://ci.aztec-labs.com/1779299975599110 failed on:
Test log: http://ci.aztec-labs.com/852ace33ed5b6f03
Root Cause
The test (added in #23286) is timing-sensitive. It spawns one malicious validator with
broadcastInvalidBlockProposal: trueand expects honest observers to:state_mismatchunvalidatedIn the failing run, the observer recorded
blocks-missed, meaning it never saw the malicious node's block proposal at all. Despite the warp-to-slot-before-target andmockGossipSubNetwork: truesetup, the proposer-pipelining build phase for the target slot lands on the malicious node before the network has fully settled.The test failed twice in a row (initial run + retry), so the existing
e2e-p2p-epoch-flakesgroup didn't catch it.Fix
Skip the test (assigned to palla) so the merge-train can advance while the timing issue is investigated. Follows the same approach used for
epochs_l1_reorgs.parallel.test.ts.Slack: https://aztecprotocol.slack.com/archives/C0AU8BULZHC/p1779301250083769
ClaudeBox log: https://claudebox.work/s/856f19a40ad6abca?run=1