DockerClientProviderStrategy.getDescription() should be called after …#218
Merged
rnorth merged 1 commit intotestcontainers:masterfrom Sep 11, 2016
kunickiaj:logorder
Merged
DockerClientProviderStrategy.getDescription() should be called after …#218rnorth merged 1 commit intotestcontainers:masterfrom kunickiaj:logorder
rnorth merged 1 commit intotestcontainers:masterfrom
kunickiaj:logorder
Conversation
Member
|
Looks good to me - thanks. Seeing a strange failure on Travis but looks unrelated, so will merge anyway. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When using testcontainers 1.1.0+ I get the following
In the refactoring that happened for 1.1.0+ the DockerClientProviderStrategy logs strategy.getDescription() before the config is initialized, which is why for Environment strategy the values are empty. This simply reverses the logging order to after test() has been called and config is populated.