libnetwork: wait until t.Deadline() instead of hardcoded value#42703
Merged
Conversation
added 2 commits
August 1, 2021 17:47
Signed-off-by: Roman Volosatovs <[email protected]>
Use `verifyNetworkExistence` like it was done in 2837fba Signed-off-by: Roman Volosatovs <[email protected]>
Author
|
Failures seem unrelated: |
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
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.
(hopefully?) closes #42698
- What I did
It seems that the flakiness is caused by the occasional slowness of the CI, hence wait until
t.Deadlinefor node to appear instead of relying on a hard-coded value, which may or may not suffice in all environments.Also applied the same "waiting" approach from #42625 in the unit test in question.
- How I did it
Check for
t.Deadlineand, if set, wait until at most that; use the previous hard-coded value otherwise. Since we settimeoutinhack/test/unit, the deadline value should generally be set regardless of the environment, so this should work in CI, as well as locally (unless, of course, tests are run directly withgo test).- How to verify it
I suppose the only way would be to observe multiple CI runs
- Description for the changelog
- A picture of a cute animal (not mandatory but encouraged)