Originally the idea was to disable error checking, to match output from Kernel and SPDK NVMe cuse. This includes passing test commands and failures. Any discrepancy would be caught by log output diff at the end. Flaw in this logic is that test command itself might be incorrect. We shouldn't depend on that, nor attempt to cover up some of the failures even if they occur on both interfaces. Most probable cause for this at all, was NVMe emulated in QEMU not really working with all the nvme-cli commands from this test. Since the original creation of this test, CUSE executes on physical devices (to be able to support namespace management). The behavior there is predictable and works with current test commands, thus the test exits on any error with this patch. Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: I086faf38b2cbbb6225935cc50d4fad14e81f1972 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/3032 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@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 |