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

False positive Clang warnings on Linux from openssl output. #473

Closed
nuclearsandwich opened this issue Jun 12, 2020 · 3 comments · Fixed by #477
Closed

False positive Clang warnings on Linux from openssl output. #473

nuclearsandwich opened this issue Jun 12, 2020 · 3 comments · Fixed by #477
Assignees
Labels
bug Something isn't working

Comments

@nuclearsandwich
Copy link
Member

Lines such as

258: validate_local_permissions failed: (127) Failed to parse PKCS7 SMIME document: 281473198688096:error:21075075:PKCS7 routines:PKCS7_verify:certificate verify error:../crypto/pkcs7/pk7_smime.c:284:Verify error:self signed certificate

from cyclonedds security tests are matching the Jenkins analysis model regexp as a Clang warning.

Linux aarch64 debug #1234 is an example build exhibiting these warnings.

I've done some quick checking to see if there's a described format for clang messages in order to improve upstream's regexp and haven't found anything yet. Since our normal Linux builds use GCC we don't necessarily need to look at them for Clang errors so I'm going to open a PR that adds that parser only conditionally.

This is related to #316

@nuclearsandwich nuclearsandwich self-assigned this Jun 12, 2020
@dirk-thomas
Copy link
Member

Since our normal Linux builds use GCC we don't necessarily need to look at them for Clang errors so I'm going to open a PR that adds that parser only conditionally.

Since the option to use clang is a job parameter I am not sure how the parser could be conditional based on that parameter?

@nuclearsandwich
Copy link
Member Author

Since the option to use clang is a job parameter I am not sure how the parser could be conditional based on that parameter?

Yep I realized that trying to set it up. Doing it based on the job default would take away the ability to see clang warnings on regular Linux CI jobs. So I don't currently have a solution to this problem.

@dirk-thomas
Copy link
Member

Since we have to resolve #316 soon anyway in order to get the CI to be green I would say it is fine to wait for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants