-
Notifications
You must be signed in to change notification settings - Fork 2k
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
static_tests: Add test for Rust code formatting rules #20886
Conversation
Hm, there is a holdup: The static tests are run in a different container than riotbuild, and that doesn't have Rust :-/ Should I just add it there? |
I would say yes. Is there an easy way to measure the extra time this will cost per static-test run? |
Hard to tell w/o knowing GitHub's container cache strategy, but I think that the time to fetch the container (10s in this case) will grow proportionally with its size in some approximation. |
Lets just do it. How bad can it be? 🙈 |
This is needed for the static tests introduced in [20886]; no need for nightly or target specific tools. [20886]: RIOT-OS/RIOT#20886
This is needed for the static tests introduced in [20886]; no need for nightly or target specific tools. [20886]: RIOT-OS/RIOT#20886
This got shut down by GitHub trying to do NLP and failing miserably, closing this through RIOT-OS/riotdocker#254 … and since I force-pushed to make it trigger again, I can't reopen either. Anyone ever heard of Forgejo? Updated PR incoming. |
Contribution description
It is common for projects with Rust code to just enforce the code style suggested by Rust.
This adds a check to the static tests, and
Testing procedure
This PR should fail with a sensible message on the first run, and be green when I push the second commit fixing all the formatting errors (through the provided command).
Issues/PRs references
Thanks @Teufelchen1 for spotting the formatting errors.