[Bug 1567096] Comment bridged from LTC Bugzilla

2019-05-29 Thread bugproxy 
--- Comment From s...@us.ibm.com 2019-05-29 18:04 EDT---
This bug has not been touched in over two years, so I am rejecting it. If you 
feel this is in error, please reopen and justify.

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

Title:
  Docker doesn't work since Containerd integration

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1567096] Comment bridged from LTC Bugzilla

2016-12-16 Thread bugproxy 
--- Comment From clnpe...@us.ibm.com 2016-12-16 12:24 EDT---
Hi Canonical,

This somehow fell off of everyone's radar. Can we get another shot at
getting it in? We'll have someone look at it ASAP.

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

Title:
  Docker doesn't work since Containerd integration

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1567096] Comment bridged from LTC Bugzilla

2016-05-04 Thread bugproxy 
--- Comment From bo...@us.ibm.com 2016-05-04 10:42 EDT---
I've tried several Ubuntu distros and it passes everywhere I've tried, even on 
15.10.

Just to be sure:  fsnotify and everything that depends on go has been
rebuilt with the new go1.6.2?

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

Title:
  Docker doesn't work since Containerd integration

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1567096] Comment bridged from LTC Bugzilla

2016-05-03 Thread bugproxy 
--- Comment From clnpe...@us.ibm.com 2016-05-03 11:47 EDT---
(In reply to comment #35)
> That's not really the sort of test I wanted; I want something I can
> show to the SRU team that will motivate including Go 1.6.2 in Ubuntu
> 16.04. This bug was originally about docker not working, can you
> provide reproduction steps for that?
>
> As far as I can tell, everything in yakkety should be new enough to
> run the golang-fsnotify tests, but they still fail on ppc64el for me
> (TestInotifyRemoveTwice fails with "no error on removing invalid file"
> and TestInotifyInnerMapLength hangs until the 10 minute timeout kills
> it).

If you have an installation of Ubuntu 16.04, you can install go &
docker, build docker from upstream source, copy all the docker binaries
(dockerd, docker, docker-containerd, docker-containerd-ctr, docker-
containerd-shim, and docker-runc) into  /usr/bin/ , and then run a
container (docker run -it ppc64le/ubuntu echo hi) and it will hang and
fail to exit.


Or, you can build docker in a container and then run  (the way the CI tests 
work):

0. Install docker
1. checkout and patch docker master:

diff --git a/Dockerfile.ppc64le b/Dockerfile.ppc64le
index 208c3a5..3fa36a0 100644
--- a/Dockerfile.ppc64le
+++ b/Dockerfile.ppc64le
@@ -73,9 +73,9 @@ RUN cd /usr/local/lvm2 \
## BUILD GOLANG 1.6
# NOTE: ppc64le has compatibility issues with older versions of go, so make 
sure the version >= 1.6
-ENV GO_VERSION 1.6.2
+ENV GO_VERSION 1.6.1
ENV GO_DOWNLOAD_URL https://golang.org/dl/go${GO_VERSION}.src.tar.gz
-ENV GO_DOWNLOAD_SHA256 
787b0b750d037016a30c6ed05a8a70a91b2e9db4bd9b1a2453aa502a63f1bccc
+ENV GO_DOWNLOAD_SHA256 
1d4b53cdee51b2298afcf50926a7fa44b286f0bf24ff8323ce690a66daa7193f
ENV GOROOT_BOOTSTRAP /usr/local
RUN curl -fsSL "$GO_DOWNLOAD_URL" -o golang.tar.gz

2. build the docker dev container:
$docker build -t docker:1.6.1 -f Dockerfile.ppc64le .

3. Run the docker dev container
$docker run -it --privileged docker:1.6.1 /bin/bash

4. From the container, build the docker binary
root@05f8c2e2a546:/go/src/github.com/docker/docker# ./hack/make.sh binary

5. Run a docker container:
root@05f8c2e2a546:/go/src/github.com/docker/docker# cd 
bundles/latest/binary-daemon
root@05f8c2e2a546:/go/src/github.com/docker/docker# ./docker &
root@05f8c2e2a546:/go/src/github.com/docker/docker# cd ../docker-client
root@05f8c2e2a546:/go/src/github.com/docker/docker# ./ ./docker run -it 
ppc64le/ubuntu echo hi
hi
[infinite cursor]

You can see that the container runs, but never exits.

==

Is that helpful?

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

Title:
  Docker doesn't work since Containerd integration

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1567096] Comment bridged from LTC Bugzilla

2016-05-02 Thread Michael Hudson-Doyle 
Hm, that's not what I see, but I am running in a yakkey chroot on a
wily system -- could there be a dependence on kernel version here?

On 3 May 2016 at 05:50, bugproxy  wrote:
> --- Comment From bo...@us.ibm.com 2016-05-02 13:45 EDT---
> Here is a bit more detail on my earlier comment:
>
> You need fsnotify commit 836bfd to see the problem with go1.6.1.  If the
> fsnotify package is built with this commit using go1.6.1 and the test
> built with go1.6.1, then there will be several failures and a hang
> TestInotifyInnerMapLength:
>
> ./fsnotify.test -test.v
> === RUN   TestPollerWithBadFd
> --- PASS: TestPollerWithBadFd (0.00s)
> === RUN   TestPollerWithData
> --- FAIL: TestPollerWithData (0.00s)
> inotify_poller_test.go:85: expected poller to return true
> === RUN   TestPollerWithWakeup
> --- PASS: TestPollerWithWakeup (0.00s)
> === RUN   TestPollerWithClose
> --- FAIL: TestPollerWithClose (0.00s)
> inotify_poller_test.go:119: expected poller to return true
> === RUN   TestPollerWithWakeupAndData
> --- FAIL: TestPollerWithWakeupAndData (0.00s)
> inotify_poller_test.go:140: expected poller to return true
> === RUN   TestPollerConcurrent
> --- FAIL: TestPollerConcurrent (0.05s)
> inotify_poller_test.go:197: expected true
> === RUN   TestInotifyCloseRightAway
> --- PASS: TestInotifyCloseRightAway (0.05s)
> === RUN   TestInotifyCloseSlightlyLater
> --- PASS: TestInotifyCloseSlightlyLater (0.10s)
> === RUN   TestInotifyCloseSlightlyLaterWithWatch
> --- PASS: TestInotifyCloseSlightlyLaterWithWatch (0.10s)
> === RUN   TestInotifyCloseAfterRead
> --- PASS: TestInotifyCloseAfterRead (0.10s)
> === RUN   TestInotifyCloseCreate
> --- FAIL: TestInotifyCloseCreate (0.05s)
> inotify_test.go:136: Took too long to wait for event
> === RUN   TestInotifyStress
> --- FAIL: TestInotifyStress (5.00s)
> inotify_test.go:238: Expected at least 50 creates, got 0
> === RUN   TestInotifyRemoveTwice
> --- PASS: TestInotifyRemoveTwice (0.00s)
> === RUN   TestInotifyInnerMapLength
> 
>
> However, if you switch to using go1.6.2, rebuild the fsnotify package and 
> testcase from this same fsnotify commit id and run the test, it passes:
> boger@ampere:~/fsnotify/src/github.com/fsnotify/fsnotify$ go version
> go version go1.6.2 linux/ppc64le
> boger@ampere:~/fsnotify/src/github.com/fsnotify/fsnotify$ go test -c
> boger@ampere:~/fsnotify/src/github.com/fsnotify/fsnotify$ ./fsnotify.test
> PASS
>
> If you change to use the latest commit for fsnotify (containing the
> switch to use x/sys/unix for the header files), rebuild the fsnotify
> package and the test, that seems to work for both go1.6.1 and go1.6.2,
> since it is no longer using the header file from the golang directories
> but from the golang/x directories.
>
> --
> You received this bug notification because you are subscribed to
> golang-1.6 in Ubuntu.
> https://bugs.launchpad.net/bugs/1567096
>
> Title:
>   Docker doesn't work since Containerd integration
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/golang-1.6/+bug/1567096/+subscriptions

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

Title:
  Docker doesn't work since Containerd integration

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1567096] Comment bridged from LTC Bugzilla

2016-05-02 Thread bugproxy 
--- Comment From bo...@us.ibm.com 2016-05-02 13:45 EDT---
Here is a bit more detail on my earlier comment:

You need fsnotify commit 836bfd to see the problem with go1.6.1.  If the
fsnotify package is built with this commit using go1.6.1 and the test
built with go1.6.1, then there will be several failures and a hang
TestInotifyInnerMapLength:

./fsnotify.test -test.v
=== RUN   TestPollerWithBadFd
--- PASS: TestPollerWithBadFd (0.00s)
=== RUN   TestPollerWithData
--- FAIL: TestPollerWithData (0.00s)
inotify_poller_test.go:85: expected poller to return true
=== RUN   TestPollerWithWakeup
--- PASS: TestPollerWithWakeup (0.00s)
=== RUN   TestPollerWithClose
--- FAIL: TestPollerWithClose (0.00s)
inotify_poller_test.go:119: expected poller to return true
=== RUN   TestPollerWithWakeupAndData
--- FAIL: TestPollerWithWakeupAndData (0.00s)
inotify_poller_test.go:140: expected poller to return true
=== RUN   TestPollerConcurrent
--- FAIL: TestPollerConcurrent (0.05s)
inotify_poller_test.go:197: expected true
=== RUN   TestInotifyCloseRightAway
--- PASS: TestInotifyCloseRightAway (0.05s)
=== RUN   TestInotifyCloseSlightlyLater
--- PASS: TestInotifyCloseSlightlyLater (0.10s)
=== RUN   TestInotifyCloseSlightlyLaterWithWatch
--- PASS: TestInotifyCloseSlightlyLaterWithWatch (0.10s)
=== RUN   TestInotifyCloseAfterRead
--- PASS: TestInotifyCloseAfterRead (0.10s)
=== RUN   TestInotifyCloseCreate
--- FAIL: TestInotifyCloseCreate (0.05s)
inotify_test.go:136: Took too long to wait for event
=== RUN   TestInotifyStress
--- FAIL: TestInotifyStress (5.00s)
inotify_test.go:238: Expected at least 50 creates, got 0
=== RUN   TestInotifyRemoveTwice
--- PASS: TestInotifyRemoveTwice (0.00s)
=== RUN   TestInotifyInnerMapLength


However, if you switch to using go1.6.2, rebuild the fsnotify package and 
testcase from this same fsnotify commit id and run the test, it passes:
boger@ampere:~/fsnotify/src/github.com/fsnotify/fsnotify$ go version
go version go1.6.2 linux/ppc64le
boger@ampere:~/fsnotify/src/github.com/fsnotify/fsnotify$ go test -c
boger@ampere:~/fsnotify/src/github.com/fsnotify/fsnotify$ ./fsnotify.test
PASS

If you change to use the latest commit for fsnotify (containing the
switch to use x/sys/unix for the header files), rebuild the fsnotify
package and the test, that seems to work for both go1.6.1 and go1.6.2,
since it is no longer using the header file from the golang directories
but from the golang/x directories.

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

Title:
  Docker doesn't work since Containerd integration

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1567096] Comment bridged from LTC Bugzilla

2016-05-01 Thread Michael Hudson-Doyle 
That's not really the sort of test I wanted; I want something I can
show to the SRU team that will motivate including Go 1.6.2 in Ubuntu
16.04. This bug was originally about docker not working, can you
provide reproduction steps for that?

As far as I can tell, everything in yakkety should be new enough to
run the golang-fsnotify tests, but they still fail on ppc64el for me
(TestInotifyRemoveTwice fails with "no error on removing invalid file"
and TestInotifyInnerMapLength hangs until the 10 minute timeout kills
it).

Cheers,
mwh

On 30 April 2016 at 02:19, bugproxy  wrote:
> --- Comment From bo...@us.ibm.com 2016-04-29 10:15 EDT---
> Hi, here's a very simple testcase to verify that the EpollEvent structure is 
> correct in the src/syscall directory:
>
> package main
>
> import "fmt"
> import "syscall"
> import "reflect"
>
> func main() {
> var ee syscall.EpollEvent
> fmt.Printf("EpollEvent fields (should be 4): %d\n", 
> reflect.ValueOf(ee).NumField())
> }
>
> As far as the fsnotify tests working, sometime after I submitted my fix
> there have been changes in fsnotify to use golang.org/x/sys/unix instead
> of the stdlib syscall package, so I'm not sure if that is affecting your
> results or not.  A fix for EpollEvent for that directory has been
> submitted.
>
> --
> You received this bug notification because you are subscribed to
> golang-1.6 in Ubuntu.
> https://bugs.launchpad.net/bugs/1567096
>
> Title:
>   Docker doesn't work since Containerd integration
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/golang-1.6/+bug/1567096/+subscriptions

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

Title:
  Docker doesn't work since Containerd integration

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1567096] Comment bridged from LTC Bugzilla

2016-04-29 Thread bugproxy 
--- Comment From bo...@us.ibm.com 2016-04-29 10:15 EDT---
Hi, here's a very simple testcase to verify that the EpollEvent structure is 
correct in the src/syscall directory:

package main

import "fmt"
import "syscall"
import "reflect"

func main() {
var ee syscall.EpollEvent
fmt.Printf("EpollEvent fields (should be 4): %d\n", 
reflect.ValueOf(ee).NumField())
}

As far as the fsnotify tests working, sometime after I submitted my fix
there have been changes in fsnotify to use golang.org/x/sys/unix instead
of the stdlib syscall package, so I'm not sure if that is affecting your
results or not.  A fix for EpollEvent for that directory has been
submitted.

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

Title:
  Docker doesn't work since Containerd integration

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1567096] Comment bridged from LTC Bugzilla

2016-04-28 Thread Michael Hudson-Doyle 
Yes, I need to go through the SRU process to get Go 1.6.2 into Xenial
(and Trusty). Hopefully I can get to that today.

On 29 April 2016 at 07:42, bugproxy  wrote:
> --- Comment From bren...@br.ibm.com 2016-04-28 15:35 EDT---
> I understood that this comment means that Canonical has golang version 1.6.2 
> in 16.10:
> $ go version
> go version go1.6.2 linux/ppc64le
>
> On the other side, 16.04 still has 1.6.1
> $ go version
> go version go1.6.1 linux/ppc64le
>
> --
> You received this bug notification because you are subscribed to
> golang-1.6 in Ubuntu.
> https://bugs.launchpad.net/bugs/1567096
>
> Title:
>   Docker doesn't work since Containerd integration
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/golang-1.6/+bug/1567096/+subscriptions

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

Title:
  Docker doesn't work since Containerd integration

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1567096] Comment bridged from LTC Bugzilla

2016-04-28 Thread bugproxy 
--- Comment From bren...@br.ibm.com 2016-04-28 15:35 EDT---
I understood that this comment means that Canonical has golang version 1.6.2 in 
16.10:
$ go version
go version go1.6.2 linux/ppc64le

On the other side, 16.04 still has 1.6.1
$ go version
go version go1.6.1 linux/ppc64le

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

Title:
  Docker doesn't work since Containerd integration

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1567096] Comment bridged from LTC Bugzilla

2016-04-28 Thread bugproxy 
--- Comment From clnpe...@us.ibm.com 2016-04-28 15:15 EDT---
Hi Canonical,

I don't know the context of the last comment, and also see that the
epoll fix hasn't made it in yet, so want to sync up and make sure 1.6.2
from upstream is what you're pulling in and patching.

Thanks!

- Christy

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

Title:
  Docker doesn't work since Containerd integration

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1567096] Comment bridged from LTC Bugzilla

2016-04-14 Thread bugproxy 
--- Comment From bo...@us.ibm.com 2016-04-14 09:01 EDT---
This bug affects anything that uses one of the epoll* syscalls that returns 
information in the EpollEvent structure that was incorrectly defined for 
ppc64/ppc64le in golang.  Without this fix those syscalls will return incorrect 
event information, and many of the tests in fsnotify fail.  It wasn't found 
until upstream Docker hit it, but I think it could affect more than just Docker.

The fix consists only of correctly defining the data structure used by
these syscalls and only for ppc64le/ppc64 so I don't think it is very
risky.

On the other hand, I just requested it get into go 1.6.2, I think that
should go in, but I don't know what kind of time line we are talking
about for Ubuntu 16.04 golang to move to that.

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

Title:
  Docker doesn't work since Containerd integration

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs