-
Notifications
You must be signed in to change notification settings - Fork 17.6k
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
iter: TestPull failures #66017
Comments
Found new dashboard test flakes for:
2024-02-27 23:58 gotip-darwin-amd64_13 go@96e9838f iter:iter.TestPull/2 (log)
|
I think this test might just have an issue with background goroutines getting spawned or exiting. It shouldn't happen often but I suppose it can happen (e.g. a goroutine that is presumed to exit after it unblocked on a channel actually took a long time to unblock on it, or something). |
CC @rsc maybe? |
Found new dashboard test flakes for:
2024-03-15 03:39 gotip-darwin-amd64_13 go@453cbb8f iter:iter.TestPull/3 (log)
|
Found new dashboard test flakes for:
2024-05-06 15:34 gotip-darwin-amd64_14 go@3c72dd51 iter:iter.TestPull2/0 (log)
|
Found new dashboard test flakes for:
2024-05-07 18:36 netbsd-386-9_3 go@709d6d5d iter.TestPull2 (log)
|
Found new dashboard test flakes for:
2024-05-07 15:21 gotip-darwin-amd64-longtest go@38ee0c76 iter.TestPull/3 (log)
|
Found new dashboard test flakes for:
2024-05-08 19:10 gotip-linux-arm64-race go@69e75c85 iter.TestPull2/1 (log)
|
Found new dashboard test flakes for:
2024-05-17 00:11 gotip-linux-amd64-race go@69105d79 iter.TestPull2/3 (log)
|
Found new dashboard test flakes for:
2024-05-15 21:51 gotip-freebsd-riscv64 go@13d36a9b iter.TestPull2/0 (log)
|
Found new dashboard test flakes for:
2024-05-17 17:15 gotip-darwin-amd64_13 go@01ad44bc iter:iter.TestPull/2 (log)
|
Found new dashboard test flakes for:
2024-05-22 13:40 gotip-linux-arm64-boringcrypto go@bb2b7363 iter.TestPull2/0 (log)
|
Change https://go.dev/cl/587917 mentions this issue: |
This is still happening. |
I'm not sure it is. All the reported failures in #68118, #68119, and #68120 are from mid-May, before this was fixed on May 24th. I don't know why watchflakes only recently opened issues for these failures, but I don't think there's anything to do here. Closing, but if I got something wrong please feel free to reopen. |
Ah ha, sorry for the noise. |
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: