Then it apparently kills the remote sshd end of the ssh session, which makes the controller's ssh process exit with 255 (255 is ssh's code for an interrupted connection ).
I checked five different worker logs and it's always the same place where this happens. So whatever the next test after TestContainerApiRestart is is likely the one that causes this.
The test runs fine up to this point:
PASS: docker_ api_containers_ test.go: 902: DockerSuite. TestContainerAp iKill 0.420s api_containers_ test.go: 441: DockerSuite. TestContainerAp iPause 0.491s api_containers_ test.go: 800: DockerSuite. TestContainerAp iPostCreateNull 0.291s api_containers_ test.go: 887: DockerSuite. TestContainerAp iRename 0.421s api_containers_ test.go: 916: DockerSuite. TestContainerAp iRestart 1.555s
PASS: docker_
PASS: docker_
PASS: docker_
PASS: docker_
Connection to 10.42.43.169 closed by remote host.^M
adt-run [17:08:10]: ERROR: testbed failure: testbed auxverb failed with exit code 255
Then it apparently kills the remote sshd end of the ssh session, which makes the controller's ssh process exit with 255 (255 is ssh's code for an interrupted connection ).
I checked five different worker logs and it's always the same place where this happens. So whatever the next test after TestContainerAp iRestart is is likely the one that causes this.