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.

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/http: frequent test failures with "Only one usage of each socket address" on windows-amd64-longtest #47016

Open
bcmills opened this issue Jul 1, 2021 · 3 comments

Comments

@bcmills
Copy link
Member

@bcmills bcmills commented Jul 1, 2021

What version of Go are you using?

release-branch.go1.15

Does this issue reproduce with the latest release?

No.

What did you expect to see?

Tests on the current release branches (release-branch.go1.15 and release-branch.go1.16) consistently passing, especially for all first class ports.

What did you see instead?

Tests on the windows-amd64-longtest builder started failing intermittently in March, got better for a while in May, and are now failing in net/http on just about every run (https://build.golang.org/?repo=&branch=release-branch.go1.15#short):
image

The failure mode consists of many Only one usage of each socket address errors (https://build.golang.org/log/30a479e652cc31796c8d900ab0494ffff5765266), sometimes accompanied by a test deadlock or timeout (https://build.golang.org/log/3ff9e1b80ee03390ebb171468f0fb00ceb23795d).

These failures result in TryBot / SlowBot failures on the release branch for unrelated backports (https://golang.org/cl/332330). Since the builders are consistently broken, there is a substantial risk that these failures will cause some other regression on this branch to go unnoticed.

CC @neild @golang/release

@cagedmantis
Copy link
Contributor

@cagedmantis cagedmantis commented Jul 1, 2021

I believe the work to try and resolve this issue has been previously tracked in #45358.

@bcmills
Copy link
Member Author

@bcmills bcmills commented Jul 2, 2021

I believe the work to try and resolve this issue has been previously tracked in #45358.

Yeah, it's closely related.

I actually tried to find that issue before filing this one, but it didn't turn up in my search results — the problem described in the issue title seems to have been addressed, and the string in the current error message isn't mentioned in that issue at all. 😕

@dmitshur
Copy link
Contributor

@dmitshur dmitshur commented Jul 12, 2021

This flaky failure continues to be an issue but we're not going to block Go 1.15.14 on it. Moving to next milestone.

@dmitshur dmitshur removed this from the Go1.15.14 milestone Jul 12, 2021
@dmitshur dmitshur added this to the Go1.15.15 milestone Jul 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants