-
Notifications
You must be signed in to change notification settings - Fork 91
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(consume): Add consume cache
, and --input
flag accepts versioned release names
#1044
Open
marioevz
wants to merge
14
commits into
main
Choose a base branch
from
consume-cache
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
marioevz
added
scope:consume
Scope: Consume command suite
scope:fw
Scope: Framework (evm|tools|forks|pytest)
scope:tooling
Scope: Python tools (uv, ruff, tox,...)
type:feat
type: Feature
labels
Dec 26, 2024
marioevz
force-pushed
the
consume-cache
branch
from
January 3, 2025 18:29
7e3d6f7
to
d874956
Compare
marioevz
changed the title
feat(consume): Add
feat(consume): Add Jan 6, 2025
consume cache
and --release
flagconsume cache
, and --input
flag accepts versioned release names
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
scope:consume
Scope: Consume command suite
scope:fw
Scope: Framework (evm|tools|forks|pytest)
scope:tooling
Scope: Python tools (uv, ruff, tox,...)
type:feat
type: Feature
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.
🗒️ Description
consume cache
commandTakes same inputs as other
consume
commands, but it's only used to download and cache fixtures.Useful to create docker containers and download the fixtures during the image creation process instead of each time the container runs.
The
--cache-folder
flag can also be specified to use a specific folder as cache, and when omitted it defaults toethereum-execution-spec-tests/cached_downloads
placed inside of the folder returned byplatformdirs.user_cache_dir
.Release name parsing for
--input
flagThe
--input
flag now accepts release tags in the form<RELEASE_NAME>@<RELEASE_VERSION>
, where<RELEASE_VERSION>
can be in formatv1.2.3
or the keywordlatest
to automatically fetch the latest version.It uses the GitHub API to fetch the list of releases and automatically download the specified version for the given release name.
The list of releases is cached and only re-downloaded after 10 minutes have passed since the last query, except when running inside of a docker container or in CI, in order to cache only during image creation.
Keywords
latest-stable-release
andlatest-develop-release
are deprecated in favor ofstable@latest
ordevelop@latest
respectively.Hive instance information
The
/hive
endpoint of the hive server is now used to fetch information about the hive instance being used to execute the tests.Information such as the client file used to configure the clients is now fetched and placed inside of the test description to aid on reproducibility.
🔗 Related Issues
None
✅ Checklist
mkdocs serve
locally and verified the auto-generated docs for new tests in the Test Case Reference are correctly formatted.