-
Notifications
You must be signed in to change notification settings - Fork 119
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
s2n-quic server fails resumption interop test with neqo client #2192
Comments
Sorry for the trouble here @goatgoose. mozilla/neqo#1837 fixed the issue. The The |
Hi @mxinden, it appears that even after the mozilla/neqo#1837 fix, the neqo client and s2n-quic server still fail the resumption test. From mozilla/neqo#1857 (comment):
However, looking at the interop runner, it seems like mozilla/neqo#1837 fixed the issue for all implementations except for s2n-quic: So we plan to investigate this to see if s2n-quic is causing this issue. |
I'm looking at the download of the second URL in https://interop.seemann.io/logs/2024-07-25T16:32/s2n-quic_neqo/resumption/output.txt. One thing that looks odd from neqo's perspective is that we're receving Otherwise, I can't tell from the log why we wouldn't send a |
This is expected. s2n-quic sends the
I'm currently having some trouble building on arm64 so this might take some time. |
This was a neqo bug: mozilla/neqo#2067 |
Problem:
The resumption interop test has recently started failing with the neqo client and s2n-quic server. neqo has released a fix related to this issue (mozilla/neqo#1837), but the interop test is still failing with neqo and s2n-quic.
Solution:
We should investigate the cause of this test failure. If the issue can be addressed in s2n-quic, we should resolve it and revert #2191 to enforce the resumption test with neqo and s2n-quic in CI.
The text was updated successfully, but these errors were encountered: