Skip to content

chore(tests): drop stale EIP-8037 fork split in BAL insufficient-funds test - #3545

Merged
fselmo merged 2 commits into
ethereum:forks/amsterdamfrom
shubham5080:chore/drop-bal-8037-fork-split
Sep 8, 2026
Merged

fselmo merged 2 commits into
ethereum:forks/amsterdamfrom
shubham5080:chore/drop-bal-8037-fork-split

Conversation

@shubham5080

@shubham5080 shubham5080 commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

Description

Removes the dead fork.is_eip_enabled(8037) branch in test_bal_call_revert_insufficient_funds.

This file is valid_from("Amsterdam"), and Amsterdam always enables EIP-8037, so the pre-8037 else path was unreachable. The accompanying TODO waited on #2473 being consolidated into Amsterdam; that PR already merged, and EIP-8037 (#2901) kept the early code-read behavior that this test asserts.

Also drops the unused fork fixture argument from the test and updates the docstring/comment to match current Amsterdam behavior.

Filled locally:

uv run fill tests/amsterdam/eip7928_block_level_access_lists/test_block_access_lists_opcodes.py::test_bal_call_revert_insufficient_funds --from Amsterdam --until Amsterdam --clean

24 passed.

Related Issues or PRs

Follow-up cleanup after #2473 and #2901.

Checklist

  • Ran fast static checks to avoid CI fails, see Code Standards & Verifying Changes: just static
  • PR title has the form <type>(<area>): <title>, where <type> and <area> come from an appropriate C-<type>, respectively A-<area>, label. The title should match the target squash commit message.

Cute Animal Picture

otter

…s test

This file is valid_from Amsterdam where EIP-8037 is always enabled, so the
pre-8037 branch and ethereum#2473 TODO were unreachable dead code.

Co-authored-by: Cursor <cursoragent@cursor.com>
@fselmo
fselmo merged commit 9608b09 into ethereum:forks/amsterdam Sep 8, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants