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.

Sign up for GitHub

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

Jump to bottom

zerortt QNS interop failures #1874

Open
larseggert opened this issue May 3, 2024 · 2 comments · May be fixed by #1998
Open

zerortt QNS interop failures #1874

larseggert opened this issue May 3, 2024 · 2 comments · May be fixed by #1998

Comments

@larseggert
Copy link
Collaborator

Our client randomly fails zerortt interop tests with various servers. This seems to happen, because while the client correctly sends a lot of stream data in 0-RTT packets, it declares them all as lost and retransmits everything in 1-RTT, causing the interop runner to (correctly) declare a failure.
@larseggert
Copy link
Collaborator Author

Still happening, e.g., https://interop.seemann.io/logs/2024-07-18T01:39/quic-go_neqo/zerortt/output.txt

@larseggert larseggert mentioned this issue Jul 19, 2024
Closed
@larseggert
Copy link
Collaborator Author

I bisected this, and I'm reasonably sure this got broken by 4852dc6, i.e., DPLPMTUD.

(Reasonably, because the interop test only fails sporadically. I ran repeated runs for at least ten minutes against quic-go as server, and that's the commit it landed on. 4852dc6 is definitely bad, but maybe an earlier one is already bad but wasn't caught. Unlikely though.)

@larseggert larseggert linked a pull request Jul 21, 2024 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: No time-based loss detection before largest_acked & fixes larseggert/neqo
1 participant
@larseggert