kubevirt-bot
commented
3 years ago Hi @alonSadan. Thanks for your PR.
I'm waiting for a k8snetworkplumbingwg member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.
Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
alonSadan
phoracek
The current timeout in the tests is 2 minutes. The update interval is 1 minute, and it has a jitter of 1.2. IF the test assertion start right after the start of the interval, 1 minute has passed , and for some reason the update fails, there could be more than two minutes between updates, and the tests could fail.
This commit increases the tests timeout to 3 minutes, which should be enough.
Signed-off-by: alonsadan asadan@redhat.com