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.

Sign up for GitHub

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

Jump to bottom

Make Analyzing <> with clangsa CTU failed! non-fatal? #3946

Closed
LebedevRI opened this issue Jul 1, 2023 · 2 comments
Closed

Make Analyzing <> with clangsa CTU failed! non-fatal? #3946

LebedevRI opened this issue Jul 1, 2023 · 2 comments

Comments

@LebedevRI
Copy link
Contributor

I'm trying to enable CTU analysis on a project: https://github.com/darktable-org/rawspeed/actions/runs/5432405993/jobs/9879426261?pr=306

I rely on the fact that CodeChecker exits with non-zero exit status
if the bugs were found to fail the build (is there some nicer way to do that?)
but unfortunately if CTU analysis fails on some files,
that also results in non-zero exit status.

Additionally, --ctu-reanalyze-on-failure appears to be at deprecated,
even though there are clearly some CTU bugs...

Are there some recommendations on how to deal with this?
LebedevRI added a commit to LebedevRI/rawspeed that referenced this issue Jul 1, 2023
@LebedevRI
CodeChecker: try to pass --ctu-reanalyze-on-failure
fd9c3cc 
Otherwise, CTU failure is treated as a detected bug,
which is not what we want here.

Ericsson/codechecker#3946
@LebedevRI
Copy link
Contributor Author

Ok, --ctu-reanalyze-on-failure solves my problem:
https://github.com/darktable-org/rawspeed/actions/runs/5432566751/jobs/9879687726?pr=306

And looks like it's not actually deprecated as of #3823.

Thanks!

@LebedevRI LebedevRI closed this as not planned Won't fix, can't repro, duplicate, stale Jul 1, 2023
@bruntib
Copy link
Contributor

bruntib commented Jul 6, 2023

Hi,
It's good if you managed to workaround the problem with --ctu-reanalyze-on-failure. I just want to add that this PR might be related too: #3943.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@LebedevRI @bruntib