EVS coverage test fails when CFE_PLATFORM_EVS_DEFAULT_TYPE_FLAG is set to 0xF

[skliper]

Describe the bug
When CFE_PLATFORM_EVS_DEFAULT_TYPE_FLAG is set to 0xF there are two failures:

[ FAIL] 14.001 evs_UT.c:2675 - CFE_EVS_WriteLogDataFileCmd - Write log data - successful
[ FAIL] 14.002 evs_UT.c:2685 - CFE_EVS_SetLogModeCmd - Set logging mode - successful

To Reproduce
Steps to reproduce the behavior:

1. Set CFE_PLATFORM_EVS_DEFAULT_TYPE_FLAG to 0xF
2. Build unit tests, run cfe-core_evs_UT, observe failure

Expected behavior
Test should pass with debug events enabled (shouldn't care).

Code snips

cFE/fsw/cfe-core/unit-test/evs_UT.c

Lines 2670 to 2688 in dc3d62b

	/* Test successful log data file write */
	UT_InitData();
	UT_EVS_DoDispatchCheckEvents(&PktBuf.writelogdatacmd, sizeof(PktBuf.writelogdatacmd),
	UT_TPID_CFE_EVS_CMD_WRITE_LOG_DATA_FILE_CC,
	&UT_EVS_EventBuf);
	UT_Report(__FILE__, __LINE__,
	UT_EVS_EventBuf.EventID == 0xFFFF,
	"CFE_EVS_WriteLogDataFileCmd",
	"Write log data - successful");
	/* Test successfully setting the logging mode */
	UT_InitData();
	UT_EVS_DoDispatchCheckEvents(&PktBuf.modecmd, sizeof(PktBuf.modecmd),
	UT_TPID_CFE_EVS_CMD_SET_LOG_MODE_CC,
	&UT_EVS_EventBuf);
	UT_Report(__FILE__, __LINE__,
	UT_EVS_EventBuf.EventID == 0xFFFF,
	"CFE_EVS_SetLogModeCmd",
	"Set logging mode - successful");

System observed on:

• Hardware: cFS Dev Server
• OS: Ubuntu 18.04
• Versions: 6.8.0-rc1+dev129

Additional context
N/A

Reporter Info
Jacob Hageman - NASA/GSFC

[skliper]

I haven't dug into the logic, but I suspect it's considering no events a success. This doesn't seem very resilient, check should be that the dispatch logic was followed as expected not zero events. If all events were disabled, this would always pass.