-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
runtime: TestNetpollDeadlock failures #66275
Comments
Found new dashboard test flakes for:
2024-03-08 22:14 linux-arm64-longtest go@c220fbab runtime.TestNetpollDeadlock (log)
2024-03-09 14:19 windows-amd64-longtest go@74726def runtime.TestNetpollDeadlock (log)
|
Found new dashboard test flakes for:
2024-03-12 17:24 linux-386-longtest go@34d28ba9 runtime.TestNetpollDeadlock (log)
|
@rsc, in triage, we think this may somehow be related to the timer refactor. The first failure happened immediately after the last CL of the refactor landed. (This is also plausible because timers affect netpoll deadlines.) However, what's weird is that the test is incredibly simple, basically just calling |
Found new dashboard test flakes for:
2024-03-08 22:14 gotip-linux-386-longtest go@3c39b2ed runtime:mayMoreStackPreempt.TestNetpollDeadlock (log)
2024-03-11 18:35 gotip-windows-amd64-longtest go@edbb5a13 runtime:mayMoreStackPreempt.TestNetpollDeadlock (log)
2024-03-12 17:04 gotip-windows-amd64-longtest go@5eb87c39 runtime:mayMoreStackPreempt.TestNetpollDeadlock (log)
2024-03-13 18:22 gotip-windows-amd64-longtest go@38723f2b runtime:mayMoreStackPreempt.TestNetpollDeadlock (log)
|
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: