4ee82987ec
I saw a failure of TestDockerCmdWithTimeout. This test starts a command that produces output after 10 ms, but uses a 5 ms timeout, so normally the command will be killed before the output. The time intervals are so small that the timeout may not reliably trigger before the output, which can cause the test to fail. This commit changes the test to only fail if the process is still alive after 10 seconds. This means the test will confirm that the timeouts are happening, but not attempt to gauge that the timeouts are happening within milliseconds of when they are expected (which can't be done reliably). Signed-off-by: Aaron Lehmann <aaron.lehmann@docker.com> Upstream-commit: 13d768b8ee05d3158c62d761e4ebe657cd7a8c25 Component: engine