test: fix failing test_simulate_succeeds on anvil@1.8.1 - #104
Merged
Conversation
pepebndc
approved these changes
Sep 4, 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
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.
Needed for #103, as it fixes its failing CI.
Cause
The test workflow installs Foundry with no
versioninput, sofoundry-toolchaininstalls the currentstable. The last green run on Aug 26 got anvil 1.7.1. The failing run on Sep 2 got anvil 1.8.1, released Aug 28.Foundry PR #15792 (in 1.8.0) makes anvil honor the
validation: trueflag ofeth_simulateV1. It now enforces fee checks and returns the spec error codes-38010to-38014.The test in
tests/eth_namespace/call.rs:131-153sends a call with no fee fields andvalidation: true. Anvil 1.8.1 answers:{"code":-38012,"message":"err: max fee per gas less than block base fee"}The robust provider treats this error as retryable in
src/robust_provider/errors.rs:123, so it retries until the 5 second call timeout and reportsOperation timed out. That hides the real error.