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

Jump to bottom

net/http: TestTransportMaxConnsPerHost failure with "too many dials" on windows-arm64-11 #51147

Closed
bcmills opened this issue Feb 11, 2022 · 1 comment
Closed

net/http: TestTransportMaxConnsPerHost failure with "too many dials" on windows-arm64-11 #51147

bcmills opened this issue Feb 11, 2022 · 1 comment
Labels
arch-arm64 NeedsFix The path to resolution is known, but the work has not been done. OS-Windows Testing An issue that has been verified to require only test changes, not just a test failure.
Milestone
Go1.21

Comments

@bcmills
Copy link
Member

bcmills commented Feb 11, 2022 •
edited 

--- FAIL: TestTransportMaxConnsPerHost (0.02s)
    transport_test.go:678: round 1: too many dials (https): 2 != 1
    transport_test.go:681: round 1: too many get connections (https): 2 != 1
    transport_test.go:684: round 1: too many tls handshakes (https): 2 != 1
2022/02/09 21:55:39 http: TLS handshake error from 127.0.0.1:51228: read tcp 127.0.0.1:51227->127.0.0.1:51228: wsarecv: An established connection was aborted by the software in your host machine.
FAIL
FAIL	net/http	7.785s

greplogs --dashboard -md -l -e 'FAIL: TestTransportMaxConnsPerHost .*(?:\n .*): too many' --since=2021-04-16

2022-02-09T21:50:10-20c300b/windows-arm64-11

CC @neild
@bcmills bcmills added this to the Backlog milestone Feb 11, 2022
@bcmills bcmills added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Feb 11, 2022
@bcmills bcmills mentioned this issue Sep 8, 2022
Closed
@bcmills bcmills mentioned this issue Apr 7, 2023
Closed
@gopherbot
Copy link

Change https://go.dev/cl/483116 mentions this issue: net/http: wait forever for write results in tests

@dmitshur dmitshur modified the milestones: Backlog, Go1.21 May 24, 2023
@dmitshur dmitshur added NeedsFix The path to resolution is known, but the work has not been done. Testing An issue that has been verified to require only test changes, not just a test failure. and removed NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels May 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
arch-arm64 NeedsFix The path to resolution is known, but the work has not been done. OS-Windows Testing An issue that has been verified to require only test changes, not just a test failure.
Projects
None yet
Milestone
Go1.21
Development

No branches or pull requests
3 participants
@dmitshur @bcmills @gopherbot