Missing EVM restrictions and EOF compatibility in tests #15816
Merged
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
clonker
approved these changes
Feb 3, 2025
cameel
force-pushed
the
missing-evm-restrictions-and-eof-compatibility-in-tests
branch
from
3122985 to
d7af663
Compare
cameel
deleted the
missing-evm-restrictions-and-eof-compatibility-in-tests
branch
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.
Fixes the failures in the nightly workflow caused by a test from #15788 missing EVM version restriction (
t_ubu_soltest_alljob 1749992).Also addresses EOF-compatibility of some of the tests added in #15712 (
t_ubu_soltest_deprecated_evm_versionsjob 1749408). It went unnoticed because the failures only show up in #15666, where we enable testing on EOF by default.