Thanks. According to Chris (one of emails below), change is not immediate. But after looking at defined components in more detail, I noticed that there is already ignore for java api:
.*/vpp-api/java/.*/target/.* And if you look at the defect, e.g.: /build-root/build-vpp_debug-native/vpp/vpp-api/java/jvpp-core/target/io/fd/vpp/jvpp/core/dto/VnetSummaryStatsReply.java They are classified as VPP API (generated) : .*/build-root/.*/vpp-api/.* Which also match VnetSummaryStatsReply.java. So it looks like that java exclude should go higher on the list of components. Regards, Marek From: Dave Barach (dbarach) Sent: 30 stycznia 2017 14:15 To: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <mgrad...@cisco.com>; Luke, Chris <chris_l...@comcast.com>; vpp-dev@lists.fd.io; hc2...@lists.fd.io Cc: Damjan Marion (damarion) <damar...@cisco.com> Subject: RE: Coverity warnings in generated java files Done... Thanks... Dave From: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) Sent: Monday, January 30, 2017 7:34 AM To: Luke, Chris <chris_l...@comcast.com<mailto:chris_l...@comcast.com>>; vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>; hc2...@lists.fd.io<mailto:hc2...@lists.fd.io> Cc: Dave Barach (dbarach) <dbar...@cisco.com<mailto:dbar...@cisco.com>>; Damjan Marion (damarion) <damar...@cisco.com<mailto:damar...@cisco.com>> Subject: RE: Coverity warnings in generated java files Luke (or sb who has admin rights), could you please update the rule? Regards, Marek From: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) Sent: 24 stycznia 2017 18:02 To: Luke, Chris <chris_l...@comcast.com<mailto:chris_l...@comcast.com>>; vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>; hc2...@lists.fd.io<mailto:hc2...@lists.fd.io> Cc: Dave Barach (dbarach) <dbar...@cisco.com<mailto:dbar...@cisco.com>>; Damjan Marion (damarion) <damar...@cisco.com<mailto:damar...@cisco.com>> Subject: RE: Coverity warnings in generated java files I found following rule .*/build-root/.*/vpp-api/java/jvpp-core/.* I think it should be .*/build-root/.*/vpp-api/java/.* Regards, Marek From: hc2vpp-boun...@lists.fd.io<mailto:hc2vpp-boun...@lists.fd.io> [mailto:hc2vpp-boun...@lists.fd.io] On Behalf Of Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) Sent: 17 stycznia 2017 11:46 To: Luke, Chris <chris_l...@comcast.com<mailto:chris_l...@comcast.com>>; vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>; hc2...@lists.fd.io<mailto:hc2...@lists.fd.io> Cc: Dave Barach (dbarach) <dbar...@cisco.com<mailto:dbar...@cisco.com>>; Damjan Marion (damarion) <damar...@cisco.com<mailto:damar...@cisco.com>> Subject: Re: [hc2vpp] Coverity warnings in generated java files Hi, It looks like coverity is applied to debug build, could you please to update path to use build-vpp_debug-native ? Thanks, Marek From: Luke, Chris [mailto:chris_l...@comcast.com] Sent: 12 stycznia 2017 14:54 To: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <mgrad...@cisco.com<mailto:mgrad...@cisco.com>>; vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>; hc2...@lists.fd.io<mailto:hc2...@lists.fd.io> Cc: Damjan Marion (damarion) <damar...@cisco.com<mailto:damar...@cisco.com>>; Dave Barach (dbarach) <dbar...@cisco.com<mailto:dbar...@cisco.com>> Subject: RE: Coverity warnings in generated java files Done. The Coverity web-ui makes this simple for admins to do. Reference for other Coverity admins: On the "Analysis settings" tab, add a "component" whose path is a regexp and you check the "ignore in analysis" box. The list is ordered; drag the new item into the appropriate place and then save. It sometimes take a few moments for the change to be reflected; it reclassifies all the currently known defects based on the regexps of the configured components. Chris. From: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) [mailto:mgrad...@cisco.com] Sent: Tuesday, January 10, 2017 11:33 AM To: vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>; hc2...@lists.fd.io<mailto:hc2...@lists.fd.io> Cc: Damjan Marion (damarion) <damar...@cisco.com<mailto:damar...@cisco.com>>; Luke, Chris <chris_l...@cable.comcast.com<mailto:chris_l...@cable.comcast.com>>; Dave Barach (dbarach) <dbar...@cisco.com<mailto:dbar...@cisco.com>> Subject: Coverity warnings in generated java files Hi, do you know is there a way to exclude java file / code line from coverity analysis, by adding some code annotation? In case it is not possible (or as a temporary workaround), here is a list of directories, that need exclusion: ./build-vpp-native/vpp/vpp-api/java/jvpp-acl/target/ ./build-vpp-native/vpp/vpp-api/java/jvpp-core/target/ ./build-vpp-native/vpp/vpp-api/java/jvpp-ioamexport/target/ ./build-vpp-native/vpp/vpp-api/java/jvpp-snat/target/ ./build-vpp-native/vpp/vpp-api/java/jvpp-ioamtrace/target/ ./build-vpp-native/vpp/vpp-api/java/jvpp-ioampot/target/ So we need rule of this kind: ./build-vpp-native/vpp/vpp-api/java/*/target/ Regards, Marek
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
