Commit e3f54f32 authored by Jim Harris's avatar Jim Harris
Browse files

test/blob: add some SPDK_CU_ASSERT_FATAL checks 



I have no idea why - but scan-build starts complaining about
some missing SPDK_CU_ASSERT_FATAL checks when analyzing the
next patch - even though that patch has nothing whatsoever
to do with the scan-build error reports.

scan-build is really weird sometimes.

Signed-off-by: default avatarJim Harris <james.r.harris@intel.com>
Change-Id: I3d426384fa4f846abf2eb98fd29ee308d08c1943

Reviewed-on: https://review.gerrithub.io/391875


Reviewed-by: default avatarDaniel Verkamp <daniel.verkamp@intel.com>
Reviewed-by: default avatarBen Walker <benjamin.walker@intel.com>
Tested-by: default avatarSPDK Automated Test System <sys_sgsw@intel.com>
parent feba13bb

test/unit/lib/blob/blob.c/blob_ut.c

+3 −3
Original line number Diff line number Diff line
@@ -2012,17 +2012,17 @@ blob_flags(void) 


	spdk_bs_open_blob(g_bs, blobid_invalid, blob_op_with_handle_complete, NULL);

	CU_ASSERT(g_bserrno == 0);

	CU_ASSERT(g_blob != NULL);

	SPDK_CU_ASSERT_FATAL(g_blob != NULL);

	blob_invalid = g_blob;



	spdk_bs_open_blob(g_bs, blobid_data_ro, blob_op_with_handle_complete, NULL);

	CU_ASSERT(g_bserrno == 0);

	CU_ASSERT(g_blob != NULL);

	SPDK_CU_ASSERT_FATAL(g_blob != NULL);

	blob_data_ro = g_blob;



	spdk_bs_open_blob(g_bs, blobid_md_ro, blob_op_with_handle_complete, NULL);

	CU_ASSERT(g_bserrno == 0);

	CU_ASSERT(g_blob != NULL);

	SPDK_CU_ASSERT_FATAL(g_blob != NULL);

	blob_md_ro = g_blob;



	__blob_to_data(blob_invalid)->invalid_flags = (1ULL << 63);