cmd/release: linux-arm release build fails

[davecheney]

After applying CL 17663 the release build fails to complete the tests.

--- FAIL: TestGdbPython (4.19s)
        runtime-gdb_test.go:42: gdb version 7.7
        runtime-gdb_test.go:129: failed to load Go runtime support: warning: File "/usr/local/go/src/runtime/runtime-gdb.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load:/workdir/go/src/
runtime".
FAIL
FAIL    runtime 143.480s

I believe this is because the release build runs with GOROOT_FINAL set, altering the path to runtime-gdb.py which is embedded into the binary.

Blocks #13066

/cc @bradfitz @broady

[rsc]

Where did auto-load safe-path come from?

[davecheney]

It's coming from the Ubuntu 14.04 flavour of Linux our scaleway arm boxes
come with. I suspect the GCE Linux builders don't come with gdb installed.

On Thu, 17 Dec 2015, 18:14 Russ Cox [email protected] wrote:

Where did auto-load safe-path come from?

—
Reply to this email directly or view it on GitHub
#13577 (comment).

[mwhudson]

Certainly my not very sophisticated approach to Debian package builds
failing on this test is to run them in a chroot that does not have gdb
installed.

On 17 December 2015 at 20:40, Dave Cheney [email protected] wrote:

It's coming from the Ubuntu 14.04 flavour of Linux our scaleway arm boxes
come with. I suspect the GCE Linux builders don't come with gdb installed.

On Thu, 17 Dec 2015, 18:14 Russ Cox [email protected] wrote:

Where did auto-load safe-path come from?

—
Reply to this email directly or view it on GitHub
#13577 (comment).

—
Reply to this email directly or view it on GitHub
#13577 (comment).

[rsc]

https://go-review.googlesource.com/17970 should take care of disabling the test in this case.

[davecheney]

I went even more lowbrow. I used gomote to rm /usr/bin/gdb before the builder got to that phase of ./all.bash

On 17 Dec 2015, at 21:04, Michael Hudson-Doyle [email protected] wrote:

Certainly my not very sophisticated approach to Debian package builds
failing on this test is to run them in a chroot that does not have gdb
installed.

On 17 December 2015 at 20:40, Dave Cheney [email protected] wrote:

It's coming from the Ubuntu 14.04 flavour of Linux our scaleway arm boxes
come with. I suspect the GCE Linux builders don't come with gdb installed.

On Thu, 17 Dec 2015, 18:14 Russ Cox [email protected] wrote:

Where did auto-load safe-path come from?

—
Reply to this email directly or view it on GitHub
#13577 (comment).

—
Reply to this email directly or view it on GitHub
#13577 (comment).

—
Reply to this email directly or view it on GitHub.

[bradfitz]

Um, the scaleway builders don't run in Docker containers. They run under systemd with a freshly tmpfs as their build filesystem $WORKDIR, but /usr/bin/gdb was the host's gdb you deleted. :-)

[davecheney]

Oh crap. Sorry. I did not know that.

On 18 Dec 2015, at 10:10, Brad Fitzpatrick [email protected] wrote:

Um, the scaleway builders don't run in Docker containers. They run under systemd with a freshly tmpfs as their build filesystem $WORKDIR, but /usr/bin/gdb was the host's gdb you deleted. :-)

—
Reply to this email directly or view it on GitHub.

[rsc]

Did you try it with my CL before deleting gdb? Just curious whether it helped at all.

[davecheney]

I did that process last week when I was trailing the change on the Go 1.5.2
release tag

On Fri, 18 Dec 2015, 10:34 Russ Cox [email protected] wrote:

Did you try it with my CL before deleting gdb? Just curious whether it
helped at all.

—
Reply to this email directly or view it on GitHub
#13577 (comment).