[zeromq-dev] CZMQ Coverity Scan

[Pieter Hintjens]

After my request was accepted, I could see the defects. Mostly memory leaks
on exceptional failures afaics. I already run CZMQ selftests under valgrind
to catch normal case memory leaks. So this is a great addition, nice!

On Sun, Oct 26, 2014 at 7:34 PM, Arnaud Kapp <kapp.arno at gmail.com> wrote:

> Hello,
>
> Yeah I just received your request.
> It's weird that you couldn't see the defect. While it's not public for
> unlogged user, it should be available to anyone who logged in.
>
> Project setting is this: "Project summary and defects are viewable in
> read-only mode by all users".
>
> On Sun, Oct 26, 2014 at 7:21 PM, Pieter Hintjens <ph at imatix.com> wrote:
>
>> Is there any way I can see the defects? I've requested access via that
>> site. Shame it's not open by default. The analysis should not be private.
>>
>> On Sun, Oct 26, 2014 at 6:26 PM, William Martin <
>> william.martin at power-lan.com> wrote:
>>
>>> Hi,
>>>
>>> It's looks like a very nice tool. I have create some issue based on the
>>> last report.
>>> https://scan.coverity.com/projects/3263/view_defects
>>>
>>> Thanks,
>>>
>>> On Sun, Oct 26, 2014 at 4:36 PM, Arnaud Kapp <kapp.arno at gmail.com>
>>> wrote:
>>>
>>>> Hello everyone,
>>>>
>>>> About a week ago I added CZMQ to Coverity Scan. For those who
>>>> don't know, it's a rather powerful static code analyzer.
>>>>
>>>> Coverity integrates well with Github. You should be able to see the
>>>> defects report here: https://scan.coverity.com/projects/3263 ,
>>>> provided that you are logged in (you can log-in with Github).
>>>>
>>>> Note that this build was manually uploaded. However,
>>>> Coverity supports Travis-Ci integration.
>>>>
>>>> The number of scan per week is limited (based on number of line of
>>>> code). This best pratice is to create a "coverity-scan" branch
>>>> and to push change regularly in order to trigger build.
>>>>
>>>> If you guys are interested I can come up with a PR that would
>>>> change the .travis.yml file and enable this behavior. We would
>>>> then have to push code to covery-scan branch from time to time.
>>>>
>>>> Then, if this proves useful, we could consider adding libzmq.
>>>>
>>>> Thanks,
>>>> _______________________________________________
>>>> zeromq-dev mailing list
>>>> zeromq-dev at lists.zeromq.org
>>>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>>>>
>>>
>>>
>>>
>>> --
>>> William MARTIN
>>> <http://www.power-lan.com/>
>>> 15 rue de la Noé des Yonnières
>>> 44850 Saint-Mars-du-Désert
>>>
>>> Email : william.martin at power-lan.com
>>> Tel : 02 85 52 12 74 - 06 49 23 59 68
>>> Fax : 02 85 52 13 72
>>>
>>> _______________________________________________
>>> zeromq-dev mailing list
>>> zeromq-dev at lists.zeromq.org
>>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>>>
>>>
>>
>> _______________________________________________
>> zeromq-dev mailing list
>> zeromq-dev at lists.zeromq.org
>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>>
>>
>
>
> --
> Kapp Arnaud - Xaqq
>
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20141026/5c6ca5e5/attachment.htm>