-
Notifications
You must be signed in to change notification settings - Fork 11
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
ci: add static analysis action #137
Conversation
⚡ Static analysis result ⚡ 🔴 cppcheck found 6 issues! Click here to see details.espp/components/state_machine/include/magic_enum.hpp Lines 863 to 868 in 2712283
!Line: 863 - information: ValueFlow analysis is limited in constexpr_switch. Use --check-level=exhaustive if full analysis is wanted. [checkLevelNormal]
espp/components/state_machine/include/magic_enum.hpp Lines 731 to 736 in 2712283
!Line: 731 - style: Consider using std::accumulate algorithm instead of a raw loop. [useStlAlgorithm]
espp/components/state_machine/include/magic_enum.hpp Lines 741 to 746 in 2712283
!Line: 741 - style: Consider using std::accumulate algorithm instead of a raw loop. [useStlAlgorithm]
espp/components/state_machine/include/magic_enum.hpp Lines 255 to 260 in 2712283
!Line: 255 - style: Unused private function: 'case_insensitive::to_lower' [unusedPrivateFunction]
espp/components/state_machine/include/magic_enum.hpp Lines 730 to 735 in 2712283
!Line: 730 - information: Unmatched suppression: useStlAlgorithm [unmatchedSuppression]
espp/components/state_machine/include/magic_enum.hpp Lines 740 to 745 in 2712283
!Line: 740 - information: Unmatched suppression: useStlAlgorithm [unmatchedSuppression]
|
…enum external git submodule (also updated from magic enum 0.8 to 0.9.5 (master)
…um update the SA doesnt take more than a minute or two :) )
Description
state_machine/include/magic_enum.hpp
and replaced withexternal/magic_enum
submodule (which is included by thestate_machine
component)led
class related to semaphore access / management (found by SA)Motivation and Context
Helps ensure code quality by checking mistakes or bad programming practices. Also helps with code consistency.
How has this been tested?
Building the examples in this PR and checking that the static analysis PR action runs and produces meaningful output.
Screenshots (if appropriate, e.g. schematic, board, console logs, lab pictures):
Types of changes
Checklist:
Software
.github/workflows/build.yml
file to add my new test to the automated cloud build github action.