-
Notifications
You must be signed in to change notification settings - Fork 17.5k
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
os/signal: TestTerminalSignal failures with subprogram failed: signal: killed
#57418
Comments
Found new dashboard test flakes for:
2022-12-19 21:31 darwin-amd64-10_15 go@75406751 os/signal.TestTerminalSignal (log)
|
Found new dashboard test flakes for:
2022-11-30 18:33 darwin-amd64-10_14 go@9f443332 os/signal.TestTerminalSignal (log)
2022-12-21 19:09 darwin-amd64-12_0 go@41eb70ae os/signal.TestTerminalSignal (log)
|
Found new dashboard test flakes for:
2023-01-30 17:13 darwin-amd64-race go@01a5a83c os/signal.TestTerminalSignal (log)
|
Seems this hasn't happened for quite some time (the test is not skipped on darwin). |
Since this technically isn't an issue with the current release, moving it into Backlog. |
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
subprogram failed: signal: killed
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: