-
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/http: TestServerShutdown failures #56421
Comments
Found new dashboard test flakes for:
2022-10-25 00:18 linux-amd64-buster go@9fffcde1 net/http.TestServerShutdown (log)
|
Is this a duplicate of #56036? (Compare #38305, #54758 (comment).) |
Found new dashboard test flakes for:
2022-10-27 01:24 dragonfly-amd64-622 go@612bb34a net/http.TestServerShutdown (log)
2022-10-31 20:45 linux-amd64-nounified go@76940b3e net/http.TestServerShutdown (log)
|
Found new dashboard test flakes for:
2022-11-15 00:27 linux-amd64 go@f977ffe8 net/http.TestServerShutdown (log)
|
(attn @neild) |
Yes, due to the test being renamed from |
Found new dashboard test flakes for:
2022-11-11 01:29 linux-386-sid go@4d37f968 net/http.TestServerShutdown (log)
|
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Found new dashboard test flakes for:
2023-02-09 23:41 linux-arm64 go@fb79da29 net/http.TestServerShutdown (log)
|
Found new dashboard test flakes for:
2023-02-27 11:56 linux-amd64 go@0d52401e net/http.TestServerShutdown (log)
|
Found new dashboard test flakes for:
2023-03-01 21:50 linux-386-bullseye go@3243f937 net/http.TestServerShutdown (log)
|
Found new dashboard test flakes for:
2023-03-13 14:20 dragonfly-amd64-622 go@b6f29d23 net/http.TestServerShutdown (log)
|
Change https://go.dev/cl/476036 mentions this issue: |
Change https://go.dev/cl/483896 mentions this issue: |
We don't have a way to terminate the leaked goroutines, and we can't wait forever for them to exit (or else we would risk timing out the test and losing the log line describing what exactly leaked). So we have reason to believe that they will remain leaked while we run the next test, and we don't want the goroutines from the first leak to generate a spurious error when the second test completes. This also removes a racy Parallel call I added in CL 476036, which was flagged by the race detector in the duplicate-suppression check. (I hadn't considered the potential interaction with the leak checker.) For #59526. Updates #56421. Change-Id: Ib1f759f102fb41ece114401680cd728343e58545 Reviewed-on: https://go-review.googlesource.com/c/go/+/483896 TryBot-Result: Gopher Robot <[email protected]> Reviewed-by: Michael Pratt <[email protected]> Auto-Submit: Bryan Mills <[email protected]> Run-TryBot: Bryan Mills <[email protected]>
Found new dashboard test flakes for:
2023-11-07 17:04 linux-amd64 go@46fb7816 net/http.TestServerShutdown (log)
|
Found new dashboard test flakes for:
2024-01-09 18:15 linux-amd64-boringcrypto go@a95136a8 net/http.TestServerShutdown (log)
|
Commit a95136a is also on |
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: