[Bug 1567096] Comment bridged from LTC Bugzilla
Michael Hudson-Doyle
michael.hudson+lp at canonical.com
Sun May 1 22:52:01 UTC 2016
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 <bugproxy at us.ibm.com> wrote:
> ------- Comment From boger at 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
Foundations Bugs, which is subscribed to golang-1.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1567096
Title:
Docker doesn't work since Containerd integration
Status in golang-1.6 package in Ubuntu:
Fix Released
Bug description:
-- Problem Description --
Docker build hangs indefinitely when run using a 1.11.0 binary built after containerd integration, and go 1.6 on ppc64le. Doing the same thing works with gccgo.
Looking at the differences in docker logs shows that the containerd
event "exit", never happens when using a binary built with gc.
fsnotify, the file system handler for go, doesn't seem to receive the
correct event when a file is either written to, or closed, which I
believe is whats causing this issue.
Link to fsnotify issue which shows some failing tests :
https://github.com/fsnotify/fsnotify/issues/130
I have a patch that fixes the errors when I run fsnotify. I am
preparing it for submission now and should be out there as a golang CL
this morning.
Do you want the patch so you can rebuild golang with it? If fsnotify
is a separate package then you will have to rebuild it with the new
golang.
Here's the CL link if you want to get the patch for ppc64le: https://go-review.googlesource.com/#/c/21582/
Go to the upper right where it says download and I think if you select patch file it will give you the patch.
We'll update with more info after testing the patch Lynn submitted,
but we wanted to let Canonical know about this issue in the meantime
since 1.11 is about to GA upstream.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-1.6/+bug/1567096/+subscriptions
More information about the foundations-bugs
mailing list