-
Notifications
You must be signed in to change notification settings - Fork 5
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
eos-evm-node repo integration test #17
Conversation
Use eos-evm repo contract artifact.
Trying to manually solve error installing leap deb package around unmet dependencies.
Set up absolute paths as workflow step outputs to be reused in test invokation.
Having tests and peripherals in the build allows simply downloading the archived build artifact and having everything necessary to run integration tests. Update node.yaml workflow for using only the build artifact. It no longer needs to clone the eos-evm-node repository.
…nch an eos-evm-rpc. Also add error checking for the eos-evm-rpc logs and killing of the process at end of test.
run: | | ||
mkdir test_run_root | ||
cd test_run_root | ||
${{ steps.evm-node-build.outputs.EVM_NODE_BUILD }}/tests/nodeos_eos_evm_test.py -v --eos-evm-contract-root ${{ steps.evm-contract.outputs.EVM_CONTRACT }} --eos-evm-build-root ${{ steps.evm-node-build.outputs.EVM_NODE_BUILD }} --use-tx-wrapper ${{ steps.evm-node-build.outputs.EVM_NODE_BUILD }}/peripherals/tx_wrapper |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we consider setting up ctest?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure what that would look like since this is an integration test that requires access to leap
, leap-dev
, cdt
, eos-evm-contract
which may not be available locally for ctest
.
Seems this change is still necessary. This reverts commit 51c323c.
require is not defined in ES module scope, you should use import instead.
Update package-lock.json and yarn.lock
Resolves: #11
Port PR for leap integration test updates and workflow. (eosnetworkfoundation/eos-evm-contract#355)
Use
eos-evm
repo forcontract
artifact.leap
,leap-dev
,cdt
,eos-evm-contract
build.tar.gz
by omitting object files from uploaded artifact.nodeos_eos_evm_test.py
to work with changes made when porting code over toeos-evm-node
and splitting outeos-evm-rpc
into separate executable.nodeos_eos_evm_test.py
eos-evm-node
build, addstests
andperipherals
to build dir to be included in tarball artifact of build, and copies executables into thebin
directory.tx_wrapper/index.js