Accounting for asynchronous service removals #2228
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Swarmkit services' removal will soon become asynchronous (see
moby/moby#38525); that is, a service will only actually
get deleted once all of its containers are shut down.
This patch changes service tests'
tearDown
to wait for services to beactually removed, so that there's no name collision with subsequent tests.
This change is fully backward compatible with the engine's current behaviour.
Couple of other misc changes: consolidated polling in a single
wait_until_truthy
function, and allowed passing more flags topy.test
inthe makefile test-integration targets through a new optional
pytest_options
env variable.
Signed-off-by: Jean Rouge [email protected]