-
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: timeouts in TestNotifyContextNotifications on solaris-amd64-oraclerel #51054
Comments
It's interesting that the test is blocked on this subprocess in particular, because we explicitly plumb in a value for the |
Thanks for pinging me, @bcmills. |
One more this month:
2022-03-07T18:19:44-7dc6c5e/solaris-amd64-oraclerel I notice that we're not actually calling It occurs to me that the |
* I was able to reproduce this (building checked out @ commit 0261fa6) when running all.bash on a |
Since
|
Change https://go.dev/cl/398454 mentions this issue: |
Change https://go.dev/cl/398454 mentions this issue: |
If we run out of time on the first subtest, we don't want to start the second one with essentially no time remaining. (Moreover, there is no compelling reason not to run these tests in parallel, since they send signals to separate processes.) For #51054. Change-Id: I0424e08c3a9d2db986568d5a5c004859b52f7c51 Reviewed-on: https://go-review.googlesource.com/c/go/+/398454 Trust: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> Reviewed-by: Ian Lance Taylor <iant@golang.org> Reviewed-by: Henrique Vicente de Oliveira Pinto <henriquevicente@gmail.com> TryBot-Result: Gopher Robot <gobot@golang.org>
CL 398454 might fix this. I'll keep an eye on it. |
The thrilling conclusion, from https://build.golang.org/log/efc839b64c4b5ef269ecf21fa28685fbeb600e18:
The large |
Change https://go.dev/cl/403199 mentions this issue: |
The settleTime is arbitrary. Ideally we should refactor the test to avoid it (using subprocesses instead of sleeps to isolate tests from each others' delayed signals), but as a shorter-term workaround let's try scaling it back to match linux/ppc64 (the other builder that empirically requires a longer settleTime). For #51054. Updates #33174. Change-Id: I574fffaadd74c52c13d63974e87f20b6d3cf3c4b Reviewed-on: https://go-review.googlesource.com/c/go/+/403199 TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Bryan Mills <bcmills@google.com> Reviewed-by: Ian Lance Taylor <iant@google.com> Run-TryBot: Bryan Mills <bcmills@google.com>
Rolling forward to 1.20. Please comment if you disagree. Thanks. |
Found new dashboard test flakes for:
2023-01-09 17:35 solaris-amd64-oraclerel go@87105e5b os/signal.TestNotifyContextNotifications (log)
|
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.) |
Duplicate of #60152 |
greplogs --dashboard -md -l -e 'panic: test timed out .*\n(?:\ngoroutine \d+ .*:\n(.+\n)*)*^os/signal\.TestNotifyContextNotifications' --since=2021-01-01
2022-02-04T20:44:18-02224c8/solaris-amd64-oraclerel
2021-11-29T19:45:58-f598e29/solaris-amd64-oraclerel
2021-11-17T04:31:45-633d8c1/solaris-amd64-oraclerel
2021-10-31T15:36:50-243c5ae/solaris-amd64-oraclerel
2021-10-01T18:18:46-0d65c27/solaris-amd64-oraclerel
2021-10-01T17:18:34-dab16c1/solaris-amd64-oraclerel
2021-10-01T16:17:08-f19b2d5/solaris-amd64-oraclerel
2021-10-01T14:06:36-96d3ba8/solaris-amd64-oraclerel
2021-09-17T20:26:51-974b016/solaris-amd64-oraclerel
2021-08-16T23:32:14-8ff16c1/solaris-amd64-oraclerel
2021-08-16T14:26:45-b0fba64/solaris-amd64-oraclerel
2021-04-28T19:52:58-07e006d/solaris-amd64-oraclerel
2021-04-26T18:54:39-0d1280c/solaris-amd64-oraclerel
2021-04-23T21:42:57-c0e1301/solaris-amd64-oraclerel
2021-04-22T16:15:44-d3853fb/solaris-amd64-oraclerel
2021-04-16T16:36:57-2f0e5bf/solaris-amd64-oraclerel
2021-04-16T16:11:09-04e1176/solaris-amd64-oraclerel
2021-04-15T12:38:11-dba2eab/solaris-amd64-oraclerel
2021-04-06T04:48:09-a25c584/solaris-amd64-oraclerel
2021-03-18T14:09:57-db4adb1/solaris-amd64-oraclerel
This is the same test that was observed to be flaky in #41561 (CC @henvic, @ianlancetaylor, @cherrymui).
The text was updated successfully, but these errors were encountered: