You'll be glad to hear that it did, indeed, clear Coverity up. :)
Chris
-Original Message-
From: Benoit Ganne (bganne)
Sent: Tuesday, October 22, 2019 12:32
To: Luke, Chris ; Damjan Marion
Cc: vpp-dev@lists.fd.io
Subject: [EXTERNAL] RE: [vpp-dev] Coverity run FAILED as of 2019-10-
> Redefine the macro for the Coverity case, so Coverity doesn't complain. It
> just needs to be representative of the execution you expect to happen.
Ha yes good point, I was focusing on the ASSERT()...
Just did that: https://gerrit.fd.io/r/c/vpp/+/22936
Hopefully, Coverity should remove the false
AM
To: Damjan Marion
Cc: vpp-dev@lists.fd.io
Subject: [EXTERNAL] Re: [vpp-dev] Coverity run FAILED as of 2019-10-22 14:00:19
UTC
> you can try to wrap that assert with #ifndef __COVERITY__ ...
It is in a macro... I was thinking to do something like ASSERT(0 == (l) || (l)
<= vec_max_le
have to mark every
> single report as a false positive?
> >
> > Ben
> >
> >> -Original Message-
> >> From: vpp-dev@lists.fd.io On Behalf Of Noreply
> >> Jenkins
> >> Sent: mardi 22 octobre 2019 16:04
> >> To: vpp-dev@lists.fd.io
will that silence Coverity? Or do we have to mark every
> single report as a false positive?
>
> Ben
>
>> -Original Message-
>> From: vpp-dev@lists.fd.io On Behalf Of Noreply
>> Jenkins
>> Sent: mardi 22 octobre 2019 16:04
>> To: vpp-dev@lists.fd
Sent: mardi 22 octobre 2019 16:04
> To: vpp-dev@lists.fd.io; Ed Kern (ejk)
> Subject: [vpp-dev] Coverity run FAILED as of 2019-10-22 14:00:19 UTC
>
> Coverity run failed today.
>
> Current number of outstanding issues are 194
> Newly detected: 193
> Eliminated:
Coverity run failed today.
Current number of outstanding issues are 194
Newly detected: 193
Eliminated: 0
More details can be found at
https://scan.coverity.com/projects/fd-io-vpp/view_defects
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#14262)
