We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Thank @tersec for reporting it:
https://github.com/ethereum/consensus-specs/tree/v1.5.0-alpha.0/tests/formats/operations states that there should be a .ssz_snappy for each test, but
https://github.com/ethereum/consensus-spec-tests/tree/v1.5.0-alpha.0/tests/minimal/electra/operations/consolidation/pyspec_tests/multiple_consolidations_below_churn
https://github.com/ethereum/consensus-spec-tests/tree/v1.5.0-alpha.0/tests/minimal/electra/operations/consolidation/pyspec_tests/multiple_consolidations_equal_churn
https://github.com/ethereum/consensus-spec-tests/tree/v1.5.0-alpha.0/tests/minimal/electra/operations/consolidation/pyspec_tests/multiple_consolidations_equal_twice_churn etc only have pre/post states?
The text was updated successfully, but these errors were encountered:
test_multiple_consolidations_*
hwwhww
Successfully merging a pull request may close this issue.
Thank @tersec for reporting it:
https://github.com/ethereum/consensus-specs/tree/v1.5.0-alpha.0/tests/formats/operations states that there should be a .ssz_snappy for each test, but
https://github.com/ethereum/consensus-spec-tests/tree/v1.5.0-alpha.0/tests/minimal/electra/operations/consolidation/pyspec_tests/multiple_consolidations_below_churn
https://github.com/ethereum/consensus-spec-tests/tree/v1.5.0-alpha.0/tests/minimal/electra/operations/consolidation/pyspec_tests/multiple_consolidations_equal_churn
https://github.com/ethereum/consensus-spec-tests/tree/v1.5.0-alpha.0/tests/minimal/electra/operations/consolidation/pyspec_tests/multiple_consolidations_equal_twice_churn etc only have pre/post states?
The text was updated successfully, but these errors were encountered: