Skip to content

fix(tests): run Bogota fixtures on the Amsterdam spec in the json loader - #3696

Closed
AnkushinDaniil wants to merge 1 commit into
ethereum:eips/amsterdam/eip-8141from
AnkushinDaniil:daniil/json-loader-bogota-alias
Closed

AnkushinDaniil wants to merge 1 commit into
ethereum:eips/amsterdam/eip-8141from
AnkushinDaniil:daniil/json-loader-bogota-alias

Conversation

@AnkushinDaniil

Copy link
Copy Markdown

Description

Since the rebase onto newer forks/amsterdam (#3564), the json loader only knows forks that have an ethereum.forks.* module. Bogota is a test-only fork on the Amsterdam spec, so json-loader fails on AmsterdamToBogotaAtTime15k and validate-blocks drops every Bogota fixture and exits 5 in fill (bogota). This maps Bogota to the Amsterdam spec.

Checked locally: tests/json_loader/test_fork_transition_networks.py 24 passed. Filled 27 Bogota blockchain fixtures (-k nonce); validate-blocks on them gives exit 5 without the change and 53 passed with it.

Related Issues or PRs

Unblocks CI on #3682, #3683.

Checklist

  • Ran fast static checks to avoid CI fails: ruff check, ruff format --check on the changed file
  • PR title has the form <type>(<area>): <title>

@spencer-tb

Copy link
Copy Markdown
Contributor

Closing as we no longer need the alias :) we now have the real Bogota fork module from #3665

@spencer-tb spencer-tb closed this Oct 6, 2026
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