Fix #, test

[Cameron-Sykes]

Describe the contribution
A clear and concise description of what the contribution is.

• Include explicitly what issue it addresses [e.g. Fixes #X]

Testing performed
Steps taken to test the contribution:

1. Build steps '...'
2. Execution steps '...'

Expected behavior changes
A clear and concise description of how this contribution will change behavior and level of impact.

• API Change: xxx (if applicable)
• Behavior Change: xxx (if applicable)
• Or no impact to behavior

System(s) tested on

• Hardware: [e.g. PC, SP0, MCP750]
• OS: [e.g. Ubuntu 18.04, RTEMS 4.11, VxWorks 6.9]
• Versions: [e.g. cFE 6.6, OSAL 4.2, PSP 1.3 for mcp750, any related apps or tools]

Additional context
Add any other context about the contribution here.

Third party code
If included, identify any third party code and provide text file of license

Contributor Info - All information REQUIRED for consideration of pull request
Full name and company/organization/center of all contributors ("Personal" if individual work)

• Note CLA's apply to software contributions.

For members of the cFS Team
Click the Preview tab and select the pull request template corresponding to the type of change you are submitting:

• Comment/Documentation Change
• Flight Software Code Change
• Workflows Change