Skip to content

fix(ci): extend AVM check timeout for multiple blobs#24621

Draft
AztecBot wants to merge 1 commit into
nextfrom
cb/avm-multiple-blobs-check-timeout
Draft

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

Conversation

@AztecBot

@AztecBot AztecBot commented Jul 9, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Root cause: the AVM check-circuit job hit the per-input harness timeout, not a circuit constraint failure. The failing dumped input was from e2e_multiple_blobs, ran over 700,560 rows, and was killed by timeout -v 30s with exit code 124.
  • Keep the default AVM check-circuit timeout at 30s for ordinary dumped inputs.
  • Give dumped e2e_multiple_blobs/* inputs a 60s timeout, matching their intentionally larger trace size without relaxing the whole job.

Failing run: https://github.com/AztecProtocol/aztec-packages/actions/runs/28993687510
Dashboard log: http://ci.aztec-labs.com/1783572773996984

Testing

  • bash -O extglob -n yarn-project/end-to-end/bootstrap.sh
  • Generator smoke test with fake dumped inputs confirmed e2e_multiple_blobs emits TIMEOUT=60s while a normal input emits TIMEOUT=30s.
  • 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 Jul 9, 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