-
Notifications
You must be signed in to change notification settings - Fork 18.6k
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
Flaky test: TestStartReturnCorrectExitCode #38521
Comments
Also on:
|
I just saw this flaky test fail on PR #39638. From the console logs:
|
Seeing this issue on
|
Wondering if it's also related to load on the test machine; I think it's been mainly failing on RS1 and Power/s390x, which have been slower/more resource constraint. For example, the same test on amd64 runs in 2.3 seconds; https://ci.docker.com/public/job/moby/job/PR-39992/3/testReport/amd64/integration-cli/Build___amd64___Run_tests___TestDockerSuite_TestStartReturnCorrectExitCode/ |
Had a failure of this test on Linux this time; #41605, so not just affecting Windows it seems
|
Seen on #31551
Was failed on RS1 and found from Jenkins logs that it has failed at least couple of times on RS5 and at least on powerpc too
The text was updated successfully, but these errors were encountered: