ci: Upgrade execution-specs to tests@v20.0.1 - #1579
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1579 +/- ##
==========================================
+ Coverage 97.46% 97.47% +0.01%
==========================================
Files 170 170
Lines 15448 15448
Branches 3618 3618
==========================================
+ Hits 15056 15058 +2
+ Misses 284 283 -1
+ Partials 108 107 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
chfast
force-pushed
the
ci/tests-v20.0.0
branch
from
August 9, 2026 12:31
89e5231 to
daa6030
Compare
chfast
force-pushed
the
ci/tests-v20.0.0
branch
from
August 9, 2026 12:34
daa6030 to
9d835d3
Compare
There was a problem hiding this comment.
Pull request overview
Updates CircleCI to fetch execution-spec test fixtures from ethereum/execution-specs releases (new fixtures<suffix>.tar.gz naming) and bumps the pinned fixture releases accordingly.
Changes:
- Switch fixture download source from
ethereum/execution-spec-teststoethereum/execution-specs. - Update fixture archive naming from
fixtures_<suffix>.tar.gztofixtures<suffix>.tar.gzwith an empty default suffix. - Bump fixture releases to
tests@v20.0.1andtests-glamsterdam-devnet@v6.1.1.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
The fixture source moves from the archived ethereum/execution-spec-tests releases to ethereum/execution-specs, where the tarball is named fixtures<suffix>.tar.gz, so the suffix carries its own separator and defaults to none. The glamsterdam-devnet pin follows to v6.1.1. The download step names the repository it fetches from, fails on an HTTP error instead of unpacking the error page, and drops any leftover archive, which shares its name with every other release of the same suffix. The transactions in these fixtures are taken from their encodings, whose signatures the state test runner now verifies, so the bad_v_r_s and invalid_chain_id cases they add are rejected as they should be.
chfast
force-pushed
the
ci/tests-v20.0.0
branch
from
August 9, 2026 13:14
9d835d3 to
4d8f376
Compare
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.
Move the fixture source from the archived ethereum/execution-spec-tests releases to ethereum/execution-specs, where the tarball is named
fixtures<suffix>.tar.gz, so the suffix carries its own separator and defaults to none; the glamsterdam-devnet pin follows to v6.1.1. The transactions in these fixtures are taken from their encodings, whose signatures the state test runner now verifies, so the bad_v_r_s and invalid_chain_id cases they add are rejected as they should be.