Intermittent unit-test failure: TestBatchContainerHappyPath() #662
Comments
This was referenced Jan 12, 2017
aaithal
added a commit
to aaithal/amazon-ecs-agent
that referenced
this issue
Feb 9, 2017
This should hopefully remove the flakiness reported in aws#662
aaithal
added a commit
that referenced
this issue
Feb 9, 2017
* Force steady state check in TestBatchContainerHappyPath. This should hopefully remove the flakiness reported in #662 * Refactor task engine tests to use testify and to extract the common createDockerEvent into a function of its own
|
Should be fixed with #703 |
jwerak
pushed a commit
to appuri/amazon-ecs-agent
that referenced
this issue
Jun 8, 2017
* Force steady state check in TestBatchContainerHappyPath. This should hopefully remove the flakiness reported in aws#662 * Refactor task engine tests to use testify and to extract the common createDockerEvent into a function of its own
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On Windows Platform, unit-test sometimes fails on TestBatchContainerHappyPath() testcase.
Here is the output of failure:
--- FAIL: TestBatchContainerHappyPath (0.01s)
controller.go:113: no matching expected call: *engine.MockDockerClient.DescribeContainer([containerId])
The text was updated successfully, but these errors were encountered: