Tests: initialize all resources and then call vshard.storage.cfg to avoid flaky test #82
Conversation
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
nurzhan-saktaganov
force-pushed
the
nsaktaganov_resolve_issue_81
branch
from
08e11f5 to
5d29d15
Compare
Calling vshard.storage.cfg before creating methods, spaces and granting privileges sometimes caused flaky tests, because vshard storage started to handle requests before fully initializing its resources. Closes tarantool#81
nurzhan-saktaganov
force-pushed
the
nsaktaganov_resolve_issue_81
branch
from
5d29d15 to
9910d78
Compare
|
This fix doesn't work |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Calling vshard.storage.cfg before creating methods, spaces and granting privileges sometimes caused flaky tests, because vshard storage started to handle requests before fully initializing its resources.
Closes #81
What has been done? Why? What problem is being solved?
I didn't forget about (remove if it is not applicable):
Related issues: