Skip to content

fix(ci): relax AVM check-circuit timeout - #24925

Closed
AztecBot wants to merge 1 commit into
nextfrom
cb/fix-avm-check-circuit-timeout-5ed6c4
Closed

fix(ci): relax AVM check-circuit timeout#24925
AztecBot wants to merge 1 commit into
nextfrom
cb/fix-avm-check-circuit-timeout-5ed6c4

Conversation

@AztecBot

Copy link
Copy Markdown
Collaborator

Summary

  • Increase the per-input AVM check-circuit timeout from 30s to a bounded 2m default.
  • Add AVM_CHECK_CIRCUIT_TIMEOUT so the CI harness can tune this without another script edit.

Root Cause

The failed avm-check-circuit job was terminated by the harness timeout, not by an AVM circuit assertion. The failing dumped input was single-node/block-building/multiple_blobs tx 0x2a362dcc...; its child log reached Checking circuit... over 700,560 rows and then timeout -v 30s sent TERM. The same input failed twice on r6a.16xlarge runners, while the previous next run passed with its largest multiple_blobs input at 20s on m7a.16xlarge. The 30s budget is too tight for valid larger inputs plus CI instance variability.

Testing

  • bash -O extglob -n yarn-project/end-to-end/bootstrap.sh
  • git diff --check
  • Fixture avm_check_circuit_cmds output emits TIMEOUT=2m by default.
  • Fixture avm_check_circuit_cmds output emits TIMEOUT=45s when AVM_CHECK_CIRCUIT_TIMEOUT=45s.

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 23, 2026
@AztecBot

Copy link
Copy Markdown
Collaborator Author

Superseded by #24959, which makes the same avm_check_circuit budget fix, is rebased on current next (so its CI is meaningful), and carries the evidence from the latest failure (run 30266937162).

Five open PRs plus ~50 stale branches all propose this same one-line change and none has ever landed. Consolidating on #24959 — safe to close this one.


Created by claudebox · group: slackbot

@AztecBot

Copy link
Copy Markdown
Collaborator Author

Closing in favour of #24959, which carries the same fix rebased onto current next plus the consolidated evidence (including the circuit check: success / check_circuit_ms: 19601 sub-log from #24950 and the 22.75s local measurement from #24946).

This is a consolidation, not a rejection — the analysis here was correct, and the r6a vs m7a instance-variance observation fed into the final justification. Six identical open drafts were competing for the same review, and each was expiring to the stale-draft closer before anyone looked. Please review and merge #24959 to break the loop.


Created by claudebox · group: slackbot

@AztecBot AztecBot closed this Jul 27, 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