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

Unable to parse valid port from substrate-contracts-node v0.42.0 #2335

Closed
cmichi opened this issue Dec 4, 2024 · 0 comments · Fixed by #2336
Closed

Unable to parse valid port from substrate-contracts-node v0.42.0 #2335

cmichi opened this issue Dec 4, 2024 · 0 comments · Fixed by #2336
Assignees
Labels
A-ink_e2e [ink_e2e] Work item C-bug Something isn't working

Comments

@cmichi
Copy link
Collaborator

cmichi commented Dec 4, 2024

The log output changed with paritytech/polkadot-sdk@09254eb. Our parsing can't handle that currently.

The error appears when runing the E2E tests on a contract:

$ cargo test  --features e2e-tests   
…
thread 'static_buffer::e2e_tests::e2e_run_out_of_buffer_memory' panicked at /Users/michi/projects/ink/crates/e2e/src/node_proc.rs:221:17:
valid port expected for tracing line, got '64224,[::1]:64225'

---- static_buffer::e2e_tests::buffer stdout ----
thread 'static_buffer::e2e_tests::buffer' panicked at /Users/michi/projects/ink/crates/e2e/src/node_proc.rs:221:17:
valid port expected for tracing line, got '64228,[::1]:64229'

The issue wasn't catched in our CI. The reason is that we (accidentally) don't pull the most recent substrate-contracts-node binary release for all CI stages. In that case the substrate-contracts-node binary present in the Docker image was used, and that one is old.

@cmichi cmichi added C-bug Something isn't working A-ink_e2e [ink_e2e] Work item labels Dec 4, 2024
@cmichi cmichi self-assigned this Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-ink_e2e [ink_e2e] Work item C-bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant