Comment 5 for bug 1576419

Revision history for this message
Martin Pitt (pitti) wrote :

I ran it again locally this morning, and the hang from last night didn't occur. Now the tests actually start to run. At some point an awful lot of them fail with something like

FAIL: docker_cli_build_unix_test.go:85: DockerSuite.TestBuildAddChangeOwnership

docker_cli_build_unix_test.go:120:
    c.Fatalf("build failed to complete for TestBuildAddChangeOwnership: %v", err)
... Error: build failed to complete for TestBuildAddChangeOwnership: failed to build the image: Sending build context to Docker daemon 2.56 kB
Error response from daemon: Untar error on re-exec cmd: fork/exec /proc/self/exe: no such file or directory

which is exactly the same "test breaks /proc" effect that I noticed before. Tianon, do you get these as well? 894 failures certainly leave enough room for those :-)

But it also didn't kill sshd here.