You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: