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

ping: fix flaky test #1617

Merged
merged 1 commit into from
Jun 30, 2022
Merged

ping: fix flaky test #1617

merged 1 commit into from
Jun 30, 2022

Conversation

marten-seemann
Copy link
Contributor

Fixes #1616.

If we end up with 2 connections (TCP and QUIC) between the nodes, the dialing node might close one of those connection.
This will cause a stream reset on the connection that the dialed node might have chosen for its ping stream.


err = h1.Connect(ctx, peer.AddrInfo{
ID: h2.ID(),
Addrs: h2.Addrs(),
Addrs: []ma.Multiaddr{h2.Addrs()[0]},
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a change we can do that does this at a higher level? I think we see this flakiness in other tests too.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

True, this is not the first time I'm submitting a patch like this.

At which level would you suggest to do it?

@marten-seemann marten-seemann merged commit 95e9ff7 into master Jun 30, 2022
@MarcoPolo MarcoPolo mentioned this pull request Jul 7, 2022
41 tasks
@ajnavarro ajnavarro mentioned this pull request Aug 24, 2022
72 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

flaky TestPing
2 participants