Re: [Xen-devel] Make coverity results public

[Julien Grall <julien.grall@xxxxxxxxx>]

(sorry for the formatting)

On Wed, 28 Mar 2018, 21:48 George Dunlap, <george.dunlap@xxxxxxxxxx> wrote:

On 03/28/2018 02:33 PM, Roger Pau Monné wrote:
> Hello,
>
> According to the contribution guidelines document [0] the coverity
> database of issues is private, which makes it hard for new people to
> see issues. IMO it makes no sense to keep the result private anymore:
>
>  - They have been audited for plenty of time by different people
>    that currently has access to the database.
>  - Anyone can reproduce the same results by forking Xen on github and
>    sending a build to coverity for analysis AFAICT.
>
> On the plus side, having the database open would allow us the
> following:
>
>  - Coverity reports could be sent to xen-devel, so anyone could pick
>    and fix new issues.
>  - Newcomers could use coverity in order to find small size tasks to
>    work on.

In general, +1 from me.  But Stefano, was there some special
circumstance for the ARM Coverity runs?

We don't control what is tested on the ARM coverity. This was setup on a testing branch by EPAM, so they are putting their patches and update manually.

If we want to open that coverity then we need to track staging and have automatic push.

Otherwise it will be near to impossible to know if the failure is because of staging or their patches.

Cheers,

 -George

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel