Conversation
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
2 participants
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.
currently pyspec vectors exist in 2 versions. in this repo and in eest releases which rises confusion to which are the latest vectors to run and trust. and Prague version of it is not supported by retesteth.
to avoid confusion I remove all this vectors from here. as we migrate the tests to eest.
please refer to pyspecs releases here: https://github.com/ethereum/execution-spec-tests/releases
the reason to have it here was to provide .json files to everyone from a repo rather than tar ball
and to verify the validity of .json schemas generated by pyspecs.