-
Notifications
You must be signed in to change notification settings - Fork 593
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
ducktape: Respect rpk timeout in rpk #24642
base: dev
Are you sure you want to change the base?
Conversation
Pass the timeout value for rpk that is passed to subprocess also to rpk itself via `request_timeout_overhead`. Otherwise the specified timeout will not really be respected if the default timeout in rpk for a certain command is shorter. Because `request_timeout_overhead` is on top of other possible timeouts the total timeout might be larger than the subprocess one but that should be fine.
All CDT failure are known |
@@ -71,8 +71,7 @@ def test_modify_then_query_error(self): | |||
FailureSpec(FailureSpec.FAILURE_ISOLATE, | |||
self.redpanda.controller())) | |||
|
|||
# Timeout must be larger then hardcoded timeout of 5s within redpanda | |||
_ = superclient.acl_list(request_timeout_overhead=30) | |||
_ = superclient.acl_list() |
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.
Won't this set this test back to 5s timeout, which may cause it to fail?
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.e., don't we need to set timeout
on the rpk object to 30s now in this test.
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.
No not really because the default timeout is 30s anyway and the request_timeout_overhead
thing now effectively applies to everything so the special casing in acl_list
isn't needed anymore.
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.
question
CI test resultstest results on build#60219
|
Pass the timeout value for rpk that is passed to subprocess also to rpk
itself via
request_timeout_overhead
.Otherwise the specified timeout will not really be respected if the
default timeout in rpk for a certain command is shorter.
Because
request_timeout_overhead
is on top of other possible timeoutsthe total timeout might be larger than the subprocess one but that
should be fine.
Backports Required
Release Notes