[riot-notifications] [RIOT-OS/RIOT] Revert "ci/vera++/rules/L004: add warning support" (#15813)
notifications at github.com
Wed Jan 20 10:52:55 CET 2021
The RIOT community cares a lot about code quality.
Therefore, before describing what your contribution is about, we would like
you to make sure that your modifications are compliant with the RIOT
coding conventions, see https://github.com/RIOT-OS/RIOT/wiki/Coding-conventions.
### Contribution description
This reverts commit f3a934a169abd299f593c9e60d6ef53da1d68dfb.
The original patch added a mechanism to avoid 2 consecutive calls to `vera++`, assuming we would be using both warnings and errors for line length.
Since #15793 removed the warning, this patch is required to go back to the vanilla use case of vera++ (only report, no prints).
This should fix the issue described in https://github.com/RIOT-OS/RIOT/pull/15793#issuecomment-762938130
Put here the description of your contribution:
- describe which part(s) of RIOT is (are) involved
- if it's a bug fix, describe the bug that it solves and how it is solved
- you can also give more information to reviewers about how to test your changes
### Testing procedure
Check `vera++` output with the bogus commit.
Details steps to test your contribution:
- which test/example to compile for which board and is there a 'test' command
- how to know that it was not working/available in master
- the expected success test output
### Issues/PRs references
Examples: Fixes #1234. See also #5678. Depends on PR #9876.
Please use keywords (e.g., fixes, resolve) with the links to the issues you
resolved, this way they will be automatically closed when your pull request
is merged. See https://help.github.com/articles/closing-issues-using-keywords/.
You can view, comment on, or merge this pull request online at:
-- Commit Summary --
* Revert "ci/vera++/rules/L004: add warning support"
* REMOVE ME!
-- File Changes --
M dist/tools/vera++/scripts/rules/L004.tcl (6)
M sys/net/gnrc/netif/gnrc_netif.c (2)
-- Patch Links --
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications