-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
cmd/compile: regular panic on Plan 9 #14650
Comments
CC @4ad |
CL https://golang.org/cl/21411 mentions this issue. |
On the Plan 9 builder, we are experiencing regular failures in cmd/compile when building go_boostrap. We suspect the failures to be related to a bug in the Go 1.4 runtime. This is affecting the cmd/compile program, since it has been built with Go 1.4 and linked with the Go 1.4 runtime. Updates golang/go#14650 Change-Id: I78729c8660314be381d7b668810c6f64214f2358 Reviewed-on: https://go-review.googlesource.com/21411 Reviewed-by: Richard Miller <millerresearch@gmail.com> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Okay, I've updated the plan9-386 GOROOT_BOOTSTRAP tarball to Go tip (at 59fc42b), trimmed down for size (see #9797 (comment)), and rebuilt the plan9-386 buildlet at the same revision and deployed, restarted farmer.golang.org, and reset the failed plan9 builds on the dashboard, so they're trying again now. |
This appears to be fixed. We have an entire column of "ok" now. I'm going to optimistically close this bug. |
Since early January we started to experience occasional cmd/compile failures reported by the Plan 9 (386) trybots on the dev.ssa branch. When the dev.ssa branch was merged to master on March 1, the failures started to become much more frequent, because the master branch is more active.
The failures happen when building go_bootstrap. They look like:
or
or
I looked at all the Plan 9 trybot failures for the past few months. Here are the failures that seem related to the issue:
2016-01-07 https://storage.googleapis.com/go-build-log/08d47646/plan9-386_a0c8a6de.log
2016-02-07 https://storage.googleapis.com/go-build-log/786cb6aa/plan9-386_3caaf30b.log
2016-02-08 https://storage.googleapis.com/go-build-log/6284fd7d/plan9-386_0eb811c9.log
2016-02-08 https://storage.googleapis.com/go-build-log/c3e8473c/plan9-386_a81fe2b3.log
2016-02-08 https://storage.googleapis.com/go-build-log/74693682/plan9-386_af2ede70.log
2016-02-10 https://storage.googleapis.com/go-build-log/fd458ba4/plan9-386_32443634.log
2016-02-10 https://storage.googleapis.com/go-build-log/c05edc82/plan9-386_d9e2152a.log
2016-03-02 https://storage.googleapis.com/go-build-log/bb017f22/plan9-386_675f6af8.log
2016-03-02 https://storage.googleapis.com/go-build-log/7a15fb26/plan9-386_8300a8d5.log
2016-03-03 https://storage.googleapis.com/go-build-log/45983827/plan9-386_964f732b.log
2016-03-03 https://storage.googleapis.com/go-build-log/8ce703f2/plan9-386_f1266bd9.log
2016-03-03 https://storage.googleapis.com/go-build-log/99f4402a/plan9-386_359912ab.log
2016-03-03 https://storage.googleapis.com/go-build-log/8ce703f2/plan9-386_f1266bd9.log
2016-03-03 https://storage.googleapis.com/go-build-log/b1f365e1/plan9-386_bb0c78ee.log
2016-03-03 https://storage.googleapis.com/go-build-log/628190d2/plan9-386_dd54d34f.log
2016-03-03 https://storage.googleapis.com/go-build-log/2a89b4fa/plan9-386_b11a651b.log
2016-03-03 https://storage.googleapis.com/go-build-log/e360bef5/plan9-386_dd273260.log
2016-03-04 https://storage.googleapis.com/go-build-log/39cfd5ed/plan9-386_ac6a3ddb.log
2016-03-04 https://storage.googleapis.com/go-build-log/d02312c3/plan9-386_416636ef.log
2016-03-04 https://storage.googleapis.com/go-build-log/4af86c05/plan9-386_1b187278.log
2016-03-04 https://storage.googleapis.com/go-build-log/1023603d/plan9-386_f379247a.log
The error appeared the first time on 2016-01-07. Then, it appeared on 2016-02-07, 2016-02-08 and 2016-02-10. All these failures are related to changes on the dev.ssa branch.
Then, the dev.ssa branch was merged to master on 2016-03-01 and the issue started to appear on master as well.
Here are the issues on the build dashboard for the dev.ssa branch:
2016-01-13 http://build.golang.org/log/16064baa23820f462d88b62091555e3f3206a2c2
2016-02-07 http://build.golang.org/log/5f7bd41b60d44c44553b8a6c5fa09a3c11e1919b
2016-02-07 http://build.golang.org/log/f18355544e9b52cac265ab46181915bced101a03
2016-02-08 http://build.golang.org/log/752ad760aa459d182d494fd78b2ee027ad9d37a4
2016-02-08 http://build.golang.org/log/1cc97297b15cc3537bfe0b355412af7c5d655e1d
2016-02-09 http://build.golang.org/log/ff9ad04c40f3618ea25c752879182cab5d06d9d9
2016-02-09 http://build.golang.org/log/4cfeffddb1ce4b2ef3beab43a7020a5bade1b27e
The very first failure (2016-01-07) was noticed by the Plan 9 trybot in CL 18390, which was submitted on 2016-01-13. Then, the first failure from the dashboard (2016-01-13) appeared when the [CL 18267 (https://golang.org/cl/18267) was submitted, just after CL 18390.
I tried to reproduce the issue by running make.rc dozens of times on various machines, including the same image running the Plan 9 builder on GCE. So far, I haven't been able to reproduce the issue.
The text was updated successfully, but these errors were encountered: