cFS Integration candidate: Caelum-rc4+dev9

[astrogeco]

Checklist (Please check before submitting)

• I reviewed the Contributing Guide.
• I signed and emailed the appropriate Contributor License Agreement to [email protected] and copied [email protected].

Describe the contribution

Combines

nasa/osal#1251
nasa/cFE#2098
nasa/PSP#343

Including

cFE

nasa/cFE#2078, Adds truncation warning suppression flags

nasa/cFE#2094, Doc deploy from local workflow on main-branch push

nasa/cFE#2088, Add support for fractional seconds in epoch

nasa/cFE#2044, Remove redundant word in App Developers Guide

nasa/cFE#2099, UT updates for alternate time configuration

**RTEMS 6 Support

nasa/cFE#2097, update rtems toolchain files

nasa/osal#1250, add os-impl-no-select.c for RTEMS

nasa/PSP#339, Update RTEMS CMake Platform File

PSP

nasa/PSP#341, Add cpu affinity example

Fix Broken CodeQL Workflow Reference

nasa/PSP#337

nasa/osal#1249

nasa/sample_lib#82

nasa/sample_app#173

nasa/sch_lab#113

nasa/ci_lab#109

nasa/to_lab#120

nasa/elf2cfetbl#110

nasa/tblCRCTool#68

nasa/cFS-GroundSystem#214

Testing performed

See PRs

Expected behavior changes
See PRs

System(s) tested on
Ubuntu RTEMS

Additional context
None

Contributor Info - All information REQUIRED for consideration of pull request
@astrogeco
@chillfig
@skliper
@jonathan-brandenburg-metecs
@acudmore
@HugoValente11

[astrogeco]

@skliper I'm struggling with the documentation workflow. The installs were failing under Ubuntu 18.04 (see https://github.com/nasa/cFS/runs/6291462767?check_suite_focus=true)

I upgraded the workflows to ubuntu 20.04 but now I'm getting some LateX Errors on the users guide and
https://github.com/nasa/cFS/runs/6291868798?check_suite_focus=true and mission doc

[skliper]

@astrogeco the initial failure referenced just looks like a temporary communications error, can you just rerun and see if it'll work? Updating distros shouldn't be required.

[astrogeco]

@astrogeco the initial failure referenced just looks like a temporary communications error, can you just rerun and see if it'll work? Updating distros shouldn't be required.

tried re-running with no luck, found some forums about this being down frequently

[skliper]

I'd suggest just waiting until it's working again vs adding additional work arounds in our flow. Not sure if this is the case here, but any additional/alternative repo usage is just another security risk. Maybe just keep it simple?

[astrogeco]

I'd suggest just waiting until it's working again vs adding additional work arounds in our flow. Not sure if this is the case here, but any additional/alternative repo usage is just another security risk. Maybe just keep it simple?

Agreed, I'd rather bump up to 20.04 instead of a third party PPA. It's been failing for over a day though so I wonder if the old archive is getting deprecated.