5170ac8d83
This is a significant simplification to the whole test script. Note, it does force us to run the hello_bdev example against a gpt bdev instead of an nvme bdev directly, but I see this as an acceptable tradeoff since it seems like the purpose of running the hello_bdev example is mostly to ensure that the example itself is not broken. Change-Id: I8c2a1ede8e7ece2a82222593a7ae46704cc658af Signed-off-by: Seth Howell <seth.howell@intel.com> Reviewed-on: https://review.gerrithub.io/c/spdk/spdk/+/476935 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom SPDK FC-NVMe CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Karol Latecki <karol.latecki@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> |
||
|---|---|---|
| .. | ||
| bdevio | ||
| bdevperf | ||
| bdev_raid.sh | ||
| bdev.conf.in | ||
| blockdev.sh | ||
| gen_crypto.sh | ||
| Makefile | ||
| nbd_common.sh | ||