Skip to content

feat(spec-tests, spec-tools): run fork-transition fixtures through EELS [backport benchmarks/amsterdam] - #3624

Open
github-actions[bot] wants to merge 1 commit into
benchmarks/amsterdamfrom
backports/3564-to-benchmarks/amsterdam
Open

github-actions[bot] wants to merge 1 commit into
benchmarks/amsterdamfrom
backports/3564-to-benchmarks/amsterdam

Conversation

@github-actions

Copy link
Copy Markdown

Automated backport of #3564 to benchmarks/amsterdam.

…LS (#3564)

Co-authored-by: danceratopz <danceratopz@gmail.com>
(cherry picked from commit 6f426b3)
@github-actions github-actions Bot added A-spec-specs Area: Specification—The Ethereum specification itself (eg. `src/ethereum/*`) A-spec-tools Area: Specification Tooling—Tools for the Ethereum specification (eg. `src/ethereum_spec_tools/*`) C-feat Category: an improvement or new feature labels Sep 21, 2026
@github-actions github-actions Bot added the C-feat Category: an improvement or new feature label Sep 21, 2026
@marioevz

Copy link
Copy Markdown
Member

Static fails because benchmarks/amsterdam is also missing #3307. @LouisTsai-Csie at this point I think it would be safe to simply rebase benchmarks/amsterdam to the latest forks/amsterdam or do we still need to keep them separated?

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-spec-specs Area: Specification—The Ethereum specification itself (eg. `src/ethereum/*`) A-spec-tools Area: Specification Tooling—Tools for the Ethereum specification (eg. `src/ethereum_spec_tools/*`) C-feat Category: an improvement or new feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants