-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Allow a single test to override suite timeout #26833
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
Allow a single test to override suite timeout #26833
Conversation
|
Related to #26810 |
|
/retest |
|
/lgtm |
soltysh
left a comment
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
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andfasano, bfournie, soltysh 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 |
|
/retest-required |
|
@andfasano: all tests passed! Full PR test history. Your PR dashboard. 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/test-infra repository. I understand the commands that are listed here. |
This patch adds the possibility to override the current timeout defined at the suite level for a specif test. This is required since in some specific cases a single test may require some extra time to successfully complete its execution, and it's not desirable to modify the global suite timeout since it will affect also other tests in the same suite.
The timeout is specified as part of the name using the special tag
[Timeout:<duration>]with the required duration string, for example:In case of a malformed/incorrect duration string an error will be reported immediatly.