-
Notifications
You must be signed in to change notification settings - Fork 618
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
Testing - TestDockerStateToContainerState flaky #1899
Labels
Comments
suneyz
changed the title
Testing - TestDockerStateToContainerState
Testing - TestDockerStateToContainerState flaky
Feb 27, 2019
fenxiong
added a commit
to fenxiong/amazon-ecs-agent
that referenced
this issue
Mar 6, 2019
During the workflow of TestDockerStateToContainerState, it starts a container and checks whether it's running by inspecting it. However, the container it starts exit immediately, so it's possible that when we check whether the container is running it's already stopped. This leads to flakey test as per aws#1899. Fixing by letting the container keep running rather than exit itself.
fenxiong
added a commit
to fenxiong/amazon-ecs-agent
that referenced
this issue
Mar 6, 2019
During the workflow of TestDockerStateToContainerState, it starts a container and checks whether it's running by inspecting it. However, the container it starts exit immediately, so it's possible that when we check whether the container is running it's already stopped. This leads to flakey test as per aws#1899. Fixing by letting the container keep running rather than exit itself.
fenxiong
added a commit
to fenxiong/amazon-ecs-agent
that referenced
this issue
Mar 6, 2019
During the workflow of TestDockerStateToContainerState, it starts a container and checks whether it's running by inspecting it. However, the container it starts exit immediately, so it's possible that when we check whether the container is running it's already stopped. This leads to flakey test as per aws#1899. Fixing by letting the container keep running rather than exit itself.
fenxiong
added a commit
that referenced
this issue
Mar 7, 2019
During the workflow of TestDockerStateToContainerState, it starts a container and checks whether it's running by inspecting it. However, the container it starts exit immediately, so it's possible that when we check whether the container is running it's already stopped. This leads to flakey test as per #1899. Fixing by letting the container keep running rather than exit itself.
#1926 fixes this. closing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
TestDockerStateToContainerState failed intermittently.
Description
Expected Behavior
Observed Behavior
Environment Details
Supporting Log Snippets
The text was updated successfully, but these errors were encountered: