-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
net: TestMultiPathTCP
from mptcpsock_linux_test times out
#68717
Comments
TestMultiPathTCP
from mptcpsock_linux_test times out
CC @neild It appears the timeout happened in Go 1.21.9, per the output you shared. Just noting that because your Go version is listed as go 1.20.10, which is no longer supported. |
You’re right, thanks! Mixed them up |
Tried setting |
Hello,
Mmh, are you sure you are using a Debian Bullseye image? In the logs, it looks like your kernel is coming from Fedora 37 (which has been marked as End Of Life in 2023):
In your check above (the curl command is missing), it looks like you are checking with an old version of MPTCP (RFC6824), not compatible with the new one. If you want to check on your side, you need to look at instructions from here. With Debian 11, and the default kernel, you should not have MPTCP support (no files under Can you then reproduce the issue with the verbose mode please? cd <YOUR GO DIRETORY>/src
../bin/go test -v net -run "^TestMultiPathTCP$"
The test will set one and the other. It is not supposed to be set before running the tests.
Mmh, strange, but I guess that's because you are using an (outdated) kernel from Fedora. Anyway, if the |
Go version
1.21.9
Output of
go env
in your module/workspace:What did you do?
I'm trying to build Go 1.21.x. I've previously successfully built 1.18 and 1.20.10, so my configuration should be capable of doing so. I've downloaded the repo by tag
go1.21.9
, have set environment variablesGOOS=linux, GOARCH=amd64, GOMAXPROCS=$(nproc)
, and launched the building of Golang source usingGOROOT_BOOTSTRAP=/usr/local/go1.20.10 ./all.bash
.GOROOT_BOOTSTRAP
is used here to explicitly set the Go source path, despite having the binaries in PATH. It wouldn't work without it.My build script:
What did you see happen?
An error message and a huge stacktrace after
TestMultiPathTCP
test fromsrc/net/mptcpsock_linux_test.go
timeouted after 9 minutes running. This test was included right in the 1.21 major release.What did you expect to see?
A successful test run.
Apparently, this test was enabled only for systems that support Multipath TCP - release notes
I've checked if my image, based on Debian Bullseye, supports it, and supposedly it does not:
The text was updated successfully, but these errors were encountered: