-
Notifications
You must be signed in to change notification settings - Fork 164
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
[tests-only] retry if auto-sync is enabled but client.synchronize is false #8891
base: master
Are you sure you want to change the base?
Conversation
5e3378e
to
939c605
Compare
ce01df3
to
d1d95b8
Compare
|
51e3e10
to
1a65d16
Compare
); | ||
); | ||
|
||
$jsonObj = $this->featureContext->getJsonDecodedResponseBodyContent($response); |
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.
$jsonObj = $this->featureContext->getJsonDecodedResponseBodyContent($response); | |
$jsonObj = $this->featureContext->getJsonDecodedResponseBodyContent($response); |
$jsonObj name should be replace with meaningful name
Previously flaky scenarios are consistent with this explicit wait 4e66cc7. Though it is not so good to have hard coded wait, the fix in this PR (retry step) is also not that much promising because it can lead to confusion in the future where there might be scenarios that manipulate share-sync config in different ways. So, let's keep the wait fix and I will close this PR for now. |
to avoid flaky we can check that for another scenarios we can check it like
|
Let's keep the current fix. We can come back to this if we get other flakiness |
1a65d16
to
73f1e1f
Compare
Quality Gate passedIssues Measures |
Description
Implemented retry when listing the shares if auto-sync is enabled but client.synchronize is false. If the auto-sync is disabled then the retry will be skipped.
Scenarios can pass with retry:
Related Issue
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: