+28
−29
Loading
This test has always relied on /dev/nvme0n1 being the location of our test drive which means that it is the only one in the system at the time the test is run. So instead of trying to loop multiple non-existant nvme drives, just call it out directly. Also, add a todo to remove the dependence on NVMe0n1 since we could run this test on a machine where the main filesystem is on an NVMe drive which would break this test. Change-Id: Ibb2448d9367a5c80d85a1c91b0c6e44e58237751 Signed-off-by:Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476952 Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Reviewed-by:
Tomasz Zawadzki <tomasz.zawadzki@intel.com> Reviewed-by:
Jim Harris <james.r.harris@intel.com>