The Enlightenment build hasn't updated in over a week; the page says that
something is not configured. Are you aware of this?
On Mon, Mar 21, 2016 at 5:43 AM Stefan Schmidt
wrote:
> Hello.
>
> Summary:
> o The first time in about 10 weeks that our bug count did decrease
> instead of increase
>
>
Hello.
Summary:
o The first time in about 10 weeks that our bug count did decrease
instead of increase
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 b
Hello.
I replied to your original mail with the subject enlightenment systems.
Just as a reference here is the quote:
Its great to hear that you have interested in helping out with it!
Beber (cc'ed) handles our systems and he would be the one you should
talk to.
He is also in Europe so the ti
Would love to help out with infrastructure. I sent a reply to another
email thread about looking for help but got no response.
On 2016-03-07 16:13, Stefan Schmidt wrote:
> Hello.
>
> On 07/03/16 16:04, Mike Blumenkrantz wrote:
>
>> Is there anyone else who actively works on maintaining jenkins
Hello.
On 07/03/16 16:30, Mike Blumenkrantz wrote:
> What's actually required for this? Is it code-related or just
> infrastructure?
Its a mixture of things. Sometimes its code related sometimes you have
to find out why it only fails on Jenkins and not on your local host.
Some sort of detective
Hello.
Summary:
o Many Jenkins jobs had trouble since February. Last week I was able to
get most of them back into building so our reports are actually up to
date this week.
o The dropped coverage rate looks bad on a first view but I finally got
our coverage reports to take all files into accou
What's actually required for this? Is it code-related or just
infrastructure?
On Mon, Mar 7, 2016 at 10:15 AM Stefan Schmidt
wrote:
> Hello.
>
> On 07/03/16 16:04, Mike Blumenkrantz wrote:
> > Is there anyone else who actively works on maintaining jenkins builds? Do
> > we need to try getting mo
Hello.
On 07/03/16 16:04, Mike Blumenkrantz wrote:
> Is there anyone else who actively works on maintaining jenkins builds? Do
> we need to try getting more people on that?
>
Nope, nobody else on Jenkins jobs. Beber handles the server system side
but that is all.
I'm actually trying to get more
Is there anyone else who actively works on maintaining jenkins builds? Do
we need to try getting more people on that?
On Mon, Mar 7, 2016 at 10:02 AM Stefan Schmidt
wrote:
> Hello.
>
> On 07/03/16 15:52, Mike Blumenkrantz wrote:
> > It seems somewhat pointless to continue reporting Enlightenment
Hello.
On 07/03/16 15:52, Mike Blumenkrantz wrote:
> It seems somewhat pointless to continue reporting Enlightenment defects;
> Coverity hasn't updated anything there since January.
>
Because our nightly builds (and not only those) have been failing for
almost all February. One can clearly see t
It seems somewhat pointless to continue reporting Enlightenment defects;
Coverity hasn't updated anything there since January.
On Mon, Mar 7, 2016 at 7:36 AM Stefan Schmidt
wrote:
> Hello.
>
> Summary:
> o 9 new Coverity defects in EFL. If you added something last week please
> have a look.
> o
Hello.
Summary:
o 9 new Coverity defects in EFL. If you added something last week please
have a look.
o Branch coverage is finally working for upcoming coverage reports
o A manual Jenkins job to get coverage reports for Elementary runnign in
Exactness.
This should give everyone an overview ove
On Mon, 29 Feb 2016 17:13:11 +0100 Stefan Schmidt
wrote:
> Hello.
>
> On 29/02/16 16:52, Mike Blumenkrantz wrote:
> > Your continued mails have motivated me. As of this moment,
> > Enlightenment now has 0 defects reported.
>
> That is really great to hear! Thanks a lot for this work!
Zarro boo
Hello.
On 29/02/16 16:52, Mike Blumenkrantz wrote:
> Your continued mails have motivated me. As of this moment, Enlightenment
> now has 0 defects reported.
That is really great to hear! Thanks a lot for this work!
regards
Stefan Schmidt
--
Your continued mails have motivated me. As of this moment, Enlightenment
now has 0 defects reported.
On Mon, Feb 29, 2016 at 7:35 AM Stefan Schmidt
wrote:
> Hello.
>
> Summary:
> o Our bug count is still increasing and about to reach 800 open issues
>
>
> This should give everyone an overview ov
Hello.
Summary:
o Our bug count is still increasing and about to reach 800 open issues
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:
Hello.
Summary:
o Delayed to to vacation as well as sickness
o The scan-build runs on Jenkins are removed now.
o The misc config options job now also enabled libvlc, xpresent and
hyphen for build testing
This should give everyone an overview over what has happened in the last
week on the QA fron
Hello.
Summary:
o The scan-build runs on Jenkins are scheduled for removal this week
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: 6.6
Hello.
Summary:
o The x32 builds are now removed
o Added a jenkins misc config job with some extra configs
enabled(harfbuzz, web-p, liblz4, xinput22, xine, multisense, lua-old)
This should give everyone an overview over what has happened in the last
week on the QA front. The numbers in parenthes
Hello.
Summary:
o The x32 builds are disabled already and will get removed the next days
o Terminology is back to 0 Coverity defects
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
Hello.
On 11/01/16 13:57, Boris Faure wrote:
> On 16-01-11 11:35, Stefan Schmidt wrote:
>> o Terminology: Outstanding defects 3 (0) with a density of 0.04 (0)
> Those issues should be fixed now.
>
There is still a build for Terminology pending. Most likely it will
contain your fixes and they wil
On 16-01-11 11:35, Stefan Schmidt wrote:
> o Terminology: Outstanding defects 3 (0) with a density of 0.04 (0)
Those issues should be fixed now.
--
Boris Faure
Pointer Arithmetician
signature.asc
Description: Digital signature
Hello.
Summary:
o With 1.17 beta1 coming today we should focus on bug fixing. Put your
other stuff away for a moment.
o EFL coverity issues are raising, please have a loog. I will also
mention the ones with high impact on an updated 1.17 task list
o Our open bugs numbered hit 700 for the first t
Hello.
Summary:
o Several weeks now report due to end of year vacation
o Nice to see the coverage improvements we got
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.
C
Hello.
Summary:
o Elementary almost down to zeor defeft in Coverity. Some parse problems
on the coverity side for the rest. Mailed the team.
o Rest looks like the normal up and down
This should give everyone an overview over what has happened in the last
week on the QA front. The numbers in par
Hello.
Summary:
o EFL evas unit test segfault blocks many other builds
o Decrease of open patch submissions
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 Over
Hello.
Summary:
o Number of open bugs is still raising
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: 8.9% (10.23%) failed.
https://bu
Hello.
On 23/11/15 11:02, Boris Faure wrote:
> On 15-11-23 10:44, Stefan Schmidt wrote:
>> Hello.
>>
>> Summary:
>> o Almost 20 new coverity defects in EFL. I you recently added new code
>> here please check if they come from you.
> From my experience on Terminology, it seems Coverity changed/imp
On 15-11-23 10:44, Stefan Schmidt wrote:
> Hello.
>
> Summary:
> o Almost 20 new coverity defects in EFL. I you recently added new code
> here please check if they come from you.
From my experience on Terminology, it seems Coverity changed/improved
their analyzer. It now complains when the resul
Hello.
Summary:
o Almost 20 new coverity defects in EFL. I you recently added new code
here please check if they come from you.
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
Hello.
Summary:
o Some Jenkins out-take again
o Started to work on Jenkins builds for new Phab differentials. Will
take more time.
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 y
Hello.
Summary:
o Bug count reduced and patch count increased. Pretty normal in the last
week before a release.
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
Hello.
Summary:
o The ecore_con test failure in the nightlies blocks many other tests
right now
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 st
Hello.
Summary:
o Earlier as usual as i am +8 hours in timezone right now
o Not really an unusual week.
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 b
Hello.
Summary:
o A bunch new test for evas from JP (Thanks!)
o A strange coverage decrease while we added more tests. Could only be
more new code or more new tested code paths. Not sure what is going on
there yet.
o All new Elm Coverity defects comes from the enabled examples during build
o Rag
Hello.
Summary:
o Good work on EFL Coverity defects
o Only 1 defect left in Elementary (Worthwhile fixing for 1.16)
o Bug count and patches to be reviewed increasing
This should give everyone an overview over what has happened in the last
week on the QA front. The numbers in parentheses reflect
Hello.
Summary:
o A day late due to dealing with alpha1 and being on a conf
o We got the Coverity issues down during EDD. Aiming for 0 defects with
Elementary for 1.16 would be a good idea.
This should give everyone an overview over what has happened in the last
week on the QA front. The number
Hello.
Summary:
o
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: 9.05% (8.36%) failed.
https://build.enlightenment.org/
Unique Jenkins
Hello.
Summary:
o Patch pending queue size increases
o Besides this nothing remarkable happened
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 sta
Hello.
Summary:
o Bug reports increasing again
o Jenkins crash
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: 10.28% (7.08%) failed.
ht
Hello.
Summary:
o Patches to be reviewed increasing again
o Jenkins outage with the rest of our services
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
Hello.
Summary:
o Many nightly jobs haven't been running due to a problem with one test
case. Disabled that on for now and started the nightlies again. Should
hopefully produce new coverity runs today.
This should give everyone an overview over what has happened in the last
week on the QA front
Hello.
Summary:
o Patches to be reviewed increasing again
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: 8.81% (8.61%) failed.
https://
Hello.
Summary:
o Pretty normal week
o Some build problems that showed up but also got resolved.
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 s
Hello.
Summary:
o A day late as we had some minor trouble with Jenkins. Sorted out
thanks to Beber.
o I'm working on getting us coverage graphs for elementary on Jenkins
like we have with efl. Should bew done sometime this week.
o EFL wayland build is waiting for upgraded libs in gentoo (we need
Hello.
Summary:
o Jenkins is back running
o Pending patches dropped from 100 to 71 (Cedric is back from vacation?)
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:
Hello.
Summary:
o A long time since the last report due to myself being away.
o Jenkins is in stuck in restart mode right now. This might take a while
to get fixed as Beber is away and I have no way to fix this from the
jenkins interface.
o Pending patches incresed to 100 again
o No failed build
Hello.
Summary:
o Nightly builds are back and have examples enabled for efl now.
o The number of patches which need review has reduced.
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 gi
Hello.
Summary:
o Not much to summarize this week. Pretty normal.
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: 8.09% (8.10%) failed.
Hello.
Summary:
o Still not 100% catched up after the jnekins troubles but most jobs are
running fine again.
o We had a good run on EFL coverity issues last week.
o We had our first successful run of Exactness on out elm data set.
This should give everyone an overview over what has happened in
On Mon, 08 Jun 2015 11:07:00 +0200 Stefan Schmidt said:
> Hello.
>
> On 08/06/15 11:03, Carsten Haitzler wrote:
> > On Mon, 08 Jun 2015 10:59:40 +0200 Stefan Schmidt
> > said:
> >
> >> Hello.
> >>
> >> Summary:
> >> o The reasaon for the jenkins outtake have been some trouble with our fs
> >> a
Hello.
On 08/06/15 11:03, Carsten Haitzler wrote:
> On Mon, 08 Jun 2015 10:59:40 +0200 Stefan Schmidt
> said:
>
>> Hello.
>>
>> Summary:
>> o The reasaon for the jenkins outtake have been some trouble with our fs
>> after the partition was extended. Hopefully things are sorted out now
>> and we
On Mon, 08 Jun 2015 10:59:40 +0200 Stefan Schmidt said:
> Hello.
>
> Summary:
> o The reasaon for the jenkins outtake have been some trouble with our fs
> after the partition was extended. Hopefully things are sorted out now
> and we start to catchup.
what fs problems?
> This should give eve
Hello.
Summary:
o The reasaon for the jenkins outtake have been some trouble with our fs
after the partition was extended. Hopefully things are sorted out now
and we start to catchup.
This should give everyone an overview over what has happened in the last
week on the QA front. The numbers in
Hello.
Summary:
o Jenkins was off for some time last weeks. Sorry for that, still
unclear what caused it.
o The coverage percentage is a bit out of date due to the efl nightly
build failing for different reason for a while now.
This should give everyone an overview over what has happened in the
Hello.
Summary:
o Now with a section on the unique Jenkins builds fails from last week.
o
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
Hello.
On 18/05/15 09:50, Stefan Schmidt wrote:
> Hello.
>
> Summary:
> o New Covertiy issues for EFL and Elm. If you added new code since 1.14
> please have a look if your code has the problems.
> o Outstanding patches reviews reducing
>
>
> This should give everyone an overview over what has hap
Hello.
Summary:
o New Covertiy issues for EFL and Elm. If you added new code since 1.14
please have a look if your code has the problems.
o Outstanding patches reviews reducing
This should give everyone an overview over what has happened in the last
week on the QA front. The numbers in parenthe
Hello.
Summary:
o First report after the 1.15 merge window has opened and all new things
rushed in. Welcome the b0rkage!
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 tren
Hello.
Summary:
o We hit the 39% function coverage mark in unit testing
o Good work on phab bugs and patches issues this week
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
Hello.
Summary:
o Added new builds for Rage (changely, nightly and coverity)
o Fixed on long-standing problem where builds would randomly fail due to
leaked include path from pc file to old build
o Good work on phab bugs and coverity issues this week
This should give everyone an overview over wh
Hello.
Summary:
o Coverage increasing, bugs and coverity issues decreasing. That's how I
like my stabilization weeks.
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.
C
Hello.
Summary:
o Build failures got down again after some fixes from last week
o The efl coverity issues got a bit higher but there have been some
fixes for these which are not yet included because they happened after
the analysis
This should give everyone an overview over what has happened in t
Hello.
Summary:
o Higher number of build failures in Jenkins. Not really surprising
given the rush of last minute changes to hit the 1.14 merge window
o As the alpha is out today it would be a good time for everyone to have
a look at the issues listed in phab, test their own code and maybe also
lo
Hello.
Summary:
o The issues vanished from Elm and E are back now on coverity.
o Not much changes besides that
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 Ov
Hello.
Summary:
o Some of the disappeared coverity isses from last week are back, but
not all of them.
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 bu
Hello.
Summary:
o Most of the disappeared coverity issue them to come from some coverity
backend analyser changes.
o Its nice to see that we make progress with the unit tests covering our
code. Almost reached 40% coverage for our functions.
This should give everyone an overview over what has happ
Hello.
Summary:
o xcb build job for efl is now also working
o A bunch new Coverity issues found in Elementary
o We are about to reach 600 open issues on our tracker. If everyone
could spare a few minutes to look to five of them this week this could
already help.
This should give everyone an overv
Hello.
Summary:
o No report last weeks
o New build jobs to test for all three efl profiles (dev, debug,
release) as well as a efl job to build fpr wayland and a work in
progress job to build for xcb.
This should give everyone an overview over what has happened in the last
week on the QA front. Th
Hello.
Summary:
o Not much changed
o I switched jenkins to only keep the last 30 builds instead of 50 to
save some space on our machines
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 g
Hello.
Summary:
o More issues detected with Coverity due to an update of the coverity tools
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 statist
Hello.
Summary:
o Mingw build is still out of order
o Nightly builds are working again
o Jenkins updated as well as various libs and tools
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
Hello.
Summary:
o Pushed changes are build again from jenkins
o Mingw build is still out of order
o Nightly build is still out of order
o This one means that some data for Coverity, clang, coverage, etc are
N/A or outdated right now.
This should give everyone an overview over what has happened
Hello.
Summary:
o Its been a few weeks since the last QA report
o Most of the new coverity issues are coming from new tests that came
with the updated coverity client on jenkins.
This should give everyone an overview over what has happened in the last
week on the QA front. The numbers in parenth
Hello.
Summary:
o Nothing outstanding this weak.
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: 10.15% (12.83%) failed.
https://build.e
Hello.
Summary:
o Nothing outstanding this weak.
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: 12.83% (13.5%) failed.
https://build.en
Hello.
Summary:
o I introduced some jekins build problem while trying to get a better
understanding of the bug we have in our nightly clang builds.
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
las
Hello.
Summary:
o Not much changes this week.
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: 9.95% (13.87%) failed.
https://build.enli
Hello.
Summary:
o I just disabled the mingw builds from jenkins until we solved the
problem with this slave. No need to fail almost all builds for a known
problem.
o It seems phab has some reporting tool for the maniphest bug tracker
build in https://phab.enlightenment.org/maniphest/report/burn/
Hello.
Summary:
o Terminology is down to zero coverity defects again
o The bugs list keeps growing
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
Hello.
Summary:
o Evas Generic Loaders is down to 0 coverity issues. Thanks to Sebastian
for this!
o EFL also got down to 40 issues. Thanks to everyone involved!
o Our build failure rate is still high which basically comes form a
problem with elua under mingw. q66 is back now and we will make sure
Hello.
Summary:
o First week into the stabilization phase
o Nightly builds have been fully run through since a long time
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.
Hello.
Summary:
o Build failures are rising again. Now that we enter the stabilization
phase please make sure you also test your code with thing like make
check and make distcheck.
This should give everyone an overview over what has happened in the last
week on the QA front. The numbers in parent
Hello.
Summary:
o Two weeks without report as I was on vacation
o Nice to see most things are as they should be when coming home. :)
o Bunch of unit tests added which also shows in our coverage
This should give everyone an overview over what has happened in the last
week on the QA front. The num
Hello.
Summary:
o After Cedric fixed up our nightly builds we have updated results for
scan_build and coverage generation again.
o Coverage rate dropped as we disabled the c++ stuff by default now.
o Coverity issues are coming down to a level where it might be possible
to aim for a zero covverity
Hello.
Summary:
o Coverity finally catched up with most of the closed issues. :)
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.5% (3
2014-09-01 12:30 GMT+01:00 Tom Hacohen :
> On 01/09/14 10:36, Boris Faure wrote:
> > On 14-09-01 11:14, Stefan Schmidt wrote:
> > […]
> >> Unit tests:
> >> o 326 (399) unit tests for efl and none failing
> >
> > Did we remove a bunch of unit tests?
> >
>
> Yes we did. C++ is now disabled by defaul
On 01/09/14 10:36, Boris Faure wrote:
> On 14-09-01 11:14, Stefan Schmidt wrote:
> […]
>> Unit tests:
>> o 326 (399) unit tests for efl and none failing
>
> Did we remove a bunch of unit tests?
>
Yes we did. C++ is now disabled by default.
--
Tom.
-
Hello.
On 01/09/14 11:36, Boris Faure wrote:
> On 14-09-01 11:14, Stefan Schmidt wrote:
> […]
>> Unit tests:
>> o 326 (399) unit tests for efl and none failing
> Did we remove a bunch of unit tests?
>
I wondered the same. Coverage is still at the same level so we did not
drop tests. Maybe some ha
On 14-09-01 11:14, Stefan Schmidt wrote:
[…]
> Unit tests:
> o 326 (399) unit tests for efl and none failing
Did we remove a bunch of unit tests?
--
Boris Faure
Pointer Arithmetician
signature.asc
Description: Digital signature
--
Hello.
Summary:
o Coverity finally catched up with most of the closed issues. :)
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.54% (
Hello.
Summary:
o Coverity finally catched up with most of the closed issues. :)
o Pending patches got down as we opened the merge window
o Failed builds got up as we opened the merge window. ;)
This should give everyone an overview over what has happened in the last
week on the QA front. The num
On Mon, 18 Aug 2014 11:42:01 +0200 Stefan Schmidt
wrote:
> Hello.
>
> On 08/18/2014 10:36 AM, Tom Hacohen wrote:
> > Why is evas split from EFL in coverity?
> Evas generic loaders and emotion generic players. Just to lazy to
> write it out. Its like this since I first run coverity for them and
>
Hello.
On 08/18/2014 10:36 AM, Tom Hacohen wrote:
> Why is evas split from EFL in coverity?
Evas generic loaders and emotion generic players. Just to lazy to write
it out. Its like this since I first run coverity for them and put them
into the weekly report.
regards
Stefan Schmidt
---
Why is evas split from EFL in coverity?
On Mon, Aug 18, 2014 at 8:49 AM, Stefan Schmidt
wrote:
> Hello.
>
> Summary:
> o A lot nuked coverity reports in EFL. Raster got a tiny coverity
> addiction for a few days. :) Good job.
>
> This should give everyone an overview over what has happened in t
Hello.
Summary:
o A lot nuked coverity reports in EFL. Raster got a tiny coverity
addiction for a few days. :) Good job.
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
Hello.
Summary:
o Elm is back to 0 coverity issues. Thanks to raster.
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: 4.44% (12.37%) fai
Hello.
Summary:
o After to many weeks our code and jenkins is in a state again where
more jobs are running fine again.
o The 3% increase in coverage was coming over the last weeks but sadly
did not show up as the coverage builds have been broken.
This should give everyone an overview over what h
Hello.
Summary:
o Last weeks QA report gone mising due to me being offline.
o Not much changes since last weeks. Lets hope we et some numbers done
here in the three weeks stabilization phase.
This should give everyone an overview over what has happened in the last
week on the QA front. The number
Hello.
Summary:
o Terminology is down to 0 defects in coverity builds
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: 9.12% (5.45%) fail
101 - 200 of 298 matches
Mail list logo
