-
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
[3.5] backport mix version e2e test. #17531
[3.5] backport mix version e2e test. #17531
Conversation
/retest |
1 similar comment
/retest |
bb9c887
to
c68bdcb
Compare
/retest |
cc @serathius @ahrtr |
c68bdcb
to
770bdaf
Compare
770bdaf
to
728ad60
Compare
Please link to the original PR next time when you backport any PR. |
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.
/lgtm
cc @fuweid @jmhbnz @serathius double check
require.NoError(t, err, "failed to start etcd cluster: %v", err) | ||
defer func() { | ||
derr := epc.Close() | ||
require.NoError(t, derr, "failed to close etcd cluster: %v", derr) |
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.
require.NoError(t, epx.Close(), "failed to close etcd cluster") might be cleaner.
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.
If using require.NoError(t, epx.Close(), "failed to close etcd cluster")
, we would not know what error is returned.
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.
If epc.Close() is not nil, require.NoError will panic and show us.
Never mind. Just share that we don't need to pass error value in message.
728ad60
to
6088caf
Compare
/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.
LGTM
Testing snapshot exchange between members in mixed version cluster is super useful! Thanks for adding those tests. My suggestions:
|
Signed-off-by: Siyuan Zhang <sizhang@google.com>
6088caf
to
c06ec72
Compare
The blackhole failpoint is problematic right now #17737 |
Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.
Part of #15878 (comment)
Original PR: #14707 and #15013
Slightly different from the tests in main in that we cannot verify a snapshot is sent because there is no
snapshot-catchup-entries
flag in 3.5.