Soak tests: Do not assume hypervisors run with the full path#1803
Soak tests: Do not assume hypervisors run with the full path#1803mcastelino wants to merge 1 commit intokata-containers:masterfrom
Conversation
|
/test |
4221868 to
26d99df
Compare
|
it seems that is not detecting the hypervisor |
|
@mcastelino to test locally your change just run a container in detach an see if |
|
/test |
|
Seems like we need to modify https://github.com/kata-containers/tests/blob/master/metrics/lib/common.bash#L192-L214 to get values from firecracker and nemu |
Soak tests assume hypervisors run with the full path. However when running a hypervisor with jailer the path is relative to the jail and hence the check should only look for the process. For example when running firecracker with jailer the process will be ``` /firecracker --id=5af26fcea8dbf413067e90026fd9845515d5a1f300d61f66427760a27ef114c2 --seccomp-level=2 --start-time-us=1562786230593253 --start-time-cpu-us=223 --api-sock=/api.socket� where /firecracker is relative to the jailed location. ``` Fixes: kata-containers#1802. Signed-off-by: Manohar Castelino <manohar.r.castelino@intel.com>
26d99df to
cc8b905
Compare
|
/test_fc |
@GabyCT yes it does. And tests passes locally. |
grahamwhaley
left a comment
There was a problem hiding this comment.
code change lgtm
there are some tricky rules with pkill and pgrep to do with paths and pattern matching iirc, but afaict this change looks right.
| how_many_qemus=$(pgrep -a -f ${HYPERVISOR_PATH} | wc -l) | ||
| if (( ${how_many_running} != ${how_many_qemus} )); then | ||
| echo "Wrong number of qemus running (${how_many_running} != ${how_many_qemus}) - stopping" | ||
| vmm_process=$(basename ${HYPERVISOR_PATH}) |
There was a problem hiding this comment.
note: you can use the bashism ${x##*/} or similar instead of invoking basename :-)
|
/test |
I also see that has a |
|
@mcastelino and @grahamwhaley , I just enable the |
|
/test-fc |
|
we can add an skip to the soak test, as I can not reproduce it locally on a VM this is the issue #1804 where I will debug the CI. |
Currently we have issues while trying to run the soak test on firecracker (see kata-containers#1803). We need to remove it so the change kata-containers/runtime#1649 can be merged. Fixes kata-containers#1805 Signed-off-by: Gabriela Cervantes <gabriela.cervantes.tellez@intel.com>
|
Closing this one as this is being addressed in #1807 |
Currently we have issues while trying to run the soak test on firecracker (see kata-containers#1803). We need to remove it so the change kata-containers/runtime#1649 can be merged. Fixes kata-containers#1805 Signed-off-by: Gabriela Cervantes <gabriela.cervantes.tellez@intel.com>
Currently we have issues while trying to run the soak test on firecracker (see kata-containers#1803). We need to remove it so the change kata-containers/runtime#1649 can be merged. Fixes kata-containers#1805 Signed-off-by: Gabriela Cervantes <gabriela.cervantes.tellez@intel.com>
Soak tests assume hypervisors run with the full path.
However when running a hypervisor with jailer the path is relative to
the jail and hence the check should only look for the process.
For example when running firecracker with jailer the process will be
/firecracker
--id=5af26fcea8dbf413067e90026fd9845515d5a1f300d61f66427760a27ef114c2
--seccomp-level=2 --start-time-us=1562786230593253
--start-time-cpu-us=223 --api-sock=/api.socket�
where /firecracker is relative to the jailed location.
Fixes: #1802
Signed-off-by: Manohar Castelino manohar.r.castelino@intel.com