Closed 0xf333 closed 1 year ago
I believe the problem here is that the latest substrate-contracts-node
is not compatible with the released 4.2.1
of ink_e2e
on crates.io. This is because of changes to the port discovery string.
ink! version: 4.2.1 ink_e2e version: 4.2.1 substrate-contracts-node version: 0.30.0-72e68577688
^^ These are not compatible. You need an earlier substrate-contracts-node
version for 4.2.1
Otherwise use ink
master branch which is compatible with substrate-contracts-node version: 0.30.0-72e68577688
See https://github.com/paritytech/ink/pull/1876#pullrequestreview-1578317652
This should be fixed in 4.3.0
and also 5.0.0-alpha
Description:
End-to-end tests (
e2e-tests
feature) for the Ink contracts fail to run even whensubstrate-contracts-node
is installed and setup properly.Steps to Reproduce:
Make sure you have the latest
substrate-contracts-node
andcargo-contract
installed; if you don't please run:and
clone this repo
Navigate to the
flipper
contract directory:First, run the following command to build:
And then run this command for the E2E test:
Expected Behavior:
The E2E test should run successfully.
Actual Behavior:
The E2E test fails regardless of having
substrate-contracts-node
installed. Even if you are running the node in the background and then run the E2E test, it will still fail.https://github.com/paritytech/ink/assets/100840345/1ab31641-4a8a-4a5d-816f-0e2f6cb2ca3e
Environment:
OS
: Debiancargo-contract
version 3.0.1ink!
version: 4.2.1ink_e2e
version: 4.2.1substrate-contracts-node
version: 0.30.0-72e68577688Rustc
version: 1.71.1stable
.