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

Re-enable cppcheck #188

Closed
antocuni opened this issue Mar 26, 2021 · 8 comments · Fixed by #395
Closed

Re-enable cppcheck #188

antocuni opened this issue Mar 26, 2021 · 8 comments · Fixed by #395
Assignees

Comments

@antocuni
Copy link
Collaborator

In commit a91f8f9 (PR #187 ) I had to disable cppcheck, because it failed for no good reason.

I have no idea of what's happening, we should try again in some days/weeks and maybe re-enable it.

@thedrow
Copy link
Contributor

thedrow commented Jul 6, 2021

On CPPCheck 2.5 make cppcheck passes successfully.

This sounds like a weird bug that should be reported.

@antocuni
Copy link
Collaborator Author

antocuni commented Jul 8, 2021

do you feel like making a PR with cppcheck 2.5 and see if it passes the CI?

@thedrow
Copy link
Contributor

thedrow commented Jul 11, 2021

Since snap didn't properly work, we'd probably need to install it using Linuxbrew, I guess.
If that's OK with you, I can do it.

@antocuni
Copy link
Collaborator Author

Sorry for the late response. I don't know what is linuxbrew but as long as it works, that's ok with me :)

@thedrow
Copy link
Contributor

thedrow commented Sep 13, 2021

Homebrew for linux...

This was referenced Nov 16, 2021
fangerer added a commit that referenced this issue Nov 22, 2021
@fangerer
Copy link
Contributor

I've re-enabled cppcheck but using Ubuntu's version 1.90. I think this is better than nothing for now. We may think about moving to a newer version.

@fangerer fangerer self-assigned this Nov 22, 2021
@mattip
Copy link
Contributor

mattip commented Mar 2, 2023

cppcheck is failing CI, and I think it is not a good investment of the core team to fix it. Perhaps someone will step up at some point but I think we should disable it.

@mattip mattip reopened this Mar 2, 2023
@fangerer
Copy link
Contributor

fangerer commented Mar 2, 2023

@mattip I can already reproduce the problem in a virtual machine using nearly the same system and versions as GitHub's docker images. Maybe I can quickly find the problem but as you said, I won't invest too much time.

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

Successfully merging a pull request may close this issue.

4 participants