Skip to content

fix: increase AVM check-circuit input timeout#24637

Draft
AztecBot wants to merge 1 commit into
nextfrom
cb/fix-avm-check-circuit-timeout-64c4ef16
Draft

fix: increase AVM check-circuit input timeout#24637
AztecBot wants to merge 1 commit into
nextfrom
cb/fix-avm-check-circuit-timeout-64c4ef16

Conversation

@AztecBot

Copy link
Copy Markdown
Collaborator

Summary

The AVM check-circuit workflow failed in run 29068771153 because the generated per-input command for e2e_multiple_blobs was killed by the fixed 30s wrapper timeout while checking a 700,560-row circuit.

This raises the default AVM check-circuit input timeout to 2 minutes and makes it overrideable with AVM_CHECK_CIRCUIT_TIMEOUT for ad-hoc runs.

Testing

  • ./bootstrap.sh avm_check_circuit_cmds | rg '0x26c158be877406fa0eb67f55e42c190d203c81efd9ee6064acc8b4ad59483086' with the downloaded failing artifact now emits TIMEOUT=2m.
  • AVM_CHECK_CIRCUIT_TIMEOUT=75s ./bootstrap.sh avm_check_circuit_cmds | rg '0x26c158be877406fa0eb67f55e42c190d203c81efd9ee6064acc8b4ad59483086' emits TIMEOUT=75s.
  • bash -O extglob -n yarn-project/end-to-end/bootstrap.sh.

I did not run the full bb-avm avm_check_circuit locally: building bb-avm in this checkout is blocked until the Noir submodule/AVM transpiler dependency is initialized.


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 Jul 10, 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