From: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) [mailto:mgradzki@...]
Sent: Tuesday, January 10, 2017 11:33 AM
To: vpp-dev@...; hc2vpp@...
Cc: Damjan Marion (damarion) <damarion@...>; Luke, Chris <Chris_Luke@...>; Dave Barach (dbarach) <dbarach@...>
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

 

 

 

 

From: Luke, Chris [mailto:Chris_Luke@...]
Sent: 12 stycznia 2017 14:54
To: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <mgradzki@...>; vpp-dev@...; hc2vpp@...
Cc: Damjan Marion (damarion) <damarion@...>; Dave Barach (dbarach) <dbarach@...>
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: hc2vpp-bounces@... [mailto:hc2vpp-bounces@...] On Behalf Of Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco)
Sent: 17 stycznia 2017 11:46
To: Luke, Chris <Chris_Luke@...>; vpp-dev@...; hc2vpp@...
Cc: Dave Barach (dbarach) <dbarach@...>; Damjan Marion (damarion) <damarion@...>
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

 

 

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)
Sent: 24 stycznia 2017 18:02
To: Luke, Chris <Chris_Luke@...>; vpp-dev@...; hc2vpp@...
Cc: Dave Barach (dbarach) <dbarach@...>; Damjan Marion (damarion) <damarion@...>
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

 

 

Hi,

 

It looks like coverity is applied to debug build, could you please to update path to use build-vpp_debug-native ?

 

Thanks,

Marek

 

 

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)
Sent: Monday, January 30, 2017 7:34 AM
To: Luke, Chris <Chris_Luke@...>; vpp-dev@...; hc2vpp@...
Cc: Dave Barach (dbarach) <dbarach@...>; Damjan Marion (damarion) <damarion@...>
Subject: RE: Coverity warnings in generated java files

 

Luke (or sb who has admin rights), could you please update the rule?

 

Regards,

Marek

 

 

I found following rule

 

.*/build-root/.*/vpp-api/java/jvpp-core/.*

 

I think it should be

 

 

.*/build-root/.*/vpp-api/java/.*

 

Regards,

Marek

 

 

Hi,

 

It looks like coverity is applied to debug build, could you please to update path to use build-vpp_debug-native ?

 

Thanks,

Marek

 

 

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: Dave Barach (dbarach)
Sent: 30 stycznia 2017 14:15
To: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <mgradzki@...>; Luke, Chris <Chris_Luke@...>; vpp-dev@...; hc2vpp@...
Cc: Damjan Marion (damarion) <damarion@...>
Subject: RE: Coverity warnings in generated java files

 

Done... Thanks… Dave

 

 

Luke (or sb who has admin rights), could you please update the rule?

 

Regards,

Marek

 

 

I found following rule

 

.*/build-root/.*/vpp-api/java/jvpp-core/.*

 

I think it should be

 

 

.*/build-root/.*/vpp-api/java/.*

 

Regards,

Marek

 

 

Hi,

 

It looks like coverity is applied to debug build, could you please to update path to use build-vpp_debug-native ?

 

Thanks,

Marek

 

 

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.