Skip to content

fix: give AVM check-circuit larger inputs enough time#24959

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

fix: give AVM check-circuit larger inputs enough time#24959
AztecBot wants to merge 1 commit into
nextfrom
cb/fix-avm-check-circuit-timeout-30086087202

Conversation

@AztecBot

Copy link
Copy Markdown
Collaborator

Summary

  • Increase the AVM check-circuit harness resources from the default CPUS=2, MEM=8g, TIMEOUT=30s to CPUS=4, MEM=16g, TIMEOUT=2m.
  • Keep the existing parallelize 16 cap, so the job still fits a 64-core CI instance while allowing blob-heavy generated inputs to complete.

Root Cause

The failing run https://github.com/AztecProtocol/aztec-packages/actions/runs/30086087202 did not hit a circuit assertion. The avm-check-circuit job failed because bb-avm avm_check_circuit for the generated single-node/block-building/multiple_blobs tx 0x2f7ba764... reached Running check (with skippable) circuit over 700560 rows and was then killed by the harness-level timeout -v 30s, returning code 124.

Tests

  • bash -O extglob -n yarn-project/end-to-end/bootstrap.sh
  • git diff --check

Note: plain bash -n yarn-project/end-to-end/bootstrap.sh is not representative for this script because it does not execute the startup source that enables the extglob syntax already used by the file.


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