You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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?
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.
Lines such as
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
The text was updated successfully, but these errors were encountered: