-
Notifications
You must be signed in to change notification settings - Fork 18k
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: apparent test deadlock on ppc64le #32327
Comments
We have seen this failure intermittently, but only on power8 I believe, and most often on ppc64le. Can we verify what distro and kernel is being used for the builders? If they are old, it might be worth upgrading to see if that makes any difference. I don't think we've seen this on the power9 builder, which must have a newer kernel. Or maybe the timeout is just too short for this test on ppc64x? |
Another occurrence on I don't know what distro and kernel is in use. Maybe @bradfitz, @dmitshur, or @toothrot can find out? |
|
You can do a gomote create and run "uname -a", etc to see what it's running. |
The runtime timeout has now happened on power9 so my distro theory is shot. I will see if I can reproduce the timeout on one of our systems. One interesting note is that in many cases, these timeouts happen when two testruns are started within a few seconds of each other, and it is always the first of the two that timeout. Is there anything that the second run could be getting exclusive access of that the first one then has to wait on before continuing? |
Two timeouts this morning on I don't see an obvious culprit for a contending run in either of those cases, but I'm also not very familiar with the builder logs. |
This one in |
Recently we seem to have had a lot of hangs like this where one of the goroutines is in an IO wait while trying to do a read. Just wondering if some kind of file system issue might cause that? |
Change https://golang.org/cl/197237 mentions this issue: |
These two seem to be stuck in a
Maybe there is a bug in the unparking code? |
This deadlock also seems it's fixed. |
Thanks. |
Seen in https://build.golang.org/log/01b3ad998d294eccfaed1be94a674a8ed36431d7:
CC @mknyszek @aclements
The text was updated successfully, but these errors were encountered: