fix: increase timeout for end-to-end tests #636
Conversation
In some cases, the current timeout of 600 seconds is insufficient for starting a virtual machine (VM). To address this issue, we propose increasing the timeout to 900 seconds, which should provide adequate time for the VM to start successfully. Signed-off-by: Nestor Acuna Blanco <[email protected]>
kubevirt-bot
added
the
release-note-none
kubevirt-bot
added
the
dco-signoff: yes
|
Hi @nestoracunablanco. Thanks for your PR. I'm waiting for a kubevirt member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
openshift-ci
bot
added
the
needs-ok-to-test
|
/ok-to-test |
openshift-ci
bot
added
ok-to-test
|
/retest |
|
As a follow-up, we should understand why VMs are taking so long, 600 seconds should be enough to start a VM. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 0xFelix The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
kubevirt-bot
added
the
approved
In some cases, the current timeout of 600 seconds is insufficient for starting a virtual machine (VM). To address this issue, we propose increasing the timeout to 900 seconds, which should provide adequate time for the VM to start successfully.
What this PR does / why we need it: s390x enablement
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
Release note: