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: freebsd/386 flaky TestCgoSignalDeadlock #18598
Comments
Another one:
|
Let's keep this bug about TestCgoSignalDeadlock. I filed #19381 for the TestStackGrowth bug. |
/cc @ianlancetaylor |
I haven't yet been able to recreate this using gomote with freebsd-386-110. When I run the test using gomote, it takes consistently less than 0.2s. Looking at the times from the failures listed above, I see these times: 279.16 So it looks like at at least on ARM, something is making the test take much much longer than expected. There is no FreeBSD ARM gomote. Since the test has a timeout, if something slows it down a lot it is expected to fail. Since the test calls |
CL https://golang.org/cl/46723 mentions this issue. |
Updates #18598 Change-Id: I13c60124714cf9d1537efa0a7dd1e6a0fed9ae5b Reviewed-on: https://go-review.googlesource.com/46723 Run-TryBot: Ian Lance Taylor <iant@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
Failures with additional debugging: 2017-06-27T18:53:08-5dafa91/freebsd-arm-paulzhol |
Thanks. It looks like while the test is running the system is getting steadily more and more overloaded, and the test blows through the timeout. I note that the test calls Something I didn't notice before is that every failure on ARM is in the It would be nice if we could figure out a way to print what other tests are running when this one fails. |
I recently dropped
Note that |
CL https://golang.org/cl/48233 mentions this issue. |
It seems that when too much other code is running on the system, the testprogcgo code can overrun its timeouts. Updates #18598. Not marking the issue as fixed until it doesn't recur for some time. Change-Id: Ieaf106b41986fdda76b1d027bb9d5e3fb805cc3b Reviewed-on: https://go-review.googlesource.com/48233 Run-TryBot: Ian Lance Taylor <iant@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>
I'm running the freebsd-arm-paulzhol builder with the following parameters: It's an ARM Cortex-A7 (Allwinner A20) and has only 1G RAM so it's using a swap partition from a magnetic disk. Could that be what is making it extra slow for the tests? I can provide ssh access if it would help (or I can help debug). |
This has not failed since June 29, when before then it was failing every few days. I think that removing |
While preparing go1.8rc1:
/cc @ianlancetaylor
The text was updated successfully, but these errors were encountered: