Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

sporadic failure in 666_abuse_of_start_test #1502

Closed
rade opened this issue Oct 3, 2015 · 0 comments · Fixed by #1537
Closed

sporadic failure in 666_abuse_of_start_test #1502

rade opened this issue Oct 3, 2015 · 0 comments · Fixed by #1537
Labels
bug [component/proxy]
Milestone
1.2.0

Comments

@rade
Copy link
Member

rade commented Oct 3, 2015

Have seen this on my machine...

test #1 "docker_on 192.168.48.13 inspect -f '{{.State.Running}} {{.State.ExitCode}} {{.HostConfig.Dns}}' c2" failed:
    expected "false 0 [172.17.42.1]"
    got "true 0 [172.17.42.1]"

I suspect the test is racy; the container may not have terminated yet when inspect is called.
@paulbellamy paulbellamy mentioned this issue Oct 14, 2015
Merged
rade added a commit that referenced this issue Oct 14, 2015
@rade
Merge pull request #1537 from weaveworks/1502-flakey-test
aac5fb8 
Wait until container exits in test to remove race condition

Fixes #1502
@rade rade added this to the 1.2.0 milestone Oct 15, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug [component/proxy]
Projects
None yet
Milestone
1.2.0
Development

Successfully merging a pull request may close this issue.

Wait until container exits in test to remove race condition weaveworks/weave
1 participant
@rade