Conversation
Collaborator
Author
Flakey Tests🤖 says: This CI run detected 1 tests that failed, but were tolerated due to a .test_patterns.yml entry. |
Collaborator
Author
|
Automatically closing this stale claudebox draft PR (no updates for 5+ days). Re-open if still needed. |
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
FullProverTestteardown tolerate setup failures before the prover node is created, so the original setup error remains visible.Investigation
aztec-packages#24388 was removed from the merge queue at 2026-06-30 09:29 UTC after merge-group run 28432921723 failed on temporary SHA
8bbf03bfd38dd76974ff007d7d540c900374bd80.The failing leg was
a1-fast arm64 ci-fast; the wrapper log reported exit 124, and the inner test-engine log showedFAKE_PROOFS=1 yarn-project/end-to-end/scripts/run_test.sh simple single-node/prover/fulltiming out. The suite log showed setup failing while PXE contract sync queried a block hash that the node had just pruned after the setup epoch warp/proof mark. Teardown then threw onthis.proverAztecNode.stop()because setup had not reached prover-node creation.The first CI run on this PR then failed the same suite earlier with
Timeout awaiting block proven >= 6: the prior patch waited on the pre-prune L2 block number, butmarkAsProven()only marked the latest checkpoint as proven, so an uncheckpointed setup block was still pruned. This update waits for the setup block to become checkpointed before advancing/proving, then waits for that same block to become proven.Testing
git diff --check./bootstrap.sh cidid not run locally: this checkout reportsUnknown command: ciafter Docker/Redis startup checks.FAKE_PROOFS=1 yarn-project/end-to-end/scripts/run_test.sh simple single-node/prover/fulldid not start locally: missingyarn-project/node_modules/.bin/jestin this container.Created by claudebox · group:
slackbot