fix(ci): relax AVM multi-blob check-circuit timeout#24571
Draft
AztecBot wants to merge 1 commit into
Draft
Conversation
AztecBot
added
ci-draft
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
1 participant
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
The AVM check-circuit nightly failed in run https://github.com/AztecProtocol/aztec-packages/actions/runs/28841207985 because one
e2e_multiple_blobsinput reached circuit checking for a 700560-row trace and was killed by the per-inputTIMEOUT=30swrapper.This keeps the default 30s timeout for normal AVM circuit inputs, but applies a targeted 90s timeout to
e2e_multiple_blobsinputs when generatingavm_check_circuitcommands.Verification
bash -O extglob -n yarn-project/end-to-end/bootstrap.shgit diff --checke2e_block_buildingemitsTIMEOUT=30sande2e_multiple_blobsemitsTIMEOUT=90sNo tracked issue.
Created by claudebox · group:
slackbot