Spdk/test/lvol
Jim Harris d8b8bc4353 test/lvol: wait for lvolstore tasting after nvme bdev construction
A couple of the lvol tests delete the nvme bdev, then construct
it again to test lvolstore tasting.  But constructing the nvme
bdev and then the tasting can take a tiny bit of time, and if
we check for the lvolstore too soon, it could fail.  There are
a large number of intermittent test failures in the test pool
that show this signature.

So sleep one second to allow time for the tasting to complete.

Signed-off-by: Jim Harris <james.r.harris@intel.com>
Change-Id: Iebabe09458302d8300e704f232fdbb245b562268

Reviewed-on: https://review.gerrithub.io/392559
Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com>
Tested-by: SPDK Automated Test System <sys_sgsw@intel.com>
Reviewed-by: Ben Walker <benjamin.walker@intel.com>
Reviewed-by: Karol Latecki <karol.latecki@intel.com>
2017-12-21 10:42:17 -05:00
..
lvol_test.py test/lvol: Add lvol tasting test 2017-11-17 18:24:08 -05:00
lvol.sh test/lvol: Add lvol tasting test 2017-11-17 18:24:08 -05:00
rpc_commands_lib.py test/lvol: Replace stop/start vhost with add/delete bdev 2017-12-13 11:26:54 -05:00
test_cases.py test/lvol: wait for lvolstore tasting after nvme bdev construction 2017-12-21 10:42:17 -05:00
test_plan.md test/lvol: Replace stop/start vhost with add/delete bdev 2017-12-13 11:26:54 -05:00