Skip to content

fix(ci): raise AVM check-circuit per-tx timeout to 120s#24137

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

fix(ci): raise AVM check-circuit per-tx timeout to 120s#24137
AztecBot wants to merge 1 commit into
nextfrom
cb/avm-check-circuit-timeout-27628986531

Conversation

@AztecBot

Copy link
Copy Markdown
Collaborator

Summary

Raise the per-input avm_check_circuit timeout from the hard-coded 30s to a 120s default, configurable through AVM_CHECK_CIRCUIT_TIMEOUT.

Root cause

The failed avm-check-circuit job in run https://github.com/AztecProtocol/aztec-packages/actions/runs/27628986531 did not hit a circuit assertion. The child command for e2e_multiple_blobs reached Checking circuit... over 700,560 rows and was killed by timeout -v 30s after 34s with exit code 124. Memory was about 3.9 GiB against the 8 GiB limit, so this was a wall-clock budget failure for the largest dumped AVM input under the default 2-CPU isolated CI quota.

This supersedes the stale draft #23662 with the same fix, rebased onto current next and opened with the standard CI labels.

Verification

  • bash -O extglob -n bootstrap.sh from yarn-project/end-to-end
  • Synthetic dumped-input command generation emits TIMEOUT=120s by default
  • AVM_CHECK_CIRCUIT_TIMEOUT=75s command generation emits TIMEOUT=75s

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 16, 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