f2f1060ed2
In case when no device supporting Namespace Managment was found, the test case exits without producing an error. For example QEMU NVMe emulated device does not support it, thus only physical devices have to be used right now. This goes against design of "run_test" function, that when executed should always run and never silently skip. This patch adds check whether there is a device support and triggers the test case only then. Note that original code for selecting the device is still in original script. This is to enable running nvme_ns_manage_cuse.sh on its own. Right now CUSE tests are only enabled on VMs so nvme_ns_manage_cuse, was added to exception list. This will soon be reverted as the tests are moved to job that runs on physical machines. Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: Ie784696c2628b5fe45ce751b3978abcc03118cd9 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/2828 Community-CI: Broadcom CI Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| cuse.c | ||
| Makefile | ||
| nvme_cuse_rpc.sh | ||
| nvme_cuse.sh | ||
| nvme_ns_manage_cuse.sh | ||
| spdk_nvme_cli_cuse.sh | ||
| spdk_smartctl_cuse.sh | ||