[Bug 1591010] Re: two s390x fixes for docker

[Michael Hudson-Doyle]

I built all packages that build-depend on golang or golang-go in
https://launchpad.net/~mwhudson/+archive/ubuntu/go162-rebuilds/+packages
and 30 odd failed to build but all of the failures match those in
-release:

  cadvisor              -- fails on arm64, same in -release
  ciborium              -- ftbfs on same arches in -release
  consul-migrate        -- ftbfs with Go >= 1.6
  docker-registry       -- ftbfs on same arches in -release
  gb                    -- ftbfs on same arches in -release
  go-md2man             -- tries to build with gccgo on s390x
  golang-fsnotify       -- succeeded on retry
  golang-ginkgo         -- fails on arm64, same as -release (flaky tests)
  golang-git2go         -- ftbfs (amd64 only), in -release too
  golang-github-armon-go-metrics        -- ftbfs (amd64 only), in -release too
  golang-github-armon-gomdb     -- ftbfs (amd64 only), in -release too
  golang-github-aws-aws-sdk-go  -- ftbfs (amd64 only), in -release too
  golang-github-davecgh-go-spew -- ftbfs (amd64 only), in -release too
  golang-github-eknkc-amber     -- tries to build with gccgo on s390x
  golang-github-hashicorp-raft-mdb      -- ftbfs (amd64 only), in -release too
  golang-github-hashicorp-serf  -- ftbfs on arm64, succeeded on retry
  golang-github-jacobsa-ogletest        -- ftbfs with Go >= 1.5
  golang-github-miekg-mmark     -- tries to build with gccgo on arm64 & s390x
  golang-github-miekg-pkcs11    -- ftbfs (amd64 only), in -release too
  golang-github-mitchellh-reflectwalk   -- ftbfs (amd64 only), in -release too
  golang-github-samalba-dockerclient    -- ftbfs (amd64 only), in -release too
  golang-github-yosssi-ace      -- tries to build with gccgo on s390x
  golang-gocheck        -- ftbfs (amd64 only), in -release too
  golang-goyaml         -- ftbfs with Go >= 1.6 (maybe >= 1.5)
  golang-protobuf-extensions    -- ftbfs (amd64 only), in -relase too
  golang-rrd            -- ftbfs (amd64 only), in -release too
  gopacket              -- ftbfs (amd64 only), in -release too
  juju-mongo-tools3.2   -- ftbfs on arm64, flaky test retry hammer eventually worked
  knot-resolver         -- depwait on s390x, ppc64el, arm64, same as -release
  libguestfs            -- ftbfs everywhere, go related but same as -release
  ngrok                 -- depwait on s390x, same as -release
  notary                -- ftbfs on arm64, same as -release
  pay-service           -- ftbfs everywhere, same in as -release
  prometheus            -- ftbfs on arm64, actually better than situation in -release (!?)
  prometheus-node-exporter      -- ftbfs everywhere, bit wtf, but same as -release
  slt                   -- depwait on s390x, same as -release

I haven't verified that the fixes I want help with docker 1.11 on
ppc64el and s390x yet, will do that next.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to golang-1.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1591010

Title:
  two s390x fixes for docker

Status in golang-1.6 package in Ubuntu:
  Fix Released
Status in golang-1.6 source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  As explained in https://github.com/golang/go/issues/16021#issuecomment-225029684, the s390x port for Go contains two bugs that prevent docker from operating correctly.

  [Test Case]
  Build the docker, containerd and runc source packages from yakkety, install them "docker run s390x/ubuntu:16.04 echo hi" -- in the failing case this will hang on exit and containerd will be observed to use 100% cpu.
  Rebuild all packages that build-depend on golang in xenial.

  [Regression potential]
  Slight. I believe the Go point releases meet the guidelines described at https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-1.6/+bug/1591010/+subscriptions