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

Config file not applied #3384

Closed
LesserBabka opened this issue Jul 21, 2021 · 0 comments · Fixed by #3385
Closed

Config file not applied #3384

LesserBabka opened this issue Jul 21, 2021 · 0 comments · Fixed by #3385
Labels
analyzer 📈 Related to the analyze commands (analysis driver) bug 🐛

Comments

@LesserBabka
Copy link

LesserBabka commented Jul 21, 2021

CodeChecker config file does not seem to be applied. I have created a json file according to documentation and help text, to configure my call to CodeChecker. However, regardless of what I put in there it does not seem to be applied.

CodeChecker analyzer version:

---------------------------------------------------------------
Kind                 | Version                                 
---------------------------------------------------------------
Base package version | 6.16.0                                  
Package build date   | 2021-06-10T12:34                        
Git commit ID (hash) | 8880695af939838b2e1e16b018c51ed66c6a5366
Git tag information  | 6.16                                    
---------------------------------------------------------------

Minimal config file (Note: I have also tried replacing "analyzer" with "analyze" as it says in the example config file in the documentation)

$ cat ccc.json 
{
  "analyzer": [
    "--disable=valist"
  ]
}

Invoke check
$ CodeChecker check -b "ninja" -o ./reports --config ccc.json

Info printout includes the disabled check (Full debug output, codechecker_config_file_debug_output.txt)

[INFO 2021-07-21 09:57] - Enabled checkers:
clangsa: ..., valist.CopyToSelf, valist.Uninitialized, valist.Unterminated, valist.ValistBase
...

Disabling the same checker group using the disable parameter works fine
CodeChecker check -b "ninja" -o ./reports -d=valist

This is just an example, I cannot see that any configuration from file seem to be applied.

@whisperity whisperity added the analyzer 📈 Related to the analyze commands (analysis driver) label Aug 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
analyzer 📈 Related to the analyze commands (analysis driver) bug 🐛
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants