fix: repair fairies v5 benchmark CI failures#24347
Draft
AztecBot wants to merge 2 commits into
Draft
Conversation
Collaborator
Author
Flakey Tests🤖 says: This CI run detected 2 tests that failed, but were tolerated due to a .test_patterns.yml entry. |
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
Refs aztec-packages#24223.
The latest merge-queue dequeue for aztec-packages#24223 was from CI3 run
28272090637, job83771340260, not a merge conflict. The train PR is mergeable/clean; the dequeue came from CI failures in benchmark/test execution.Failures found in the CI dashboard logs:
client_flows/amm: expected 14 private execution steps, got 17 forecdsar1 + sponsored_fpcAMM add-liquidity.client_flows/transfers: expected 11/13 private execution steps, got 13/14 forprivate_fpctransfers.bench_build_block: repeated sender tagging failures at index 21 withUNFINALIZED_TAGGING_INDEXES_WINDOW_LEN = 20.This PR:
MAX_PRIVATE_LOGS_PER_TXso benchmark blocks can keep several same-secret txs pending.Verification
git diff --check.claude/tests/agents_symlink_testa842b16424a0ead826c998b1c52b933eac44cbb7../bootstrap.sh ciwas attempted as requested, but this checkout's root bootstrap does not define a barecicommand (Unknown command: ci). It also cannot connect to Docker for local Redis in this container.sync_tagged_private_logs.test.tswas attempted, but Yarn is not installed/generated in this workspace (Couldn't find the node_modules state file).Created by claudebox · group:
slackbot