Landings were blocked today by a bug [1381671] where a recently landed test file was failing to build on the ppc64 slave.
As far as I can see, there's nothing obviously broken, and the package follows the same basic layout as its api/ siblings. So, for now, I've skipped building this file to unblock trunk. The linker failure itself looks similar to an issue [1289067] Dave fixed upstream earlier in the year. However the fixed gccgo package is indeed being used on the slave, so this requires extra investigation: # testmain /tmp/go-build988982231/github.com/juju/juju/api/reboot/_test/github.com/juju/juju/api/libreboot.a(reboot.o): In function `github_com_juju_juju_api_reboot.ClearReboot.pN37_github_com_juju_juju_api_reboot.State': /home/ubuntu/juju-core_1.21-alpha2/src/github.com/juju/juju/api/reboot/reboot.go:67: multiple definition of `github_com_juju_juju_api_reboot.ClearReboot.pN37_github_com_juju_juju_api_reboot.State' /tmp/go-build988982231/github.com/juju/juju/api/libreboot.a(reboot.o):/home/ubuntu/juju-core_1.21-alpha2/src/github.com/juju/juju/api/reboot/reboot.go:67: first defined here ... I cannot reproduce the error with gccgo on amd64 or armhf, only on the pcc64 machine. Any ideas? Martin [1381671] "reboot tests fail to build on gccgo" <https://bugs.launchpad.net/juju-core/+bug/1381671> "arm64 multiple definition of `launchpad.net_juju_core_cmd._.0" <https://bugs.launchpad.net/juju-core/+bug/1289067> -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
