You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ci-draftRun CI on draft PRs.ci-no-fail-fastSets NO_FAIL_FAST in the CI so the run is not aborted on the first failureclaudeboxOwned by claudebox. it can push to this PR.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
AVM_CHECK_CIRCUIT_TIMEOUTso the CI harness can tune this without another script edit.Root Cause
The failed
avm-check-circuitjob was terminated by the harness timeout, not by an AVM circuit assertion. The failing dumped input wassingle-node/block-building/multiple_blobstx0x2a362dcc...; its child log reachedChecking circuit...over 700,560 rows and thentimeout -v 30ssent TERM. The same input failed twice onr6a.16xlargerunners, while the previousnextrun passed with its largestmultiple_blobsinput at 20s onm7a.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.shgit diff --checkavm_check_circuit_cmdsoutput emitsTIMEOUT=2mby default.avm_check_circuit_cmdsoutput emitsTIMEOUT=45swhenAVM_CHECK_CIRCUIT_TIMEOUT=45s.Created by claudebox · group:
slackbot