Hello.
On 08/08/16 16:22, Carsten Haitzler (The Rasterman) wrote:
> On Mon, 8 Aug 2016 16:08:58 +0200 Stefan Schmidt <ste...@osg.samsung.com>
> said:
>
>> Hello.
>>
>> On 08/08/16 15:35, Carsten Haitzler (The Rasterman) wrote:
>>> On Mon, 8 Aug 2016 14:31:06 +0200 Stefan Schmidt <ste...@osg.samsung.com>
>>> said:
>>>
>>>> Hello.
>>>>
>>>> Summary:
>>>> o Coverity updated their analyzer side so we got a bunch new defects
>>>> o On the other hand a lot of them got fixed already :)
>>>> o Mike, yes there is a new one in E. Build is from 04.08 :)
>>>>
>>>>
>>>> This should give everyone an overview over what has happened in the last
>>>> week on the QA front. The numbers in parentheses reflect the values from
>>>> last week to give you a trend.
>>>>
>>>> CI:
>>>> o Overall build statistic: 3.10% (5.04%) failed.
>>>> https://build.enlightenment.org/
>>>>
>>>> Unit tests:
>>>> o 841 (839) unit tests for efl
>>>>
>>>> Coverage:
>>>> o EFL total coverage is at N/A (N/A) lines, N/A (N/A) functions and N/A
>>>> (N/A) branches
>>>> https://build.enlightenment.org/view/Test%20Coverage/
>>>
>>> WAT? N/A?
>>
>>
>> I had to disable the lcov-check run on Jenkins as it was getting stuck
>> during the build. I also had OOM problems with it before. A bit hard to
>> debug as locally this works fine for me. Need to have another look.
>
> OOM? wow.
Indeed. I was surprised as well. I never had it locally though. Maybe I
need to try harder or get a better handle on debugging this remotely on
Jenkins.
>
>>>> Coverity:
>>>> o EFL: Outstanding defects 90 (74) with a density of 0.08 (0.07)
>>>
>>> when is the next coverity scan possible? 1 week from now?
>>
>> 11.08
>
> thursday. hmmm.
>
>> I tried to produce a fresh run before I sent this mail and it told me
>> the following when uploading:
>>
>> 01:28:56.612 {"message":"The build submission quota for this project has
>> been reached. Next submission permitted on or after 2016-Aug-11 10:58 AM
>> UTC"}
>
> yeah. we're big. we have a limit on frequency of runs. i just didnt know when
> the next is.
>
> my suggestion is wait for the next run to collect coverity stats before
> release
> then release right after that. (1.18). sound good? it means coverity info can
> be included up-to-date in the release. it's soon enough...
Hmm, not sure I agree here. Waiting two days with the release just to
have updated coverity stats? So far we have not even mentioned them in
the release notes. Given the timezone this machine sits in this would
basically mean I would only be able to do the release on Friday.
regards
Stefan Schmidt
------------------------------------------------------------------------------
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
