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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] test_connection_cleanups is flaky #3190

Closed
vicsn opened this issue Mar 26, 2024 · 2 comments 路 Fixed by #3192
Closed

[Bug] test_connection_cleanups is flaky #3190

vicsn opened this issue Mar 26, 2024 · 2 comments 路 Fixed by #3192
Assignees
Labels
bug Incorrect or unexpected behavior

Comments

@vicsn
Copy link
Collaborator

vicsn commented Mar 26, 2024

馃悰 Bug Report

It appears that sometimes, when a validator is picked in the test, it fails:

thread 'test_connection_cleanups' panicked at node/router/tests/cleanups.rs:74:9:
the deadline has elapsed for condition: tcp0.num_connected() == 1 && tcp1.num_connected() == 1
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

A quick print statement indicated: Unable to connect to '127.0.0.1:63168' - '127.0.0.1:63168' disconnected before sending "Message::ChallengeResponse"

Steps to Reproduce

cd node/router && cargo test test_connection_cleanups

Due to random sampling of the node type, the test only sometimes fails.

Expected Behavior

The test should pass.

Your Environment

Ran it on mainnet-staging 491f3078a

@niklaslong
Copy link
Contributor

niklaslong commented Mar 26, 2024

The fix is in #3164. Increasing the timeout a little ensures the test passes every time.

@niklaslong
Copy link
Contributor

niklaslong commented Mar 26, 2024

I may have spoken too soon, I'll investigate some more. It's less flaky with a longer timeout but it occasionally still fails 馃

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

Successfully merging a pull request may close this issue.

2 participants