Skip to content

fix(ci): increase e2e_prover_full_real timeout after circuit changes#22100

Merged
AztecBot merged 1 commit into
merge-train/spartanfrom
fix/e2e-prover-timeout
Mar 27, 2026
Merged

fix(ci): increase e2e_prover_full_real timeout after circuit changes#22100
AztecBot merged 1 commit into
merge-train/spartanfrom
fix/e2e-prover-timeout

Conversation

@AztecBot

Copy link
Copy Markdown
Collaborator

Summary

  • Increases the e2e_prover_full_real CI timeout from 20m to 40m in end-to-end/bootstrap.sh
  • Increases the Jest TIMEOUT constant from 15m (900s) to 35m (2100s) in full.test.ts
  • Increases the beforeAll Jest timeout from 2m to 5m

Root Cause

The merge-next PR (#22089) merged 111 commits into spartan that introduced multiple cumulative performance regressions for the full prover test:

  1. CHONK recursion gates: +577 gates (1,493,584 → 1,494,161)
  2. ECCVM recursive verifier gates: +579 gates (224,657 → 225,236)
  3. AVM SHA256 PIL: added new circuit includes (bitwise.pil, memory.pil, precomputed.pil)
  4. Shplemini security fix: adds padding_indicator_array multiplication per round
  5. CRS format change: first-run decompression overhead on fresh EC2 instances

These changes collectively push the test from ~17-18 minutes to over 20 minutes, causing it to be killed by the 20-minute OS timeout.

Test plan

  • CI passes on merge-train/spartan with this fix
  • e2e_prover_full_real completes within the new 40-minute timeout

🤖 Generated with Claude Code

The merge-next brought circuit gate count increases (CHONK +577, ECCVM
+579) and AVM circuit complexity changes from SHA256 PIL refactoring.
These combined to push the e2e_prover_full_real test just over its
previous 20-minute CI timeout.

- CI timeout: 20m → 40m
- Jest timeout: 15m → 35m
- beforeAll timeout: 2m → 5m

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@AztecBot AztecBot merged commit 0e2cc73 into merge-train/spartan Mar 27, 2026
11 of 15 checks passed
@AztecBot AztecBot deleted the fix/e2e-prover-timeout branch March 27, 2026 13:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant