---------- Forwarded message ----------
Date: Mon, 02 Nov 2015 14:47:39 -0800
From: scan-admin@coverity.com
Reply-To: Developer discussions 
To: csound-devel@lists.sourceforge.net
Subject: [Old-Cs-dev] Coverity Scan: Analysis completed for csound/csound


     Your request for analysis of csound/csound has been completed successfully.
     The results are available at https://scan.coverity.com/projects/csound-csound

     Analysis Summary:
        New defects found: 17
        Defects eliminated: 4

     If you have difficulty understading any defects, email us at scan-admin@coverity.com,
     or post your question to the Coverity Community
     at https://communities.coverity.com/community/scan-(open-source)/content


------------------------------------------------------------------------------
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I got a reply (over a month after sending in an email, but then I
think the company got bought and there was some transition happening):

[start quote]

Sorry for the late reply.
Actually the latest build of your project contains both C/C++ and Java
code, however we supported only one language at a time.
We have added support for multiple language.

We already added your build into queue for analysis and it should be
finish in next few hours.
Let us know if your build doesn¹t get processed by end of day.

[end quote]

It looks like Coverity will be running again now.  I think we should
find a way to turn off the Java scanning though as it is mostly
generated code.

On Tue, Nov 3, 2015 at 5:40 AM, jpff  wrote:
> ---------- Forwarded message ----------
> Date: Mon, 02 Nov 2015 14:47:39 -0800
> From: scan-admin@coverity.com
> Reply-To: Developer discussions 
> To: csound-devel@lists.sourceforge.net
> Subject: [Old-Cs-dev] Coverity Scan: Analysis completed for csound/csound
>
>
>     Your request for analysis of csound/csound has been completed
> successfully.
>     The results are available at
> https://scan.coverity.com/projects/csound-csound
>
>     Analysis Summary:
>        New defects found: 17
>        Defects eliminated: 4
>
>     If you have difficulty understading any defects, email us at
> scan-admin@coverity.com,
>     or post your question to the Coverity Community
>     at https://communities.coverity.com/community/scan-(open-source)/content
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net

Java code could be fairly easily ignored via a Component match:

.*interfaces/.*.java => ignore.

I could add it if you agree to it. We already have a match for the
generated cxx files.

On 3 November 2015 at 11:41, Steven Yi  wrote:
> I got a reply (over a month after sending in an email, but then I
> think the company got bought and there was some transition happening):
>
> [start quote]
>
> Sorry for the late reply.
> Actually the latest build of your project contains both C/C++ and Java
> code, however we supported only one language at a time.
> We have added support for multiple language.
>
> We already added your build into queue for analysis and it should be
> finish in next few hours.
> Let us know if your build doesn¹t get processed by end of day.
>
> [end quote]
>
> It looks like Coverity will be running again now.  I think we should
> find a way to turn off the Java scanning though as it is mostly
> generated code.
>
> On Tue, Nov 3, 2015 at 5:40 AM, jpff  wrote:
>> ---------- Forwarded message ----------
>> Date: Mon, 02 Nov 2015 14:47:39 -0800
>> From: scan-admin@coverity.com
>> Reply-To: Developer discussions 
>> To: csound-devel@lists.sourceforge.net
>> Subject: [Old-Cs-dev] Coverity Scan: Analysis completed for csound/csound
>>
>>
>>     Your request for analysis of csound/csound has been completed
>> successfully.
>>     The results are available at
>> https://scan.coverity.com/projects/csound-csound
>>
>>     Analysis Summary:
>>        New defects found: 17
>>        Defects eliminated: 4
>>
>>     If you have difficulty understading any defects, email us at
>> scan-admin@coverity.com,
>>     or post your question to the Coverity Community
>>     at https://communities.coverity.com/community/scan-(open-source)/content
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel



-- 

Saludos,

Hi Felipe,

Yes please do. I think those issues reported for those files are ones we can't do anything about (except report to SWIG project).

Thanks!
Steven

Done. It should refresh itself in 15 minutes.

On 3 November 2015 at 14:20, Steven Yi  wrote:
> Hi Felipe,
>
> Yes please do. I think those issues reported for those files are ones we
> can't do anything about (except report to SWIG project).
>
> Thanks!
> Steven
>
>
> On Tue, Nov 3, 2015, 9:52 AM Felipe Sateler  wrote:
>>
>> Java code could be fairly easily ignored via a Component match:
>>
>> .*interfaces/.*.java => ignore.
>>
>> I could add it if you agree to it. We already have a match for the
>> generated cxx files.
>>
>> On 3 November 2015 at 11:41, Steven Yi  wrote:
>> > I got a reply (over a month after sending in an email, but then I
>> > think the company got bought and there was some transition happening):
>> >
>> > [start quote]
>> >
>> > Sorry for the late reply.
>> > Actually the latest build of your project contains both C/C++ and Java
>> > code, however we supported only one language at a time.
>> > We have added support for multiple language.
>> >
>> > We already added your build into queue for analysis and it should be
>> > finish in next few hours.
>> > Let us know if your build doesn¹t get processed by end of day.
>> >
>> > [end quote]
>> >
>> > It looks like Coverity will be running again now.  I think we should
>> > find a way to turn off the Java scanning though as it is mostly
>> > generated code.
>> >
>> > On Tue, Nov 3, 2015 at 5:40 AM, jpff  wrote:
>> >> ---------- Forwarded message ----------
>> >> Date: Mon, 02 Nov 2015 14:47:39 -0800
>> >> From: scan-admin@coverity.com
>> >> Reply-To: Developer discussions 
>> >> To: csound-devel@lists.sourceforge.net
>> >> Subject: [Old-Cs-dev] Coverity Scan: Analysis completed for
>> >> csound/csound
>> >>
>> >>
>> >>     Your request for analysis of csound/csound has been completed
>> >> successfully.
>> >>     The results are available at
>> >> https://scan.coverity.com/projects/csound-csound
>> >>
>> >>     Analysis Summary:
>> >>        New defects found: 17
>> >>        Defects eliminated: 4
>> >>
>> >>     If you have difficulty understading any defects, email us at
>> >> scan-admin@coverity.com,
>> >>     or post your question to the Coverity Community
>> >>     at
>> >> https://communities.coverity.com/community/scan-(open-source)/content
>> >>
>> >>
>> >>
>> >> ------------------------------------------------------------------------------
>> >> _______________________________________________
>> >> Csound-devel mailing list
>> >> Csound-devel@lists.sourceforge.net
>> >> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
>>
>> --
>>
>> Saludos,
>> Felipe Sateler



-- 

Saludos,

Can it also mail the new list as well?

On Tue, 3 Nov 2015, Felipe Sateler wrote:

> Done. It should refresh itself in 15 minutes.

The list change is in develop but not in the coverity_scan branch.
Most likely coverity ran a new scan after their toolchain was updated.

On 3 November 2015 at 15:11, jpff  wrote:
> Can it also mail the new list as well?
>
>
> On Tue, 3 Nov 2015, Felipe Sateler wrote:
>
>> Done. It should refresh itself in 15 minutes.
>>
>



-- 

Saludos,

If we pull from develop to coverity_scan, the email list should be
taken care of then (if I understand correctly).

On Tue, Nov 3, 2015 at 10:13 AM, Felipe Sateler  wrote:
> The list change is in develop but not in the coverity_scan branch.
> Most likely coverity ran a new scan after their toolchain was updated.
>
> On 3 November 2015 at 15:11, jpff  wrote:
>> Can it also mail the new list as well?
>>
>>
>> On Tue, 3 Nov 2015, Felipe Sateler wrote:
>>
>>> Done. It should refresh itself in 15 minutes.
>>>
>>
>
>
>
> --
>
> Saludos,

Right, I think that would fix it.

BTW, in coverity scan the java errors are gone.

Saludos

On 3 November 2015 at 15:33, Steven Yi  wrote:
> If we pull from develop to coverity_scan, the email list should be
> taken care of then (if I understand correctly).
>
> On Tue, Nov 3, 2015 at 10:13 AM, Felipe Sateler  wrote:
>> The list change is in develop but not in the coverity_scan branch.
>> Most likely coverity ran a new scan after their toolchain was updated.
>>
>> On 3 November 2015 at 15:11, jpff  wrote:
>>> Can it also mail the new list as well?
>>>
>>>
>>> On Tue, 3 Nov 2015, Felipe Sateler wrote:
>>>
>>>> Done. It should refresh itself in 15 minutes.
>>>>
>>>
>>
>>
>>
>> --
>>
>> Saludos,
>> Felipe Sateler



-- 

Saludos,

Fantastic, thanks!

On Tue, Nov 3, 2015 at 10:34 AM, Felipe Sateler  wrote:
> Right, I think that would fix it.
>
> BTW, in coverity scan the java errors are gone.
>
> Saludos
>
> On 3 November 2015 at 15:33, Steven Yi  wrote:
>> If we pull from develop to coverity_scan, the email list should be
>> taken care of then (if I understand correctly).
>>
>> On Tue, Nov 3, 2015 at 10:13 AM, Felipe Sateler  wrote:
>>> The list change is in develop but not in the coverity_scan branch.
>>> Most likely coverity ran a new scan after their toolchain was updated.
>>>
>>> On 3 November 2015 at 15:11, jpff  wrote:
>>>> Can it also mail the new list as well?
>>>>
>>>>
>>>> On Tue, 3 Nov 2015, Felipe Sateler wrote:
>>>>
>>>>> Done. It should refresh itself in 15 minutes.
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Saludos,
>>> Felipe Sateler
>
>
>
> --
>
> Saludos,