-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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: TestGdbLoadRuntimeSupport fails on non intel platforms #9820
Comments
This is failing because in environments where From a working tree that one of my builders was building at the time:
If I had to guess, the linux builders which are passing have a copy of Go 1.4 in |
Aha, that's because we set GOROOT_FINAL in builders.
|
No need to guess. Our builder environments are described with scripts to hermetically reproduce them. Just look in x/builder/env. |
Go 1.4's runtime-gdb.py is broken, so the reason why x86 builders are
passing that test
is definitely not because they are using Go 1.4 version of runtime-gdb.py.
Something else is happening that makes the runtime path correct despite the
fact that
we set GOROOT_FINAL.
(Or it is possible that only the old style builders set GOROOT_FINAL, and
new style
builders are not?)
|
But why do we set it to /usr/local/go during a build that we know will be
|
This is failing for me on OS X as well: $ go test runtime -v -run=TestGdbLoadRuntimeSupport
=== RUN TestGdbLoadRuntimeSupport
--- FAIL: TestGdbLoadRuntimeSupport (0.25s)
runtime-gdb_test.go:59:
FAIL
exit status 1
FAIL runtime 0.250s |
I think we're not going to get to this for Go 1.5. |
runtime.TestGdbLoadRuntimeSupport
does not pass on linux/arm or linux/ppc64le. In both cases the error is the sameThe text was updated successfully, but these errors were encountered: