-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
Reproduce #17529 in robustness tests #17680
Conversation
Skipping CI for Draft Pull Request. |
Based on #16761 as introducing compaction prevents us from depending on Watch events for their persistance. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted filessee 23 files with indirect coverage changes @@ Coverage Diff @@
## main #17680 +/- ##
==========================================
+ Coverage 68.75% 68.95% +0.20%
==========================================
Files 416 416
Lines 35128 35128
==========================================
+ Hits 24152 24223 +71
+ Misses 9569 9512 -57
+ Partials 1407 1393 -14 Continue to review full report in Codecov by Sentry.
|
6d11170
to
24f0a7f
Compare
Signed-off-by: Marek Siarkowicz <siarkowicz@google.com>
cc @fuweid @siyuanfoundation @MadhavJivrajani |
Signed-off-by: Marek Siarkowicz <siarkowicz@google.com>
/retest |
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.
fuse: device not found, try 'modprobe fuse' first
We can disable lazyfs recently.
@@ -0,0 +1,12 @@ | |||
diff --git a/server/etcdserver/api/v3rpc/watch.go b/server/etcdserver/api/v3rpc/watch.go |
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.
I like this idea~
/retest |
sws.mu.RUnlock() | ||
|
||
var serr error | ||
+ // gofail: var beforeSendWatchResponse struct{} |
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.
should the failpoint also be backported to 3.5 to ensure the issue is fixed for the latest 3.5 release?
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.
Right, there is even a issue for that #17817
ping @fuweid @MadhavJivrajani |
Reproduce #17529