Coverity reports for test suite

[Amine Khaldi]

On 26/02/2017 21:53, Alexandre Julliard wrote:
> Nikolay Sivov <bunglehead at gmail.com> writes:
>
>> On 26.02.2017 21:32, Austin English wrote:
>>> On Sun, Feb 26, 2017 at 12:09 PM, Nikolay Sivov <bunglehead at gmail.com> wrote:
>>> FWIW, coverity supports putting issues into different components based
>>> on filename. It would be trivial to set up two different components
>>> for wine, e.g., 'wine' and 'wine-tests', then have wine/*/*/tests/* go
>>> to wine-tests, and wine/* to wine.
>>>
>>> For those not familiar with coverity administration, this would not
>>> require two separate builds, the results are separated when results
>>> are displayed on the server.
>>>
>> If it's possible to make them appear separately, so tests don't affect
>> our main reports, I see no harm in scanning tests too.
> There's probably no harm in getting a scan once, but I'm concerned that
> it would make people start "fixing" things that don't matter.
>
I have created a "wine-tests" component using .*/tests/.* and a "wine" 
component for the remaining. Please let me know if you need anything else.

Regards,
Amine.