test/nvme_cuse: start nvme_cuse ctrlr in test_nvme_cuse_stop()
Patch below broke the UT due to not accouting for changes in nvme_cuse since original submission: (19f0bfd
) test/nvme_cuse: cases for stop cuse The change was introduced with: (d651f8a
) nvme/nvme_cuse: Fix race condition in cuse session Now when initalizing nvme_cuse controller it uses is_started, to avoid race condition. The UT was missing this part of nvme_cuse controller initalization. Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: I46344977204c3383d8f400c80bc7df50e6d7581d Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9001 Reviewed-by: Michal Berger <michalx.berger@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
This commit is contained in:
parent
80b3b68841
commit
7aed75fbc2
@ -363,6 +363,7 @@ test_nvme_cuse_stop(void)
|
||||
|
||||
g_ctrlr_started = spdk_bit_array_create(128);
|
||||
SPDK_CU_ASSERT_FATAL(g_ctrlr_started != NULL);
|
||||
ctrlr_device->is_started = true;
|
||||
|
||||
ctrlr_device->ns_devices[0].is_started = true;
|
||||
ctrlr_device->ns_devices[1].is_started = true;
|
||||
|
Loading…
Reference in New Issue
Block a user