Re: [E-devel] Weekly news from the automated build and QA front

Hello. On 03/05/2018 03:21 PM, Stefan Schmidt wrote: > Hello. > > Summary: > o The server is coming up to speed again slowly after our hardware problems > o No new Coverity results yet, hopefully next week > > > This should give everyone an overview over what has happened in the last > week on

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o The server is coming up to speed again slowly after our hardware problems o No new Coverity results yet, hopefully next 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

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Not much changes this week o Latest Coverity build are failing thus we have no latest numbers for it 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.

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Updated coverity builds after it got fixed on Jenkins 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. Travis branches builds:

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o No recent Coverity numbers (a problem on our side where cov-builds segfaults) o Travis catched up with a long backlog of osx builds and all builds for EFL are passing This should give everyone an overview over what has happened in the last week on the QA front. The numbers in

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Updated wayland-protocols version on all CI system as newer EFL and E dependency o Increase in Copverity issues in EFL. If you submitted code last week please have a look and fix the issues reported in your code o Travis CI did identify another build break on OSX. I have a

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Quite a few Jenkins jobs failed due to the new wayland-procols versions requirement (we will get them updated on Jenkins) o The Travis builds helped to identify and verify a build problem with OSX o Travis now also builds with wayland and some miscellaneous build options as

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Stats wise it was the normal up and down last week o I worked on extending out Travis CI setup for EFL (parallel to Jenkins). It does run on all branches now and supports builds on various Linux distros in docker as well as mac OSX This can be very handy if you push your

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o EFL coverity issues again raise faster as we can fix them o Patch backlogs keeps going down 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

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Coverity issue rate still increasing o Pending patch reviews dropped (Thanks to JP, I guess) 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

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o A bunch of new patches for review 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.80% (7.16%) failed.

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Build failures have been reduced again. One slave more stable and I switched the Terminology and E builds to meson. o No coverage report as make check does not build for me (c++ related) o EFL Coverity defects are increasing again o E and Rage have each one Coverity issue left

Re: [E-devel] Weekly news from the automated build and QA front

Hello. On 11/21/2017 12:29 PM, Andrew Williams wrote: > Hi Stefan, > > Thanks for this. The 5 -> 21% build failures is the biggest jump by far, so > we have a commentary on the cause/issue here? > Yeah, I should have commented on that. Its basically due to one of the slave being down sometimes.

Re: [E-devel] Weekly news from the automated build and QA front

Hi Stefan, Thanks for this. The 5 -> 21% build failures is the biggest jump by far, so we have a commentary on the cause/issue here? Thanks, Andy On Tue, 21 Nov 2017 at 10:52, Stefan Schmidt wrote: > Hello. > > Summary: > o Been a long time since the last report. But I

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Been a long time since the last report. But I am back now and should run this regularly 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:

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Not much change since last 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: 5.84% (5.84%) failed.

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o No coverage information as make check is broken, 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: 5.84%

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o The big increase in efl tickets was actually not that big (I simply miscalculated) o Coverage is not working as the make check and neither make examples build for me right now. o Coverity has problems with the rage build. Need to debug. This should give everyone an overview

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o New Coverity numbers from today o Big increase in efl tickets due to project assignments in all tickets 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

Re: [E-devel] Weekly news from the automated build and QA front

You can't expect me to read that far down in a mail, it's 2017! On Mon, Aug 28, 2017 at 6:59 AM Stefan Schmidt wrote: > Hello. > > On 08/28/2017 12:55 PM, Mike Blumenkrantz wrote: > > Hm it looks like enlightenment is not updating again? > > See what I wrote in the

Re: [E-devel] Weekly news from the automated build and QA front

Hello. On 08/28/2017 12:55 PM, Mike Blumenkrantz wrote: Hm it looks like enlightenment is not updating again? See what I wrote in the summary below. On Mon, Aug 28, 2017 at 5:44 AM Stefan Schmidt wrote: Hello. Summary: o Some of the Coverity numbers might be

Re: [E-devel] Weekly news from the automated build and QA front

Hm it looks like enlightenment is not updating again? On Mon, Aug 28, 2017 at 5:44 AM Stefan Schmidt wrote: > Hello. > > Summary: > o Some of the Coverity numbers might be outdated ( I know for sure in > case of E) > > This should give everyone an overview over what has

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Some of the Coverity numbers might be outdated ( I know for sure in case of E) 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

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o At least the efl build are finally enabled again on Jenkins o Some builds need to stay disabled until our servers get updated dependencies (meson for rage, wayland update for efl) o The Enlightenment bug count made a significant drop lately This should give everyone an

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o A bunch of new patches to be reviewed. o I disabled all new Jenkins jobs now to see if that helps our server stability. Which means QA mails for the next two or three weeks are unlikely. This should give everyone an overview over what has happened in the last week on the QA

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o A few new Coverity issues and a bunch of new bug reports for efl 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:

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o E is back to zero 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 you a trend. CI: o Overall build statistic: 2.75% (2.70%) failed.

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o E is back to zero 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 you a trend. CI: o Overall build statistic: 2.75% (2.70%) failed.

Re: [E-devel] Weekly news from the automated build and QA front

Thanks! On Thu, May 11, 2017 at 4:16 AM Carsten Haitzler wrote: > On Tue, 09 May 2017 12:43:39 + Mike Blumenkrantz > said: > > > Hi raster, > > > > Can you look at CID1365406 for Enlightenment? I requested this last year > > and it

Re: [E-devel] Weekly news from the automated build and QA front

On Tue, 09 May 2017 12:43:39 + Mike Blumenkrantz said: > Hi raster, > > Can you look at CID1365406 for Enlightenment? I requested this last year > and it seems you still have not gotten to it... forgot about it... sorry. but really. it's not a bug. it's

Re: [E-devel] Weekly news from the automated build and QA front

Hi raster, Can you look at CID1365406 for Enlightenment? I requested this last year and it seems you still have not gotten to it... On Mon, May 8, 2017 at 4:08 AM Stefan Schmidt wrote: > Hello. > > Summary: > o A few more bug reports and a few more new patches, nothing

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o A few more bug reports and a few more new patches, nothing else really. 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

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Some new bug reports in EFL as well as E 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: 2.70% (2.74%) failed.

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Nothing noteworthy this 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. CI: o Overall build statistic: 2.74% (4.86%) failed.

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Coverity builds are running 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: 4.86% (5.14%) failed.

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Coverity numbers are outdated as the cov build fials on Jenkins since March 22nd 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

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o A lot new issues for efl, but the majority of them are todo items or new features. o The actual showstoppers for the release are almost done (separate mail for this) This should give everyone an overview over what has happened in the last week on the QA front. The numbers in

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Almost no change in numbers 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: 5.41% (5.14%) failed.

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o EFL bug count reduced o Coverity spotted 3 new 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: 5.14% (5.21%)

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Not much change in numbers 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: 5.21% (6.22%) failed.

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Not much change in numbers 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.22% (3.24%) failed.

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Decrease in open phab tickets and Coverity reports. A good sign for the stabilization phase. :) 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:

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o EFL Coverity count drops below 50 (Good job Raster) o EFL bug count increased mostly due to the fact that I did run through all tickets and added project tags when missing. This should give everyone an overview over what has happened in the last week on the QA front. The

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Not much changes since last 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: 3.31% (6.22%) failed.

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o A bunch of new patches are waiting for review 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.22% (3.02%) failed.

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Bunch of new Coverity defects in efl and E o Make check run failing again thus now numbers for unit tests or coverage 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

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Build failure percentage really low (holiday effect?) 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.83% (6.25%)

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Coverity tools have been updated showing us some more defects o Gustavo started a Coverity modeling file to surpress some false positives 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

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Code coverage is finally back on Jenkins (I had to drop branch coverage again as this is way top fragile with gcov and lcov right now) o Some work on our growing Coverity defects. Please have a loog at the list I posted a while back. This should give everyone an overview over

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Test suite failures from EO and maybe others, bisecting 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 statistic:

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Test suite is enabled again on Jenkins o For the Coverity issues you might want to look into some more detailed list I sent to the ml last 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

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Nothing to report 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.86% (8.11%) failed.

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Fairly calm week in terms of changes here. o Coverity catched up on EFL as well now and we got 8 new defects. If you added some code lately please have a look and see if they found issues in your code and fix them. This should give everyone an overview over what has happened

Re: [E-devel] Weekly news from the automated build and QA front

On Mon, 07 Nov 2016 15:28:14 + Mike Blumenkrantz said: > On Mon, Nov 7, 2016 at 4:12 AM Stefan Schmidt > wrote: > > > Hello. > > > > Summary: > > o First Coverity reports coming in again (EFL is still the old build) > > > > > > This

Re: [E-devel] Weekly news from the automated build and QA front

On Mon, Nov 7, 2016 at 4:12 AM Stefan Schmidt wrote: > Hello. > > Summary: > o First Coverity reports coming in again (EFL is still the old build) > > > This should give everyone an overview over what has happened in the last > week on the QA front. The numbers in

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o First Coverity reports coming in again (EFL is still the old build) 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:

Re: [E-devel] Weekly news from the automated build and QA front

Hello. On 03/11/16 06:54, Daniel Zaoui wrote: > Oooo... After more investigation, it more seems that exactness data > repository is not updated in the server. > > Now, I have to convince you to update Exactness repos. It gets updated every build but it was building from a different branch.

Re: [E-devel] Weekly news from the automated build and QA front

Oooo... After more investigation, it more seems that exactness data repository is not updated in the server. Now, I have to convince you to update Exactness repos. On Thu, 03 Nov 2016 07:38:54 +0200 Daniel Zaoui wrote: > Hi, > > Thank you guys to have brought

Re: [E-devel] Weekly news from the automated build and QA front

Hi, Thank you guys to have brought Jenkins/Exactness back to life. I checked the screenshots and it seems to be some issue with fonts, kind of freetype is not the last version. Can you tell me which version you are using there and how I can convince you to upgrade it :-) ? Thanks JackDanielZ

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o DNS problem on Jenkins is fixed and builds are slowly catching up o No new coverity reports. We submitted new builds but the Coverity server has a big backlog right now (around 100 builds in front our ours) o We reached 1000 open issues in total on phab so it was time to split

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o The DNS lookup problem is not fixed so no build job have been run last week o Coverity, CI and unit test runs are outdated (besides the failed builds) This should give everyone an overview over what has happened in the last week on the QA front. The numbers in parentheses

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Jenkins builds are failing right now to to DNS failures to lookup git.enlightenment.org o Coverity runs might be outdated 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

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o The E Coverity defect might be outdated as the last E coverity run is over a week old 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

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o The E Coverity defect might be outdated as the last E coverity run is 5 days old o I really need to split up the bug count as a big chunk here is from eventor and efleete now. This should give everyone an overview over what has happened in the last week on the QA front. The

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Enabled systemd on Jenkins builds again as the dependency is available now o Around 40 new test cases have been added 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

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o The default to enabling systemd caused builds to fails as Gentoo does not use systemd. Disabled for all jenmins builds 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

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Elm fileselector test case fails and causes many failed builds (reported as T4502) o Some new Coverity defects in newly submitted code in EFL This should give everyone an overview over what has happened in the last week on the QA front. The numbers in parentheses reflect the

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Nothing to special happened 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: 8.00% (3.10%) failed.

Re: [E-devel] Weekly news from the automated build and QA front

On Mon, 8 Aug 2016 16:34:39 +0200 Stefan Schmidt said: > Hello. > > On 08/08/16 16:22, Carsten Haitzler (The Rasterman) wrote: > > On Mon, 8 Aug 2016 16:08:58 +0200 Stefan Schmidt > > said: > > > >> Hello. > >> > >> On 08/08/16 15:35, Carsten

Re: [E-devel] Weekly news from the automated build and QA front

Hello. On 08/08/16 16:22, Carsten Haitzler (The Rasterman) wrote: > On Mon, 8 Aug 2016 16:08:58 +0200 Stefan Schmidt > said: > >> Hello. >> >> On 08/08/16 15:35, Carsten Haitzler (The Rasterman) wrote: >>> On Mon, 8 Aug 2016 14:31:06 +0200 Stefan Schmidt

Re: [E-devel] Weekly news from the automated build and QA front

On Mon, 8 Aug 2016 16:08:58 +0200 Stefan Schmidt said: > Hello. > > On 08/08/16 15:35, Carsten Haitzler (The Rasterman) wrote: > > On Mon, 8 Aug 2016 14:31:06 +0200 Stefan Schmidt > > said: > > > >> Hello. > >> > >> Summary: > >> o Coverity

Re: [E-devel] Weekly news from the automated build and QA front

Hello. On 08/08/16 15:35, Carsten Haitzler (The Rasterman) wrote: > On Mon, 8 Aug 2016 14:31:06 +0200 Stefan Schmidt > 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

Re: [E-devel] Weekly news from the automated build and QA front

On Mon, 8 Aug 2016 14:31:06 +0200 Stefan Schmidt 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 :) > >

[E-devel] Weekly news from the automated build and QA front

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.

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Must but not all Jenkins services are back. o A significant decrease in Coverity defects and open bugs 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

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Jenkins is done so many stats are not available 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 statistic: N/A

Re: [E-devel] Weekly news from the automated build and QA front

Thanks! On Mon, Jul 18, 2016 at 11:12 AM Stefan Schmidt wrote: > Hello. > > > On 18/07/16 16:59, Mike Blumenkrantz wrote: > > Can we stop including counts for projects which haven't successfully > built > > in the past 1-2 weeks? Every time this goes out I go to check

Re: [E-devel] Weekly news from the automated build and QA front

Can we stop including counts for projects which haven't successfully built in the past 1-2 weeks? Every time this goes out I go to check the build and sit there scratching my head until I notice it hasn't built since last month. On Mon, Jul 18, 2016 at 9:28 AM Stefan Schmidt

Re: [E-devel] Weekly news from the automated build and QA front

Hello. On 18/07/16 16:59, Mike Blumenkrantz wrote: > Can we stop including counts for projects which haven't successfully built > in the past 1-2 weeks? Every time this goes out I go to check the build and > sit there scratching my head until I notice it hasn't built since last > month. I

Re: [E-devel] Weekly news from the automated build and QA front

Hello. On 18/07/16 14:37, Stefan Schmidt wrote: > Hello. > > Summary: > o New Coverity run is delayed New run for EFL is done now. 43 issues fixed and 4 new reported. regards Stefan Schmidt -- What NetFlow Analyzer

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o New Coverity run is delayed o Bug count got 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 give you a trend. CI: o Overall build statistic: 12.36% (9.91%)

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Raster, JP, Chris, Derek and others had a good run on Coverity defetcs. These are not even the lastest numbers (next analysis should happen tomorrow) o Our pending patches queue also dropped nicely This should give everyone an overview over what has happened in the last week

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Enabled many, many config options for the efl build which submits to Coverity (wayland, drm, etc). This should find more defects in code paths we did not submit so far. This should give everyone an overview over what has happened in the last week on the QA front. The numbers

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Still no updated coverage report as the build fails with various problems even after some are fixed. Hopefully next 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

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o The problems with Jenkins have been found and fixed. One problem is still pending a fix thus we have no recent coverage reports (should be back next week) o A lot new Coverity issues came up with the tons of copde merged recently. Text interface and SVG support in edje jumped

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o The stats coming from Jenkins are almost the same as last week as we have build issues which are blocking any updates here. o The Elementary.elm_fileselector_selected test case fails with signal 9 o The Eio.eio_test_job_xattr_set fails with signal 11 This should give everyone

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o More test cases enabled and added but also more code added with the loaders and players thus the coverage is not growing as we would like to. o A pretty normal rush things in before merge window closes week I would say. This should give everyone an overview over what has

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Nothing big to report 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: 13.23% (10.03%) failed.

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Nothing big to report 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.03% (13.08%) failed.

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o E is back to 0 defects in Coverity o Rage is also back to 0 defects in Coverity 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

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Nothing urgent to report 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: 11.04% (11.57%) failed.

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o First time we have over 900 open issues in our bug tracker :( 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: 11.57%

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Nothing exciting 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: 10.00% (9.18%) failed.

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o Nothing exciting 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.18% (11.83%) failed.

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o The new Coverity numbers are in! o Enlightenment is down to 0 defects. Congrats! o That means only EFL and Rage have Coverity defects left. This should give everyone an overview over what has happened in the last week on the QA front. The numbers in parentheses reflect the

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o While most build problems are sorted out we still have some. One of it blocking the nightly efl build and thus we have no recent numbers for coverage and coverity. Hopefully next week again. This should give everyone an overview over what has happened in the last week on the

[E-devel] Weekly news from the automated build and QA front

Hello. Summary: o First report after the elm merge so take this all with a grain of salt o While most build problems are sorted out we still have some. One of it blocking the nightly efl build and thus we have no recent numbers for coverage and coverity. Hopefully next week again. This should

Re: [E-devel] Weekly news from the automated build and QA front

Thanks for this. I am confused about the results page. It claims there are 12 defects outstanding, but there are zero unresolved defects available in the list. Is there more information available? On Tue, Mar 22, 2016 at 4:16 AM Stefan Schmidt wrote: > Hello. > > On

Re: [E-devel] Weekly news from the automated build and QA front

Hello. On 22/03/16 08:31, Stefan Schmidt wrote: > Hello. > > On 21/03/16 16:26, Mike Blumenkrantz wrote: >> The Enlightenment build hasn't updated in over a week; the page says that >> something is not configured. Are you aware of this? > The not fully configured part is something you can ignore

Re: [E-devel] Weekly news from the automated build and QA front

Hello. On 21/03/16 16:26, Mike Blumenkrantz wrote: > The Enlightenment build hasn't updated in over a week; the page says that > something is not configured. Are you aware of this? The not fully configured part is something you can ignore here. We do not have components setup neither a modeling

  1   2   3   >