Closed iranzo closed 5 years ago
/cc ptrnull /kind enhancement
/retest
Do we need this? AFAIK we've been able to spin VMs just fine with nested virt so far - which should perform quite better than emulation.
The environment setup code includes enabling nested virt.
This is to test the failure in CI in #108 to see if the timeout in lab4 happens because of vm spin as the commit in that PR should have nothing to do at all with infra failing, but it does
If this test passes, means that nested is 'now' needed for another reason and might, via merge, enable us to pass 108 and merge it
I see... however, if CI is broken let's rather fix the CI, no?
My understanding is that with this change the labs would run slower, right?
@iranzo: The following test failed, say /retest
to rerun them all:
Test name | Commit | Details | Rerun command |
---|---|---|---|
kubevirt-tutorial-presubmit-lab-testing-k8s-1.13.3 | a1dfccfd81f314b4421513bcb658a380d058ec62 | link | /test kubevirt-tutorial-presubmit-lab-testing-k8s-1.13.3 |
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: To complete the pull request process, please assign iranzo You can assign the PR to them by writing
/assign @iranzo
in a comment when ready.The full list of commands accepted by this bot can be found here.