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.

Sign up for GitHub

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: TestClientTimeout_Headers failures #63365

Closed
gopherbot opened this issue Oct 4, 2023 · 3 comments
Closed

net/http: TestClientTimeout_Headers failures #63365

gopherbot opened this issue Oct 4, 2023 · 3 comments
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.

Comments

@gopherbot
Copy link 

#!watchflakes
default <- pkg == "net/http" && test == "TestClientTimeout_Headers"

Issue created automatically to collect these failures.

Example (log):

--- FAIL: TestClientTimeout_Headers (0.00s)
    --- FAIL: TestClientTimeout_Headers/h1 (0.01s)
        client_test.go:1313: error string = "Get \"http://127.0.0.1:51755\": context deadline exceeded"; missing timeout substring

— watchflakes
@gopherbot gopherbot added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Oct 4, 2023
@gopherbot
Copy link
Author

Found new dashboard test flakes for:

#!watchflakes
default <- pkg == "net/http" && test == "TestClientTimeout_Headers"
2023-10-04 02:55 windows-amd64-2016 go@9018601e net/http.TestClientTimeout_Headers (log) 
--- FAIL: TestClientTimeout_Headers (0.00s)
    --- FAIL: TestClientTimeout_Headers/h1 (0.01s)
        client_test.go:1313: error string = "Get \"http://127.0.0.1:51755\": context deadline exceeded"; missing timeout substring

— watchflakes

@bcmills
Copy link
Contributor

bcmills commented Oct 13, 2023

This looks like #43120, but on amd64 instead of arm.

@bcmills
Copy link
Contributor

bcmills commented Oct 13, 2023

Duplicate of #43120

@bcmills bcmills marked this as a duplicate of #43120 Oct 13, 2023
@bcmills bcmills closed this as not planned Won't fix, can't repro, duplicate, stale Oct 13, 2023
@bcmills bcmills mentioned this issue Oct 13, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bcmills @gopherbot