-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix #808, ES API functional tests #1251
Fix #808, ES API functional tests #1251
Conversation
fba12f9
to
d73363d
Compare
40b86f9
to
8598638
Compare
ee17610
to
241aa93
Compare
241aa93
to
36498e2
Compare
CCB:2021-03-31 APPROVED
|
3eec2b8
to
f406692
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I pulled this to test it in conjunction with what I will propose for #1266, but found it does not build when using strict ID types.
CFE/CFS developers should ideally all set this option:
set(MISSION_RESOURCEID_MODE STRICT)
in your local global_build_options.cmake
file. It isn't set that way by default in order to be compatible for external users that may have existing code, but all framework code should build with this strict option set.
@@ -87,6 +87,9 @@ void UT_BSP_DoText(uint8 MessageType, const char *OutputMessage) | |||
Prefix = "N/A"; | |||
break; | |||
case UTASSERT_CASETYPE_BEGIN: | |||
CFE_ES_WriteToSysLog("\n"); | |||
CFE_ES_WriteToSysLog("\n"); | |||
CFE_ES_WriteToSysLog("\n"); /* add a bit of extra whitespace between tests */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be left out of this PR ideally - we can do something better in #1266
f406692
to
3127a90
Compare
07127ad
to
69c31d2
Compare
a9d75b8
to
d456d86
Compare
d456d86
to
de26ba4
Compare
de26ba4
to
bc963b8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I looked again, just a couple more minor updates ... it's close!
bc963b8
to
e8a43be
Compare
ES API functional tests
Combines: nasa/cFE#1284 nasa/osal#951 nasa/PSP#289 Including: nasa/cFE#1251 - ES Info API Functional test nasa/osal#931 - Scrub include guards nasa/osal#937 - Switch to use CLOCK_REALTIME nasa/osal#938 - specify shell name in ShellOutputToFile nasa/PSP#286 - use OSAL timebase for CFE timers nasa/PSP#282 - modularize the ram, port, and eenasa/psp#om access nasa/PSP#285 - add psp module to implement timebase
Describe the contribution
Fixes #808
New tests for the ES Info API's
Testing performed
This is the test
Expected behavior changes
none
Additional Context
Dependant on #1268
Addresses are only valid on VxWorks system so the tests for when that is true have not be run and verified.
System(s) tested on
Ubuntu 20.04
Contributor Info - All information REQUIRED for consideration of pull request
Alex Campbell GSFC