fix(ci): bump avm_check_circuit per-test timeout to 120s for heavy txs

[AztecBot]

Problem

The avm-check-circuit job failed on next (run 26762926745) with exit code 124 (timeout).

The check runs bb-avm avm_check_circuit on every dumped e2e AVM circuit input in parallel, each isolated with TIMEOUT=30s and the default 2 CPUs. 499 inputs passed; one timed out:

FAILED: .../e2e_multiple_blobs/avm-circuit-inputs-tx-0x177bc7c8....bin (35s) (code: 124)

Root cause

Not a constraint failure — a timeout. From the per-test log:

• Simulating... → app logic done (~2s)
• Generating trace... → 23s (dominant cost, CPU-bound on the container's --cpus=2)
• Checking circuit... over 700560 rows started, then timeout: sending signal TERM at the 30s mark before it could finish.

e2e_multiple_blobs produces a much larger circuit (700560 rows) than the other e2e txs (which finish check-circuit in ~3s), so its trace generation + check exceeds the uniform 30s budget. The TIMEOUT=30s has been unchanged since the feature was introduced (#18747), and the existing WARNING comment in avm_check_circuit_cmds explicitly anticipated this failure mode for larger txs.

Fix

Raise the per-test timeout from 30s to 120s in avm_check_circuit_cmds (yarn-project/end-to-end/bootstrap.sh). This gives ~2x headroom over the heaviest observed total (~23s trace + check) and room for future circuit growth. The change is zero-cost for the ~500 fast checks — they still exit in a few seconds, so neither parallelism nor stage wall-clock is affected — it only lets the heavy outlier finish instead of being killed mid-check. The WARNING comment is updated to reflect the heavy-tx case.

No outer workflow/step timeout caps below this value, so the larger per-test budget takes effect.

---

Created by claudebox · group: slackbot

[AztecBot]

Automatically closing this stale claudebox draft PR (no updates for 5+ days). Re-open if still needed.