Skip to content

fix(ci): extend AVM check-circuit timeout for multiple blobs#24177

Closed
AztecBot wants to merge 1 commit into
nextfrom
cb/avm-check-circuit-timeout-388daec
Closed

fix(ci): extend AVM check-circuit timeout for multiple blobs#24177
AztecBot wants to merge 1 commit into
nextfrom
cb/avm-check-circuit-timeout-388daec

Conversation

@AztecBot

Copy link
Copy Markdown
Collaborator

Summary

  • keep the default AVM check-circuit timeout at 30s for normal dumped inputs
  • give e2e_multiple_blobs dumped AVM inputs a 2m timeout because the current fixture produces a much larger trace

Root cause

The failed run timed out, rather than hitting an AVM circuit assertion. The internal CI log shows e2e_multiple_blobs/avm-circuit-inputs-tx-0x048ad4...f77.bin reached Running check (with skippable) circuit over 700560 rows and was terminated by the per-input TIMEOUT=30s budget.

Testing

  • generated avm_check_circuit_cmds with dummy inputs before/after the change; origin/next assigned TIMEOUT=30s to the multiple-blobs input, while this patch assigns TIMEOUT=2m and keeps a normal e2e_amm input at 30s
  • bash -O extglob -n yarn-project/end-to-end/bootstrap.sh
  • git diff --check

Created by claudebox · group: slackbot

@AztecBot AztecBot added ci-draft Run CI on draft PRs. ci-no-fail-fast Sets NO_FAIL_FAST in the CI so the run is not aborted on the first failure claudebox Owned by claudebox. it can push to this PR. labels Jun 18, 2026
@AztecBot AztecBot closed this Jun 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci-draft Run CI on draft PRs. ci-no-fail-fast Sets NO_FAIL_FAST in the CI so the run is not aborted on the first failure claudebox Owned by claudebox. it can push to this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant