-
Notifications
You must be signed in to change notification settings - Fork 18.7k
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
Remove duplicate TestServiceUpdatePort #36502
Conversation
The TestAPIServiceUpdatePort test performs exactly the same steps. Signed-off-by: Sebastiaan van Stijn <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🐯
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Odd, that test was added in #36316, but trying to understand how |
oh! misreading, was looking at service count, not task-count (thanks @vdemeester), so that test is failing at moby/integration/network/service_test.go Line 52 in 0b0af85
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Codecov Report
@@ Coverage Diff @@
## master #36502 +/- ##
=========================================
Coverage ? 34.64%
=========================================
Files ? 613
Lines ? 45404
Branches ? 0
=========================================
Hits ? 15730
Misses ? 27614
Partials ? 2060 |
The
TestAPIServiceUpdatePort
test performs exactly the same steps.Here's one;
moby/integration-cli/docker_cli_service_update_test.go
Lines 14 to 47 in 5a48410
And the other;
moby/integration-cli/docker_api_swarm_service_test.go
Lines 32 to 51 in 5a48410