-
Notifications
You must be signed in to change notification settings - Fork 10.2k
Add robustness test regression target for 20693 #20663
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?
Add robustness test regression target for 20693 #20663
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: henrybear327 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
d3481ed to
3566e71
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted filessee 34 files with indirect coverage changes @@ Coverage Diff @@
## main #20663 +/- ##
==========================================
- Coverage 69.14% 69.05% -0.10%
==========================================
Files 420 417 -3
Lines 34817 34682 -135
==========================================
- Hits 24074 23948 -126
+ Misses 9338 9324 -14
- Partials 1405 1410 +5 Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
|
THe robustness tests flaked with |
|
There is also flake on |
Not yet, as I am looking into it just now. I was actually puzzled when I saw the watch validation passed on CI, but the test failed. |
c7112ac to
8de83cd
Compare
|
The target is created! Reproduction is now consistent. |
06f3ee9 to
9e80f44
Compare
|
/retest pull-etcd-robustness-amd64 |
|
@henrybear327: The Use In response to this:
Instructions 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. |
|
/test pull-etcd-robustness-amd64 |
c11049c to
a0744cb
Compare
a0744cb to
70a3d98
Compare
|
@serathius I am renaming the target to |
8387c9e to
fc5b2c7
Compare
|
Merging of this PR is dependent on #20689 |
fc5b2c7 to
adb5c97
Compare
adb5c97 to
926f4c1
Compare
|
/retest |
7a2a7b3 to
e5cd591
Compare
|
|
||
| scenarios = append(scenarios, TestScenario{ | ||
| Name: "issue20693", | ||
| Profile: traffic.HighTrafficProfile.WithoutCompaction().WithBackgroundWatchConfigInterval(10 * time.Millisecond).WithBackgroundWatchConfigRevisionOffset(-10), |
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.
This is not the best way to reproduce the issue. The current reproduction rate (one per 30 minutes) is to low. As the root cause is known, request with watch revision -1, please consider adding more targeted test to ensure higher reproducibility.
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.
Got you.
Still puzzled by how come I am consistently reproduce the problem almost all the time with <2 min on my Macbook but not else where.
e5cd591 to
6782a10
Compare
| e2e.WithClusterSize(3), | ||
| e2e.WithCompactionBatchLimit(10), | ||
| e2e.WithSnapshotCount(50), | ||
| e2e.WithSnapshotCatchUpEntries(100), | ||
| e2e.WithGoFailEnabled(true), | ||
| e2e.WithPeerProxy(true), | ||
| e2e.WithIsPeerTLS(true), |
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.
With the current root cause known, we can just disable most of those config changes.
Reference: - etcd-io#20693 Signed-off-by: Chun-Hung Tseng <[email protected]>
6782a10 to
7587cfc
Compare
|
@henrybear327: The following tests 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. Instructions 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. |
Based on the discovery from Marek #20234 #20221 (comment).
Please see the discussion starting from #20349 (comment)
Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.