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

Flaky test in SPU stream_fetch #947

Closed
nicholastmosher opened this issue Apr 9, 2021 · 2 comments
Closed

Flaky test in SPU stream_fetch #947

nicholastmosher opened this issue Apr 9, 2021 · 2 comments
Assignees
Labels
Milestone

Comments

@nicholastmosher
Copy link
Contributor

nicholastmosher commented Apr 9, 2021

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:

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.

image

@sehz sehz self-assigned this Apr 9, 2021
@sehz sehz added this to the 0.7.4 milestone Apr 9, 2021
@sehz sehz added SPU SPU related technical debt and removed stability labels Apr 9, 2021
@sehz sehz modified the milestones: 0.7.4, 0.7.5 Apr 22, 2021
@sehz sehz modified the milestones: 0.8.1, 0.8.2 May 3, 2021
@sehz
Copy link
Contributor

sehz commented May 3, 2021

Make this as optional test in CI

@nicholastmosher
Copy link
Contributor Author

Closed by #1070

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants