test: support interpreter test in evmone unittest - #267
Merged
Conversation
zoowii
reviewed
Jan 19, 2026
| bash .ci/run_test_suite.sh | ||
| build_test_release_evmone_unittests_on_x86: | ||
| name: Test DTVM-EVM multipass using evmone unit tests in release mode on x86-64 | ||
| name: Test DTVM-EVM multipass with interpreter using evmone unit tests in release mode on x86-64 |
ys8888john
force-pushed
the
add_interpreter_unittest
branch
from
January 19, 2026 10:47
eb9ceb8 to
c9a5ece
Compare
Contributor
|
conflict @ys8888john |
ys8888john
force-pushed
the
add_interpreter_unittest
branch
from
January 19, 2026 11:40
c9a5ece to
06c1f69
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
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.
1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):
2. What is the scope of this PR (e.g. component or file name):
3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):
4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):
5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:
6. Release note