b88f0c4f20
Failure to prepare CUnit for tests is always a fatal error, and application exits. Most test managment functions in CUnit set some CU_ErrorCode, that can be retrived by return code from a function or CU_get_error(). Thus usual structure of UT in SPDK checked every output from every test managment function. There is a helper function CU_set_error_action() that when set to CUEA_ABORT, will abort the application run with proper error return code. Along with nice error message. For example if one were to add same UT twice: "Aborting due to error #32: Test having this name already in suite." Application return code set to 32. Using CU_set_error_action(CUEA_ABORT), removes the need for error checking on test managment functions in CUnit. Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: Ida7de5e040b714509e79957d47a006ee518a42b8 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/930 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> |
||
|---|---|---|
| .. | ||
| blob.c | ||
| bs_dev_common.c | ||
| bs_scheduler.c | ||
| Makefile | ||