RE: coverity scan report

[Santhosh Edukulla <sa...@citrix.com>]

All,

It seems the difference in densities is because, dashboard and project overview report are using different bases i.e., "total lines of code"  and "loc in selected components" as below:

1. ((1629 OutStanding Defects)/(1,045,850 Total Lines of Code)) * 1000  = 1.56

2. ((1,629 OutStanding Defects)/(434,607 Lines of Code in selected Components))*1000 = 3.75

I have now got it corrected,  both dashboard and project overview now displays the same densities. 

Regards,
Santhosh

________________________________________
From: Santhosh Edukulla
Sent: Tuesday, June 17, 2014 10:21 AM
To: dev@cloudstack.apache.org
Subject: RE: coverity scan report

As well, there are two defect densities displayed at links below. Is the first one, an overall\all projects density metric, and other for individual cloudstack project ?

https://scan.coverity.com/dashboard
https://scan.coverity.com/projects/943?tab=overview

Regards,
Santhosh
________________________________________
From: Rajani Karuturi [Rajani.Karuturi@citrix.com]
Sent: Tuesday, June 17, 2014 5:26 AM
To: cloudstack
Subject: coverity scan report

Is there any change in the coverity scan project settings??
the dashboard says Last Analyzed on Jun 09, 2014 https://scan.coverity.com/projects/943?tab=overview

while jenkins job is successful http://jenkins.buildacloud.org/job/cloudstack-master-twiceweekly-coverity/lastBuild/


~Rajani