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
I ran it locally with a 4GB VM and managed to get through all the tests
without sshd dying. :(
(obviously we've got some failures that we'll need to figure out, but
probably only worth figuring out the failures if we can figure out why
sshd is getting killed D: )
OOPS: 192 passed, 120 skipp
FTR, this still happens when running the tests in an m1.large instance
(8 GB RAM). I was trying to reproduce locally with
adt-run --apt-pocket=proposed docker.io --- qemu adt-yakkety-
amd64-cloud.img
and have ssh open to the VM while it runs (port 10022 on localhost,
user:pass ubuntu:ubuntu)
This sounds suspiciously like OOM killing sshd, not Docker's tests
directly -- I know the integration tests used to require anywhere from
1 to 4 GB of RAM, and I imagine that's probably still the case. :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
The test runs fine up to this point:
PASS: docker_api_containers_test.go:902: DockerSuite.TestContainerApiKill
0.420s
PASS: docker_api_containers_test.go:441: DockerSuite.TestContainerApiPause
0.491s
PASS: docker_api_containers_test.go:800:
DockerSuite.TestContainerApiPostCreateNull
