Skip to content
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

e2e-tests panicked at 'We should find a port before the reader ends', #1259

Closed
gcp-development opened this issue Aug 5, 2023 · 5 comments
Closed
Labels
bug Something isn't working

Comments

@gcp-development
Copy link

gcp-development commented Aug 5, 2023

I am doing a basic E2E test using the flipper example.

I have install the substrate-contracts-node and its working fine.

I am running with the "nightly-2023-02-09" (cargo +nightly-2023-02-09 test --features e2e-tests)
I have tried with previous ones all give the same error below.

And I am getting this error message:

---- flipper::e2e_tests::it_works stdout ----
thread 'flipper::e2e_tests::it_works' panicked at 'We should find a port before the reader ends', /home/silveira/.cargo/registry/src/github.com-1ecc6299db9ec823/ink_e2e-4.2.1/src/node_proc.rs:192:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Contract Version:

image

Ubuntu

image

Cargo.toml

[package]
name = "flipper"
version = "0.1.0"
authors = ["Parity Technologies <admin@parity.io>"]
edition = "2021"
publish = false

[dependencies]
ink = { version = "4.2.1", default-features = false }

scale = { package = "parity-scale-codec", version = "3.6.3", default-features = false, features = ["derive"] }
scale-info = { version = "2.5", default-features = false, features = ["derive"], optional = true }

[dev-dependencies]
ink_e2e = { version = "4.2.1" }

[lib]
path = "src/lib.rs"

[features]
default = ["std"]
std = [
    "ink/std",
    "scale/std",
    "scale-info/std",
]
ink-as-dependency = []
e2e-tests = []

@gcp-development gcp-development added the bug Something isn't working label Aug 5, 2023
@SkymanOne
Copy link
Contributor

3.1.0 has been yanked. Please refer to this guide

@gcp-development
Copy link
Author

gcp-development commented Aug 5, 2023

Closing this one because this is being handle already in here:
#1239

This issue didn't go away it will be solved only when the e2e test is updated.

@gcp-development
Copy link
Author

This bug continues to exists, despite a new version has being release.

cargo-contract-contract 3.2.0-unknown-x86_64-unknown-linux-gnu
Reopen until is sorted.

Cheers

@ascjones
Copy link
Collaborator

The ink_e2e crate is separate from cargo-contract.

This issue should have been fixed in the new ink release https://crates.io/crates/ink_e2e/4.3.0. If you continue to experience the issue, please open an issue in the https://github.com/paritytech/ink/ repo

@gcp-development
Copy link
Author

Thanks @ascjones
Cheers,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants