My idea was to rule them out during PR reviewal, be it false or positive
issues, rather than $x days/weeks/months later :-)
--
Erik
On Tue, Jan 26, 2016 at 9:23 AM, Daan Hoogland
wrote:
> please Erik, if you have any inspiration to this cause and goal...
>
> I'm game if at all feasible. Don't
please Erik, if you have any inspiration to this cause and goal...
I'm game if at all feasible. Don't forget we have 6000+ outstanding defects
as far as coverity is concerned. Not all of those are genuine positives,
btw.
On Mon, Jan 25, 2016 at 7:16 PM, Erik Weber wrote:
> Slighly off topic, bu
Slighly off topic, but could coverity be integrated with our PR workflow?
Erik
Den mandag 25. januar 2016 skrev Daan Hoogland
følgende:
> Did a quick scan of the reported new issues. All four are older then the
> last report. Anybody feels like taking ownership?
>
> On Mon, Jan 25, 2016 at 4:13
Did a quick scan of the reported new issues. All four are older then the
last report. Anybody feels like taking ownership?
On Mon, Jan 25, 2016 at 4:13 PM, wrote:
>
> Hi,
>
> Please find the latest report on new defect(s) introduced to cloudstack
> found with Coverity Scan.
>
> 4 new defect(s) i
On Tue, Nov 24, 2015 at 9:11 AM, Daan Hoogland
wrote:
> I think we all need to triage this. Not just PR authors.
>
> On Tue, Nov 24, 2015 at 7:46 AM, Rajani Karuturi <
> rajani.karut...@citrix.com> wrote:
>
>> *98* New defects.
>> All the latest merged PR authors, can you please go through the li
I don’t know if it can be done (especially with free coverity integration, I
don’t think its possible.)
~ Rajani
-Original Message-
From: Erik Weber
Reply-To: "dev@cloudstack.apache.org"
Date: Tuesday, 24 November 2015 at 12:48 PM
To: dev
Subject: Re: New Defects r
I think we all need to triage this. Not just PR authors.
On Tue, Nov 24, 2015 at 7:46 AM, Rajani Karuturi wrote:
> *98* New defects.
> All the latest merged PR authors, can you please go through the list of
> new defects?
>
> ~ Rajani
>
>
>
>
>
>
>
>
> -Original Message-
> From: "scan-ad
On Tue, Nov 24, 2015 at 7:46 AM, Rajani Karuturi wrote:
> *98* New defects.
> All the latest merged PR authors, can you please go through the list of
> new defects?
>
Could we integrate it with travis and/or jenkins and get it reported once
submitted as PR?
https://scan.coverity.com/travis_ci
h
*98* New defects.
All the latest merged PR authors, can you please go through the list of new
defects?
~ Rajani
-Original Message-
From: "scan-ad...@coverity.com"
Reply-To: "dev@cloudstack.apache.org"
Date: Monday, 23 November 2015 at 11:44 PM
To: "dev@cloudstack.apache.org"
S
Guys `n' dolls,
good and bad news here ; the good first
590 issues were fixed and only 47 newly discovered.
bad news :
in spite of 590 fixed issues 47 new ones were introduced. So anybody
that did any checkin over the last month or so, please have a look and
see if these are false positives or
H fellow devs,
We got a bad report here: 5 new, 2 fixed.
On Mon, Dec 15, 2014 at 1:08 PM, wrote:
>
> Hi,
>
> Please find the latest report on new defect(s) introduced to cloudstack found
> with Coverity Scan.
>
> 5 new defect(s) introduced to cloudstack found with Coverity Scan.
> 2 defect(s),
it will freeze in the Sahara soon, won't it?
Also, does our coverity license/account allow for it?
On Fri, Sep 5, 2014 at 3:09 PM, sebgoa wrote:
>
> On Sep 5, 2014, at 3:00 PM, Daan Hoogland wrote:
>
> > H,
> >
> > We are not anywhere near perfect (or arguably good) but according to
> > cover
On Sep 5, 2014, at 3:00 PM, Daan Hoogland wrote:
> H,
>
> We are not anywhere near perfect (or arguably good) but according to
> coverity we are improving:
>
> *3.17*
> Defect Density
> However:
> Defect changes since previous build dated Aug 29, 2014
> *8* Newly detected
> *0* Eliminated
>
05, 2014 9:00 AM
To: dev
Subject: Re: New Defects reported by Coverity Scan for cloudstack
H,
We are not anywhere near perfect (or arguably good) but according to
coverity we are improving:
*3.17*
Defect Density
However:
Defect changes since previous build dated Aug 29, 2014
*8* Newly
H,
We are not anywhere near perfect (or arguably good) but according to
coverity we are improving:
*3.17*
Defect Density
However:
Defect changes since previous build dated Aug 29, 2014
*8* Newly detected
*0* Eliminated
and Defects by status for current build
*2,961*Total defects
*1,39
l
Cc: ; Santhosh Edukulla
Subject: Re: New Defects reported by Coverity Scan for cloudstack
Hey Ritu,
Thanks! Could you post the patch as a separate review? That way it will be a
lot easier for me to merge the changes.
The easiest way to do it is to base the new patch on the current state of the
ma
Hey Ritu,
Thanks! Could you post the patch as a separate review? That way it will be a
lot easier for me to merge the changes.
The easiest way to do it is to base the new patch on the current state of the
master branch.
Cheers,
Hugo
On 29 jul. 2014, at 22:32, Ritu Sabharwal wrote:
> Hi Hu
Hi Hugo,
I have fixed the reported findings and posted the patch on review board.
Thanks & Regards,
Ritu S.
From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
Sent: Tuesday, July 29, 2014 6:41 AM
To: Ritu Sabharwal
Cc: ; Santhosh Edukulla
Subject: Fwd: New Defects reported by C
ted code.
>>
>> Animesh
>>
>>> -Original Message-
>>> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
>>> Sent: Wednesday, June 04, 2014 3:56 PM
>>> To: dev@cloudstack.apache.org
>>> Subject: RE: New Defects
generated code.
>>
>> Animesh
>>
>>> -Original Message-
>>> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
>>> Sent: Wednesday, June 04, 2014 3:56 PM
>>> To: dev@cloudstack.apache.org
>>> Subject: RE: New Defe
about 3.4
> after excluding AWSAPI generated code.
>
> Animesh
>
>> -Original Message-
>> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
>> Sent: Wednesday, June 04, 2014 3:56 PM
>> To: dev@cloudstack.apache.org
>> Subject: RE: N
haturv...@citrix.com]
> Sent: Wednesday, June 04, 2014 3:56 PM
> To: dev@cloudstack.apache.org
> Subject: RE: New Defects reported by Coverity Scan for cloudstack
>
> Rajani
>
> Thanks for bringing this up, I looked at the analysis settings and I think the
> pattern to exclude aws c
> -Original Message-
> From: Rajani Karuturi [mailto:rajani.karut...@citrix.com]
> Sent: Monday, June 02, 2014 11:48 PM
> To: dev
> Subject: Re: New Defects reported by Coverity Scan for cloudstack
>
> These are the approximate number of defects reported by coverity from
These are the approximate number of defects reported by coverity from the
generated code.
> /awsapi/src/com/amazon/ec2 -> around 4300
> /awsapi/src/com/amazon/s3 -> around 350
total defects -> around 6500
~Rajani
On 02-Jun-2014, at 4:57 pm, Rajani Karuturi wrote:
> Hi Hugo,
>
> awsapi-g
Hi Hugo,
awsapi-generated-code is excluded for the project but I still see issues
reported in them.
For example for file src/com/amazon/ec2/DeleteTagsResponseType.java
Can you check the file exclude pattern? I think .* is missing
(awsapi/src/com/amazon/.*)
Fixing this might give us a bette
Hugo
Can you share the latest results? How can I get access to the reports?
Animesh
> -Original Message-
> From: Hugo Trippaers [mailto:trip...@gmail.com]
> Sent: Friday, November 29, 2013 7:58 AM
> To: dev@cloudstack.apache.org
> Subject: Fwd: New Defects reported by Coverity Scan for c
26 matches
Mail list logo
