-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
selftests: mptcp_connect.sh
: disconnect test timed out
#499
Comments
It looks like we just got it a second time (after 64 other attempts without issues):
|
The netdev CI might have got the same issues, with other subtests:
Here as well the MPTCP connection is in Same here:
Note that all failed tests are using the same IP for both the client and the server, maybe a link? |
I think (I'm reasonably sure) this last batch of failures have a different root cause: there is a MPTcpExtRcvPruned even (packet drop after sending the mptcp-level ack due to memory limits) and the transfer is partial. I think/fear addressing this later issue for good requires a significant refactor |
Our CI (first time) just found a similar issue with a debug kernel config
But here, there was a fallback to TCP! (MPTCP → TCP) https://github.com/multipath-tcp/mptcp_net-next/actions/runs/10109852800 |
This issue has been seen on NIPA, with a debug kernel config: the disconnect test in v4 with MPTCP on both side failed with a timeout:
From: contest - stdout
Note that the test has been re-run, and the test passed the second time.
The text was updated successfully, but these errors were encountered: