-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Return socket correctly in socket_reuse_port #22017
Conversation
I think the problem is #20362 . Appears that failures from tests run under process 1, i.e., |
3bfea97
to
1719e14
Compare
ecca93a
to
6fa26d1
Compare
I am going to be merging this soon. Linux CI passes cleanly though it appears that the Linux version used for CI does not support SO_REUSEPORT. The CI logs print an informational string "INFO: SO_REUSEPORT is unsupported, skipping reuseport tests." if this is the case. Linux kernel 3.9 and later support SO_REUSEPORT |
* Return socket correctly in socket_reuse_port * Run reuseport tests only if SO_REUSEPORT is supported. * Test fix - test for successful addition of workers in distributed test (cherry picked from commit d3bc329)
* Return socket correctly in socket_reuse_port * Run reuseport tests only if SO_REUSEPORT is supported. * Test fix - test for successful addition of workers in distributed test (cherry picked from commit d3bc329)
* Return socket correctly in socket_reuse_port * Run reuseport tests only if SO_REUSEPORT is supported. * Test fix - test for successful addition of workers in distributed test (cherry picked from commit d3bc329)
Should fix buildbot failure #21818 (comment)
A bit of a mystery as to how Linux CI passed correctly.....