-
Notifications
You must be signed in to change notification settings - Fork 18.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
integration-cli/TestSlowStdinClosing: increase timeout #36571
Conversation
I noticed this test failed on Windows: > 17:46:24 docker_cli_run_test.go:4361: > 17:46:24 c.Fatal("running container timed out") // cleanup in teardown I also noticed that in general tests are running slower on Windows, for example TestStartAttachSilent (which runs a container with `busybox echo test` and then starts it again) took 29.763s. This means a simple container start can easily take 15s, which explains the above failure. Double the timeout from 15s to 30s. Fixes: 4e262f6 ("Fix race on sending stdin close event") Signed-off-by: Kir Kolyshkin <[email protected]>
@tonistiigi PTAL |
experimental is failing on https://jenkins.dockerproject.org/job/Docker-PRs-experimental/39760/console (tracked through #36547)
powerpc failing on https://jenkins.dockerproject.org/job/Docker-PRs-powerpc/8967/console (may want to open an issue for that one as well, as I've seen it fail frequently)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SGTM
ping @johnstep PTAL
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Hm, another flaky test on experimental?
|
Looks like that one was flaky a couple of times in the past https://github.com/moby/moby/search?q=TestRunInteractiveWithRestartPolicy&type=Issues&utf8=✓ (also #27078) |
Merging this one, because the failure should not be related to this change |
I noticed this test failed on Windows:
I also noticed that in general tests are running slower on Windows, for example
TestStartAttachSilen
(which runs a container withbusybox echo test
and then starts it again) took 29.763s. This means a simple container start can easily take 15s, which explains the above failure.Double the timeout from 15s to 30s.
Fixes: 4e262f6 ("Fix race on sending stdin close event")