-
Notifications
You must be signed in to change notification settings - Fork 10.3k
[Robustness test] Implement RunWatchLoop and integrate into robustness test (part 2) #21071
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
base: main
Are you sure you want to change the base?
[Robustness test] Implement RunWatchLoop and integrate into robustness test (part 2) #21071
Conversation
|
/retest |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted filessee 25 files with indirect coverage changes @@ Coverage Diff @@
## main #21071 +/- ##
==========================================
+ Coverage 68.44% 68.57% +0.12%
==========================================
Files 429 429
Lines 35281 35281
==========================================
+ Hits 24149 24194 +45
+ Misses 9732 9691 -41
+ Partials 1400 1396 -4 Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
cc5fa24 to
2e688e4
Compare
2e688e4 to
23abb59
Compare
906157f to
f4baca0
Compare
c8d1332 to
97dc9ba
Compare
|
Have you verified how this PR changes reproducibility of previous issues found by robustness? |
|
I think this PR is the best next step as it migrates Left couple of comments, also I'm testing it for reproduction of old watch issues. |
This is in progress. |
Thank you for helping with the testing. I have closed the old part 2 PR and focus on this one instead. |
|
Please squash commits |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: henrybear327, serathius The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…or etcd traffic Signed-off-by: Marek Siarkowicz <[email protected]> Signed-off-by: Chun-Hung Tseng <[email protected]>
388c287 to
986527e
Compare
|
@henrybear327: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
| MaxNonUniqueRequestConcurrency: 3, | ||
| BackgroundWatchConfig: options.BackgroundWatchConfig{ | ||
| WatchConfig: options.WatchConfig{ | ||
| Interval: 0, |
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.
So you are enabling the mechanism in robustness tests but not in Antithesis? Why?
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.
Also interval = 0, means create watch continiously.
| return | ||
| case <-p.Finish: | ||
| return | ||
| case <-time.After(p.Interval): |
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.
What happens if interval is set to 0 ?
Implement
RunWatchLoopin etcd traffic.Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.