This repository has been archived by the owner on May 12, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 376
cli go test
failures
#1508
Comments
bergwolf
added a commit
to bergwolf/kata-runtime
that referenced
this issue
Apr 9, 2019
We don't really require nested nor unrestricted_guest to run. And there is no point validating host cpu properties in UT. Fixes: kata-containers#1508 Signed-off-by: Peng Tao <bergwolf@hyper.sh>
bergwolf
added a commit
to bergwolf/kata-runtime
that referenced
this issue
Apr 10, 2019
We don't really require nested nor unrestricted_guest to run. And there is no point validating host cpu properties in UT. Fixes: kata-containers#1508 Signed-off-by: Peng Tao <bergwolf@hyper.sh>
egernst
pushed a commit
to egernst/runtime
that referenced
this issue
Apr 16, 2019
We don't really require nested nor unrestricted_guest to run. And there is no point validating host cpu properties in UT. Fixes: kata-containers#1508 Signed-off-by: Peng Tao <bergwolf@hyper.sh>
ganeshmaharaj
pushed a commit
to ganeshmaharaj/kata-runtime
that referenced
this issue
Apr 16, 2019
cli: fix kata-check test (cherry picked from commit da08b3a) Fixes: kata-containers#1508 Signed-off-by: Ganesh Maharaj Mahalingam <ganesh.mahalingam@intel.com>
egernst
pushed a commit
to egernst/runtime
that referenced
this issue
Apr 17, 2019
We don't really require nested nor unrestricted_guest to run. And there is no point validating host cpu properties in UT. Fixes: kata-containers#1508 Signed-off-by: Peng Tao <bergwolf@hyper.sh>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We don't really require nested nor unrestricted_guest to run. And there is no point validating host cpu properties in UT.
The text was updated successfully, but these errors were encountered: