Vincent Demeester e857785df4 Fixing win2lin builds by adding a testRequires to DockerDaemonSuite ... The success of the win2lin CI before was really "by chance" on the DockerDaemonSuite : the DockerDaemonSuite was panicking when starting the daemon on the first non-skipped test.The suite panicked but as the error returned from `StartWithBusybox` was nil, the test kept going and was OK because the client had all the correct environment variables set up to discuss with the remote daemon. Then, as the suite panicked, no more test attached on the DockerDaemonSuite ran (that's why on win2lin, `DockerDaemonSuite` was only composed by 5 tests !). The really bad thing is, we didn't get any report of the panic on the suite (go-check hiding something somewhere). As DockerDaemonSuite needs to run test on the same host as it's running, this adds a `SameHostDaemon` requirement to the Suite. This changes also make sure `TestRestartContainerWithRestartPolicy` does left weirdies behind it. Signed-off-by: Vincent Demeester <vincent@sbr.pm>		2016-12-13 12:04:53 +01:00
..
daemon.go	Fixing win2lin builds by adding a testRequires to DockerDaemonSuite	2016-12-13 12:04:53 +01:00
daemon_swarm.go
daemon_unix.go
daemon_windows.go
npipe.go
npipe_windows.go