-
Notifications
You must be signed in to change notification settings - Fork 204
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
cFS-Caelum Review, CFS-41: EVS and FS #1294
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
astrogeco
force-pushed
the
caelum-code-review-cfs41
branch
2 times, most recently
from
April 11, 2021 17:56
68a627a
to
2a22870
Compare
astrogeco
force-pushed
the
caelum-code-review-cfs41
branch
from
April 11, 2021 18:00
2a22870
to
013f2fd
Compare
stashakk
reviewed
Apr 15, 2021
stashakk
reviewed
Apr 15, 2021
stashakk
reviewed
Apr 15, 2021
stashakk
reviewed
Apr 15, 2021
stashakk
reviewed
Apr 15, 2021
stashakk
reviewed
Apr 15, 2021
stashakk
reviewed
Apr 15, 2021
stashakk
reviewed
Apr 15, 2021
stashakk
reviewed
Apr 15, 2021
stashakk
reviewed
Apr 15, 2021
stashakk
reviewed
Apr 15, 2021
stashakk
reviewed
Apr 15, 2021
stashakk
reviewed
Apr 16, 2021
shjustice
reviewed
Apr 19, 2021
shjustice
reviewed
Apr 19, 2021
Review closed 4/19. For any future comments please open a new issue. |
skliper
changed the title
cFS-Caelum Review, EVS and FS, CFS-41
cFS-Caelum Review, CFS-41: EVS and FS
Apr 26, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This is a "bookkeeping" Pull Request meant for the cFS-Caelum Review code inspection (full-scale code review).
This PR is solely focused on "CFS-41". For more info see this readme
The Included files are
https://github.com/astrogeco/cFE/blob/caelum-code-review-cfs41/.gitignore
Objectives
This review starts on 04/12/2021 and ends on 04/16/2021.
Dispositions of findings is on 04/19/2021.
See also "The Power of 10" rules for safety-critical code. https://en.wikipedia.org/wiki/The_Power_of_10:_Rules_for_Developing_Safety-Critical_Code#:~:text=The%20Power%20of%2010%20Rules,to%20review%20or%20statically%20analyze
NOTE: Don't spend too much time over coding standard violations. The Static Code Analysis tool will enforce the coding standards. This code is developed by GSFC, so GSFC coding standards will be enforced for this code base.
Notes
If there's anything else that is observed as a repeated pattern, feel free to document as a general commen
There are several places that would trigger warnings with some common compilers/warning options. It would be nice to follow rule 10 in "The Power of 10".
Quick summary/references for currently enforced settings on the FSW
Compiler options (note -Wall and -Werror) -
cFE/cmake/sample_defs/arch_build_custom.cmake
Lines 28 to 37 in 0850b19
cppcheck -
cFE/.github/workflows/run_fsw_cppcheck.sh
Line 3 in 0850b19
CodeQL -
cFE/.github/workflows/codeql-build.yml
Lines 35 to 39 in 0850b19
CodeSonar - currently using default set for cFE, extending to JPL and MISRA is future work
For CodeQL and CodeSonar we don't eliminate all warnings, but we do analyze and disposition them all (plan to report dispositions as part of certification package)
This approach is compliant with the latest GSFC-582 standard (that is still going through review). Happy to discuss any additional settings that you have concerns about.