test(ci): skip flaky e2e_slashing/attested_invalid_proposal on merge-train/spartan

[AztecBot]

What failed

The merge-train/spartan ci-full-no-test-cache run at commit 1aa8f103 (feat(api)!: redesign node log retrieval API around tag-based queries, #23625) hard-failed on a single test:

FAIL src/e2e_slashing/attested_invalid_proposal.test.ts (359.854 s)
  ✓ slashes a lazy attester for an invalid checkpoint proposal (157980 ms)
  ✕ slashes a lazy attester for an invalid checkpoint and clears it on delayed equivocation (191565 ms)
  ● TimeoutError: Timeout awaiting honest validator slash offenses for invalid proposal attestation

• Run: ci.aztec-labs.com/1780072085139323
• Failing test log: ci.aztec-labs.com/825d698daa933f9b

Why it's a flake, not a #23625 regression

This is the known pipelining attestation race already registered in .test_patterns.yml: under pipelining the lazy validator's checkpoint attestation can arrive after the p2p attestation acceptance window and get rejected before the slasher's gossip callback fires, so ATTESTED_TO_INVALID_CHECKPOINT_PROPOSAL is never recorded and the wait times out. The same scenario setup passed for the first it and timed out for the second within the same run — a timing race, not deterministic breakage.

It is unrelated to the log-retrieval API redesign the train is integrating: slash-offense detection runs purely off P2P gossip + block re-execution + ValidatorClient in-memory state and never calls getPrivateLogsByTags / getPublicLogsByTags (or any node log method). If the API change had broken offense detection, the first it (same detection path) would also have failed.

Why skip rather than rely on the existing flake entry

The entry already had an error_regex flake match, but ci3 only grants a single retry for an owned flake — a test that fails twice in a row hard-fails regardless of flake_group. This run failed both attempts. This is the exact situation handled by #23544 / #23542 (error_regex flake matches "still let ci3 retry-and-fail both attempts"), whose remedy was to collapse the entry to skip: true.

Change

.test_patterns.yml: collapse the attested_invalid_proposal.test.ts flake entry from error_regex to skip: true, with an updated comment and a reference to this run's log. Owner kept as @palla. Skip stands until the pipelining attestation race is stabilised.

Verification

.test_patterns.yml parses with yq, and simulating ci3/filter_test_cmds confirms the failing command (run_test.sh simple src/e2e_slashing/attested_invalid_proposal.test.ts) is now filtered out of the test list while sibling commands are unaffected. A full ./bootstrap.sh ci run is not a meaningful check for a CI-config skip (it cannot affect a build), so it was not run on the host.

---

Created by claudebox · group: slackbot