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
This is probably because the test is creating actual sockets, which might be making it vulnerable to shakiness if the underlying system isn't ready. We should probably create some kind of timeout/retry mechanism to the test.
Here is the error from CI:
cd src/socket; cargo test --no-default-features --features tls test_multiplexing_native_tls
...
Running target/debug/deps/fluvio_spu-f81824b57bd12f41
running 15 tests
test controllers::follower_replica::state::test::test_insert_and_remove_state ... ok
test controllers::leader_replica::replica_state::test::test_follower_hw22_sync ... ok
test controllers::leader_replica::replica_state::test::test_follower_hw32_sync ... ok
test controllers::leader_replica::replica_state::test::test_follower_hw33_sync ... ok
test controllers::leader_replica::replica_state::test::test_leader_update_sync ... ok
test controllers::leader_replica::leaders_state::test_channel::test_event_shutdown_sync ... ok
test core::spus::metadata::test::test_indexed_by_id ... ok
test core::spus::metadata::test::test_peer_spu_routines ... ok
test core::store::test::test_apply_changes ... ok
test core::store::test::test_sync_all ... ok
test controllers::replica_test::test_initial_replication_sync ... ok
Apr 09 13:59:36.588 ERROR fluvio_socket::multiplexing: error sending to socket, no socket receiver founded for id: 2, abandoning sending
test services::public::stream_fetch::test::test_stream_filter_fetch_sync ... ok
test services::public::stream_fetch::test::test_stream_filter_max_sync ... ok
test smart_stream::filter::test::test_file ... ok
test services::public::stream_fetch::test::test_stream_fetch_sync ... test services::public::stream_fetch::test::test_stream_fetch_sync has been running for over 60 seconds
Error: The action has timed out.
The text was updated successfully, but these errors were encountered:
The following test has been causing a bunch of sporadic test failures in CI:
This is probably because the test is creating actual sockets, which might be making it vulnerable to shakiness if the underlying system isn't ready. We should probably create some kind of timeout/retry mechanism to the test.
Here is the error from CI:
The text was updated successfully, but these errors were encountered: