Skip to content
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

Verbosity of the tool #26

Open
aphecetche opened this issue Jan 21, 2018 · 2 comments
Open

Verbosity of the tool #26

aphecetche opened this issue Jan 21, 2018 · 2 comments

Comments

@aphecetche
Copy link

Hi,

Just trying to get my feet wet with the o2codechecker ...

At first I'd like to use it on a single file/class where I've put on purpose a member name starting with "f' instead of "m", and I find the output of the tool quite verbose. Is there a way to tame the verbosity and get the output more "to the point" ? Or is it that the command I'm using is not correct ?

Thanks,

[o2codechecker/latest-release] ~/alice/o2-dev/alo/mapping/impl2 %> run_O2CodeChecker.py -clang-tidy-binary $(which O2codecheck) -p $HOME/alice/sw/BUILD/alo-latest-clion/alo "-checks=-*,alice*" segmentationImpl2.*
['/Users/laurent/alice/sw/osx_x86-64/o2codechecker/master-2/bin/O2codecheck', '-list-checks']
Enabled checks:
    aliceO2-SizeOf
    aliceO2-member-name
    aliceO2-namespace-naming


/Users/laurent/alice/sw/osx_x86-64/o2codechecker/master-2/bin/O2codecheck -header-filter=^/Users/laurent/alice/sw/BUILD/alo-latest-clion/alo/.* -checks=-*,alice* -p=/Users/laurent/alice/sw/BUILD/alo-latest-clion/alo /Users/laurent/alice/o2-dev/alo/mapping/impl2/segmentationImpl2.cxx
/Users/laurent/alice/sw/osx_x86-64/o2codechecker/master-2/bin/O2codecheck -header-filter=^/Users/laurent/alice/sw/BUILD/alo-latest-clion/alo/.* -checks=-*,alice* -p=/Users/laurent/alice/sw/BUILD/alo-latest-clion/alo /Users/laurent/alice/o2-dev/alo/mapping/impl2/segmentationImpl2.cxx
229 warnings and 1 error generated.
Error while processing /Users/laurent/alice/o2-dev/alo/mapping/impl2/segmentationImpl2.cxx.
229 warnings and 1 error generated.
Error while processing /Users/laurent/alice/o2-dev/alo/mapping/impl2/segmentationImpl2.cxx.
458 warnings and 2 errors generated.
Error while processing /Users/laurent/alice/o2-dev/alo/mapping/impl2/segmentationImpl2.cxx.
/Users/laurent/alice/o2-dev/alo/mapping/impl2/segmentationImpl2.h:84:9: error: field declaration 'fWrong' does not match naming rule [aliceO2-member-name]
    int fWrong;
        ^
        mWrong
/Users/laurent/alice/o2-dev/alo/mapping/impl2/segmentationImpl2.h:84:9: error: field declaration 'fWrong' does not match naming rule [aliceO2-member-name]
    int fWrong;
        ^
        mWrong
Suppressed 458 warnings (458 in non-user code).
Use -header-filter=.* to display errors from all non-system headers. Use -system-headers to display errors from system headers as well.
458 warnings and 2 errors generated.
Error while processing /Users/laurent/alice/o2-dev/alo/mapping/impl2/segmentationImpl2.cxx.
/Users/laurent/alice/o2-dev/alo/mapping/impl2/segmentationImpl2.h:84:9: error: field declaration 'fWrong' does not match naming rule [aliceO2-member-name]
    int fWrong;
        ^
        mWrong
/Users/laurent/alice/o2-dev/alo/mapping/impl2/segmentationImpl2.h:84:9: error: field declaration 'fWrong' does not match naming rule [aliceO2-member-name]
    int fWrong;
        ^
        mWrong
Suppressed 458 warnings (458 in non-user code).
Use -header-filter=.* to display errors from all non-system headers. Use -system-headers to display errors from system headers as well.
@ktf
Copy link
Member

ktf commented Jan 22, 2018

Not sure about the verbosity, but you can use the -fix option to fix all of them and not worry about the verbose output anymore. ;-)

@aphecetche
Copy link
Author

yep, that's of course an option ;-) But I would prefer to avoid it as I'd prefer to see the warnings (at least in the beginning that makes it easier to teach myself the new rules).

By the way the issue is not related to the Alice specific checks. Using any of the other clang-tidy checks gives the same annoying behaviour (having 4 times the same message).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants