-
Notifications
You must be signed in to change notification settings - Fork 18
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
Added firmware static analysis to CI #165
Conversation
italo-sampaio
commented
Dec 14, 2023
•
edited
Loading
edited
- Merged old static analysis scripts into a single script
- Added static analysis to the CI on pushes to master
- Generated report is available for download on job summary
c9ea90d
to
363064b
Compare
Unified the signer and ui static analysis scripts into a single script is located under the more specific folder ledger/static-analysis. Also modified the directory of the generated reports to be under the ledger/static-analysis folder.
Added a new action to CI that runs static analysis on the firmware code. A failure in static analysis won't prevent the checks from passing, this is only informational at the moment. The generated reports are uploaded as a github artifact and can be analyzed offline.
363064b
to
5764341
Compare
An example run can be seen here. |
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.
LGTM!
As a question: I wonder whether it would make a difference using the arm clang toolchain we use for building firmware for the Nano S instead of the system /usr/bin/clang*.
Good question. The clang used for building the firmware is actually located at I'll update the script to also use the |
This makes it clear that we are using the same compiler for building the firmware and for static analysis
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.
LGTM!