fix(ci): give AVM check-circuit more time for large traces

[AztecBot]

Summary

• bump AVM check-circuit generated-command timeout from 30s to 60s
• update the nearby comment to reflect that large generated traces can exceed 30s without hitting memory limits

Root cause

Scheduled run https://github.com/AztecProtocol/aztec-packages/actions/runs/27805430170 failed in avm-check-circuit at 76536abe4b1efb7d1cc4954d3dbf61ca8660e0f3.

The failing internal log was http://ci.aztec-labs.com/b282498ab4e2e99c, launched from parent log http://ci.aztec-labs.com/1781844717230576. The input was e2e_multiple_blobs/avm-circuit-inputs-tx-0x242e67c9c421537248955736822585bf30bf7470ad3e81f0bd64c6d8e26e5b83.bin.

It reached Checking circuit... over 700560 rows and was killed by the harness timeout:

• command prefix: TIMEOUT=30s
• log line: timeout: sending signal TERM to command 'bash'
• parent result: (code: 124)

So the failure was a per-input timeout on a large generated AVM trace, not a circuit satisfiability failure.

Verification

• bash -O extglob -n yarn-project/end-to-end/bootstrap.sh
• generated a dummy e2e_multiple_blobs AVM input and ran avm_check_circuit_cmds; it emitted TIMEOUT=60s for the matching checker command
• git diff --check

---

Created by claudebox · group: slackbot

[AztecBot]

Flakey Tests

🤖 says: This CI run detected 2 tests that failed, but were tolerated due to a .test_patterns.yml entry.

\033FLAKED\033 (8;;http://ci.aztec-labs.com/6d6564ee2ce6871f�6d6564ee2ce6871f8;;�):  yarn-project/end-to-end/scripts/run_test.sh simple src/e2e_p2p/sentinel_status_slash.parallel.test.ts "slashes the proposer with INACTIVITY when checkpoint validation records unvalidated" (190s) (code: 0) group:e2e-p2p-epoch-flakes
\033FLAKED\033 (8;;http://ci.aztec-labs.com/bfde2544ab680e78�bfde2544ab680e788;;�): yarn-project/kv-store/scripts/run_test.sh src/bench/sqlite-opfs-encrypted/map_bench.test.ts (1s) (code: 0)