test(bindings): raise anvil fork startup timeout to 120s#547
Open
jonaprieto wants to merge 1 commit into
Open
Conversation
jonaprieto
force-pushed
the
refactor/bindings-tests-anvil-timeout
branch
2 times, most recently
from
bab2989 to
f4e32f1
Compare
Bindings tests fork one anvil per deployed chain; a slow or rate-limited RPC blows past anvil's 10s startup default and panics with `Timeout`, worsening as chains are added. Raise the fork startup timeout to 120s.
jonaprieto
force-pushed
the
refactor/bindings-tests-anvil-timeout
branch
from
f4e32f1 to
ce7c56c
Compare
This was referenced Jul 7, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The bindings tests fork a node per chain. Unlike the generic-call-forwarder fix (#26), these can't drop forking: the protocol adapter constructor calls into the risc0 verifier router (
isEmergencyStopped), and the execute test sends a real transaction against the deployed adapter, both of which need a forked node.Anvil only reports ready after it fetches fork state from the RPC, so a slow or rate-limited RPC blows past anvil's 10s startup default and the test panics with
Timeout(and it gets worse as chains are added). Raise the fork startup timeout to 120s.