Skip to content
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

Stress testing concurrent start/stop operations on the same container #5655

Closed
hickeng opened this issue Jul 6, 2017 · 0 comments · Fixed by #5681
Closed

Stress testing concurrent start/stop operations on the same container #5655

hickeng opened this issue Jul 6, 2017 · 0 comments · Fixed by #5681
Assignees
Labels
component/test Tests not covered by a more specific component label priority/p2 source/customer Reported by a customer, directly or via an intermediary
Milestone

Comments

@hickeng
Copy link
Member

hickeng commented Jul 6, 2017

Follow on from #5445

This issue needed a tight race between two loops to recreate: #5445 (comment)
This was exercising concurrent operations on the same container, one loop being a docker restart and the other a docker start; docker stop pair.
Errors about container unexpectedly stopping are expected, but EOFs and similar should not occur.

This test needs to be captured in robot.

Tagged as customer found as this was identified from a customer reported issue.

@hickeng hickeng added source/customer Reported by a customer, directly or via an intermediary kind/quality priority/p2 labels Jul 6, 2017
@mhagen-vmware mhagen-vmware added the component/test Tests not covered by a more specific component label label Jul 6, 2017
@mhagen-vmware mhagen-vmware self-assigned this Jul 6, 2017
@mhagen-vmware mhagen-vmware added this to the Sprint 12 milestone Jul 6, 2017
@mhagen-vmware mhagen-vmware modified the milestones: Sprint 13, Sprint 12 Jul 18, 2017
@mdubya66 mdubya66 modified the milestones: Sprint 14, Sprint 13 Aug 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/test Tests not covered by a more specific component label priority/p2 source/customer Reported by a customer, directly or via an intermediary
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants