from:"Didier Roche"

Re: [Ubuntu-phone] Daily releases delayed today

2013-08-08 Thread Didier Roche

Le 08/08/2013 08:14, Timo Jyrinki a écrit :

Hi,

Yesterday evening a problematic qtbase update [1] was uploaded to
saucy. Because of the problems it created it was stuck in -proposed,
but as our daily releases system uses -proposed (now temporarily
disabled) it resulted in failing of various builds last night.

[1]
https://launchpad.net/ubuntu/saucy/+source/qtbase-opensource-src/5.0.2+dfsg1-7ubuntu4

I noticed the upload this morning and a fix for it was now uploaded
[2]. The failed packages are being rebuilt now but they'll be
published later than usual. Touch images will be respun as well.

[2]
https://launchpad.net/ubuntu/saucy/+source/qtbase-opensource-src/5.0.2+dfsg1-7ubuntu5

-Timo

Ok,
everything that could have been published are now rebuilt, tested and
published.

To not block on my qtbase upload to build, I disabled -proposed from the
build and tests environment temporarly, then, we relaunch all failing
builds, and now, reenabled this config.

As well, after a discussion yesterday with Pat, we maintain a (manual
for now) dashboard with details about what's blocking each stack for
release. This is complementary to our existing direct ping to the
developer (and now manager) + bug filing process:
https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dHFtUmlPOUtCRk8zR2dtaEpIbUVhMmc#gid=3

Cheers,
Didier
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] Daily releases delayed today (landing is going to create build/CI issues during the day)

2013-08-08 Thread Didier Roche


Le 08/08/2013 10:13, Sebastien Bacher a écrit :

Le 08/08/2013 09:44, Didier Roche a écrit :
To not block on my qtbase upload to build, I disabled -proposed from 
the build and tests environment temporarly, then, we relaunch all 
failing builds, and now, reenabled this config.


Hey Didier, everyone,

Just a small follow-up, the qtbase version in saucy got a depends on 
libhybris (it built using libmirclient1 from the 20130806 which had 
the depends, libhardware was splitted out of libhybris since and the 
new mir/qtbase(in proposed) lost that depends).


Rebuilding against the archive version rather than proposed means 
ubuntu-ui-toolkit picked the libhybris depends and is to add to the 
list of packages breaking build/CI if you are not using an android 
device (e.g archive builders, jenkins).


I understand there is pressure to land updates, so I'm not going to 
argue on whether the tradeoff of forcing those landing is the right 
thing, just take that email as information sharing.


Things should sort themself once qtbase moves out of proposed and we 
trigger rebuilds, meanwhile if you see build/CI issues that's going to 
be due to that




After another rebuild of qtbase and rebuilt trigger for the sdk, 
settings and gallery-app, all should be now sorted out (just need one 
publisher cycle from proposed to the release pocket).


Thanks everyone (Phew!) :)
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Daily release are now running every 4h.

2013-08-14 Thread Didier Roche


Hey guys,

Yeah, we need a better name with that cadence change. :)

So now, the daily release process is run way more often to speed up our 
delivery time to the baseline (every 4h). You will find more information 
at 
http://blog.didrocks.fr/post/Release-early%2C-release-often%2C-release-every-4h%21.


The particular important piece for upstream can be summed up there:
* you now have a window of 4 hours before the "tick" to push stuff in 
different trunks in a coherence piece rather than only once a day, 
before 00 UTC.
* everytime there is an issue with one component/stack, a bug is opened, 
upstream is pinged about it and we write about those on 
https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dHFtUmlPOUtCRk8zR2dtaEpIbUVhMmc#gid=3. 
We escalate after 3 days if nothing is fixed by then.


You can find the schedule of the 4h tick here: 
https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dHFtUmlPOUtCRk8zR2dtaEpIbUVhMmc#gid=4 
(look at the X cross for when a build starts)


I hope that will help to get faster and even more snappier and easy 
delivery!


Thanks,
Didier
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Summary of Landing Task For Call 27.09.2013

2013-09-27 Thread Didier Roche

Hello all.

We are meeting twice a day to plan out landings. This email is an
experiment to see if sending out some quick notes from that call is
helpful to people. Feedback is welcome.

As always, we updated the landing pipeline:
https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0Au6idq7TkpUUdGNWb0tTVmJLVzFZd0doV3dVOGpWemc#gid=0

You can see details there.

* Alexander will be gone next week. Rick will sit in on task force
calls to help with escelations if they are necessary.
* Our next build is 68. This image will have the new lightdm session
as well as some long awaited scope crasher fixes. We want to land unity
changes, but need a release team ack because the changes impact unity
and compiz on the desktop. We will go ahead with 68 without the changes
if they can't make it through the archive in time.
* We want to dedicate build 69 to the new multimedia stack. We don't
plan to promote 69 since it will be over the weekend, but it will give
the team a chance to triple check that the new stack works just fine on
RO images. The new multimedia stack would then be generally available on
image 70.
* We are tentatively targeting build 71 for switching to Mir by
default, but this is blocked on auto-pilot support landing and those
tests passing.

Thanks,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Summary of Landing Task For Call 28.09.2013 (1)

2013-09-30 Thread Didier Roche


Hey all.

After this week-end, we are back in full shape for releasing even more 
images! Here are the latest news:


* Image 68 contained all the retained fixes for quite a long time, the 
lightdm session changes + unity8 and unity changes. Despite all those 
changes, the autopilot tests results are really promising. Well done 
everyone!
* We got 2 additional images builds during the week-end (69 and 70, due 
to a miss publisher tick), which are fixing an ubuntu-download-manager 
regression and getting more of the media-switch-to-hardware work in. The 
last one has still some bug which are going to be worked on today.
* We plan to publish image 70, but in addition to good test results, 
some more dogfooding due to a possible regression in unity8 is under 
investigation before the publication is fully done.
* Image 71 will be probably boring (plan this evening): mostly bug 
fixes. Note that we want as well to land the timezone configuration change.


This is all to clear the ground for the next image (72), which is 
planned to be about the media playback running on hardware. We hope as 
well to get the system-image changes (to get the progress download bar 
working in the UI) in. We hope that Mir switch by default may pass into 
that image or the next one (still working on the autopilot support landing).


Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Summary of Landing Task For Call 28.09.2013 (2)

2013-09-30 Thread Didier Roche


Hey everyone.

Afternoon (for some ;)) call, here is that status:

* We published image 70 which is the greatest and best ubuntu phone 
image we ever had. Congrats everyone :)
* We are close to completion to kick a build for image 71, aka "the 
boring image". Most of bug fixes are already in the archive, we are 
still waiting on some clicky-ones and download-manager. We expect to 
have that image starting to build in a couple of hours.
* This will enable us to get some bug fixes in several areas for image 
72. This image should be built ASAP as well to be able to test a pending 
system-image update to finally get feedback in the system settings 
update UI! If everything is fine, this system-image will go in image 73.
* media stacks will probably be uploaded tonight to get into next image 
(so either 72 or 73).


More news on Mir tomorrow. Stay in touch!

Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Summary of Landing Task For Call 01.10.2013 (1)

2013-10-01 Thread Didier Roche


Hey all.

Here are the latest image on the touch image front side
* We got multiple builds overnight to handle and test image upgrade (71, 
72, 73, 74). We got as planned the new media running on hardware landed 
\o/. system-images is in as well (but from our testing, it seems that we 
don't have the progress showing yet, so probably pending on another 
service side update). We also got some latest keyboard work.


However, some bad news:
* We saw that the timezone changes is working manually, but not when 
used by the system settings UI
* We got some regressions on mediaplayer-app and camera-app AP tests 
that are difficult to reproduce locally for most of us.
* It seems that content-hub was landed without any aggreement, and this 
is regressing the pickler in gallery-app


So what do we do? Image 75 will be about 2 things:
* getting back to an image that we can promote.
   - We are actively working on sorting out why media-player and 
camera-app started to fail reliably on the infrastructure. We were only 
be able to reproduce it once. osomon is helping us on that tasks and we 
are tracking that with upstream directly (seems libusermetrics, which 
though didn't land for a while, seems to be the cause for both issues).
   - Martin and Oliver are working on fixing the permission issue which 
makes the timezone changes not working on the system settings UI.
   - content-hub will probably be fixed with a gallery-app rebuild. 
Working with seb on that one.
* we got upstream proposing us a lot of upstream fixes to get AP + 
application scope activation working with Mir! So we adapt our landing 
task force to get that in the image as well (but not enabled by default) 
and running the AP tests now that we are supposed to be able to do so. :)


So, image 75 == fix regressions + Mir working with AP (not enabled). Not 
any further plan until those are under control.


Let's get that's in!
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Summary of Landing Task For Call 01.10.2013 (2)

2013-10-01 Thread Didier Roche


Hey everyone.

Part 2 on the exciting image release plan of the day!

Some good news:
* the regressions on mediaplayer-app and camera-app were tracked down 
(It was as deep as in the initramfs!). We are waiting on an android 
rebuild to get everything we need in. Then only we can start rebuilding 
the next image.
* the timezone changes through the UI is now supposed to work with an 
upload in systemd that just happened, waiting for it to land as well.

* the content-hub regression is now fixed as well.
* Mir was updated to latest. We still wait for one fixes in to get AP 
tests running with it, but we are really close!


Image 75 will contain those fixes as planned to get an image we are 
ready to promote tomorrow!


We are then focusing mainly on 3 things:
* getting back on the backlog we started to create today as part of 
blocking all releases
* a better ui in system update so that people can see an indeterminate 
progress bar
* get the latest fix for application tracking on Mir and be ready to 
have AP tests running on them.


We hope to get that done for image 76. Maybe we'll only finish the 
backlog on 77 (for most minor issues). Please be patient, we'll get there!


Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] Summary of Landing Task For Call 01.10.2013 (2)

2013-10-01 Thread Didier Roche


Le 01/10/2013 22:23, Jim Donegan a écrit :

Hi all.

Yes indeed - totally agree. I've not contributed here thus far as I know you 
guys are busy working to a deadline but I have followed your progress and have 
to say it's looking really good.

Power to yer collective elbows!


Thank you Jim and Nathan, we'll try to keep it up then! ;)

Didier



Jim Donegan

Sent from my iPhone


On 1 Oct 2013, at 21:20, Nathan Haines  wrote:


On 10/01/2013 09:43 AM, Didier Roche wrote:
Part 2 on the exciting image release plan of the day!

Didier,

Frankly, these kinds of updates are absolutely the most valuable I've ever seen 
as per tracking the progress and health of the project.  It's extremely 
valuable to have an overhead view of how the system is coming together as a 
whole.

It barely edges out the beautiful weekly updates the Music team is doing, for 
example.

So thanks for everything.  :)

Regards,
Nathan

--
Nathan Haines
Ubuntu - http://www.ubuntu.com/

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp



--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Summary of Landing Task For Call 02.10.2013 (1)

2013-10-02 Thread Didier Roche


Hey everyone.

So, image 75 was built with all the planned fixes.
Unfortunately, we are still seeing some tests issues due to the hardware 
decoding switch for mediaplayer. This is on track and planned to be 
fixed before EOD (see 
https://bugs.launchpad.net/ubuntu/+source/libhybris/+bug/1234007).


So image 76 should be the one we promote thanks to those fixes. To not 
get everything stalled until then, we are as well opening slightly the 
gate for safe changes, after some serious testing:

* bug fixes in applications and settings app
* new online music scope for online search in the dash
* music-app powerd lock
* some more bits to get AP running on Mir
* unfortunately, gstreamer 1.2 landed in an uncontrolled manner in that 
image. It's a bug fix only released, but would have been suitable for 
image 77. We'll reash on the statement to get more controlled landing.


In parallel, we are already working on running AP tests on Mir, some 
issues are already detected: 
https://bugs.launchpad.net/mir/+bug/1233944, but we will have progress 
in image 76 in the sense that some tests are already running (and are 
not stalled anymore). We'll get an exhaustive list by end of the day.


All the other more risky landing (like initramfs fixes and changes for 
system-image, new sdk, application activation behavior changes) are 
defered to image 77, once we can promote safely 76 (planned by EOD).


Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Summary of Landing Task For Call 02.10.2013 (2)

2013-10-02 Thread Didier Roche


Hey guys.

So, we are really close to have image 76 to become a reality (in 20 
minutes, it will start building).

As expected, this image has:
* bug fixes in applications and settings app
* new online music scope for online search in the dash
* music-app powerd lock
* some more bits to get autopilot running on Mir
* a gstreamer 1.2 update
* and the fix for mediaplayer to be able to read all expected video 
format/size (and so, having AP tests passing again \o/). This one is 
confirmed locally, need to be confirmed on the infrastructure.


We hope to be able to promote that image.

Then, road to 77, we plan on that one to get many bug fixes, and will 
focus on:
- getting the application activation better on Mir: application getting 
on front
- latest SDK stack, thoughtfully tested with all tests we have at our 
disposal

- core apps autopilot tests fixes
- filter and category fixes in various scopes
- various plumbing fixes that will bring us as well closer to emulator 
support


Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Summary of Landing Task For Call 03.10.2013 (1)

2013-10-03 Thread Didier Roche


Hey guys.

Good news on the landing today, we are able to promote image 78!

What 78 but not 76? What happened during a busy EU night?
* 76 had all the test fixes that was expected to get back to a greener 
image (see previous message for the detail)
* 77 was an opportunity to get core apps autopilot fixes and was issued 
for that.
* We discovered yesterday an issue with the ringtone: 
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1234087. Image 
78 was kicked in with a fix for that.


Looking at the autopilot test results, we are in a very good shape: just 
one core app has still one failing test. As we run now the toolkit tests 
as well, (ignoring the flacky tests we have to relaunch), we are now at 
99% image pass rate \o/ (on 320 tests).

So image 78 is the new just promoted gorgious ubuntu touch image!

Looking further, image 79 is targeted to:
* getting the application activation better on Mir: application getting 
on front

* filter and category fixes in various scopes with live update
* various plumbing fixes that will bring us closer to emulator support
* Mir fixes for autopilot (creating a transition due to an ABI break)
* system-update fixes to finally get a progress bar with an ETA while 
downloading the image update

* better video seek support with the new media stack
* latest autopilot potentially after a detailed testing (and some 
branches merged in upstream trunk to support latest and greatest)


Note that preliminary result on latest SDK stack showed some 
regressions, so this one will probably be delayed and we will work with 
upstream to get them fixed.


Phew, enjoy image 78! Image 79 is going to be exciting for sure :)
Didier

-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Summary of Landing Task For Call 03.10.2013 (2)

2013-10-03 Thread Didier Roche


Hey

As planned, we got a lot of goodness for image 79:
* getting the application activation better on Mir: application getting 
on front

* filter and category fixes in various scopes with live update
* various plumbing fixes that will bring us closer to emulator support
* Mir fixes for autopilot and the 100% unity8 spike is now part of the past
* system-update fixes to finally get a progress bar with an ETA while 
downloading the image update
* latest autopilot version (with some additional backport for it in 
various upstream projects). This can unblock some application activation 
and click package support.


The image is currently building, we hope to continue as good test 
results as we got.
From now on, everyone should be able to try autopilot tests while 
running Mir.


UI toolkit didn't make it, upstream is working with us to fix the 
regressions we saw on various applications.



So, what's up for next image (80):
* better video seek support with the new media stack
* continued work on the application activation (but this one is pending 
to latest toolkit)
* we will get latest Unity8 stack version for bug fixes and password 
support on snap decisions



I guess that's it for what is planned for now! Starting tomorrow, Loïc 
will excellently handle the coordination and report, and then Alexander. 
I'll be back next Thursday. Keep the image green guys! ;)

Cheers
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Summary of Landing Task For Call 10.10.2013

2013-10-10 Thread Didier Roche


Hey guys,

Back for some updates on what we landed and what we plan to land

Image 90 is promoted! It's the first image with Mir enabled by default. 
The switch was done even if the dashboard isn't green as we hoped to so 
that we can all focus on getting those issues fixed ASAP. Everyone 
should concentrate on making that experience as best as we can.


Image 91 was spinned up with an unity8 fixes for the tests failing, 
unfortunately, not as helpful as we hoped. (However, the unity8 crash on 
startup is gone)


Image 92 has those fixes staged or getting in:
- we did have the maliit keyboard loading before unity8, which was 
resulting in multiple crash, the upstart job order is now fixed
- powerd (currently moving to the release pocket) fix to get unity8 test 
suite running (device not getting to sleep when unity8 is restarting for 
the tests)
- unity-scope-click transition (currently moving to the release pocket) 
to handle debs and click packages in the image. This is going to fix a 
flickering introduced in image 90 (as well as battery polling).


We'll rekick an image as soon this is on the archive.

At the same time, we did work with upstream to identified different 
kinds of issues making those tests failing:
* We got some out of memory issues, this one can be linked to the 
upstart memory link but 100%, multiple people are working on it 
(probably causing 
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1238050 and 
https://bugs.launchpad.net/unity8/+bug/1237207)
* Maliit keyboard is crashing in 
https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1237870. 
dandrader is working on it.

* the HUD is still crashing. The HUD team is on it and under review.
* Multiple tests can't reveal the toolbar 
(https://bugs.launchpad.net/mir/+bug/1238062). It seems to be a 
Mir-input-related one. The Mir team was contacted about that one.
* We may still have an unlock screen issue with UTAH, doanac is on that 
one (and it's not linked to any image)

* Some more debugging info in platform-api for wrong socket creation
* Unity8 fix for crash on exit (coming to unity8 trunk)


Those seem to be the cause of AP tests failing that we currently see in 
the dash. We still hope to see more fixes in the coming hours and let 
the door opened for those. Tomorrow morning (european time), we'll 
reassess on reopening the gate for all other uploads depending on the 
above fixes.


Cheers,
Didier

PS: thanks Loïc for the heoric effort and countless work hours you did, 
go to sleep now ;)


--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Summary of Landing Task For Call 11.10.2013

2013-10-11 Thread Didier Roche


Hi everyone!

Good good news today, we promoted image 92 (see yesterday's email for 
the fixes in) and we had glorious test results compared to the first one 
with Mir enabled on image 93. This one is also promoted!


Image 93 contains some of the fixed issues we communicated yesterday 
(nice work is happening while you are sleeping ;)) and that we landed early:
* Some more debugging info and harness in platform-api for wrong socket 
creation

* Hud crash fix
* Mir crasher on invalid connection fix

This is what is helping to get closer to a green image!

Image 94 is going to be kicked in the coming hours. This one contains a 
lot of work which has been hanging back for Mir stabilizing. What we 
have in is mostly:
* a big indicator landing (the settings needed it) with fixes for the 
sound indicator as well (we pulled in ubuntu the whole unity7, compiz, 
nux stacks as well for this with a lot of fixes for the destkop itself)
* a fix in qtdeclarative which made unity8 spinning in infinite loop at 
100% (annoying especially during tests)
* speaking of unity8, another fix which made it spamming upstart and 
this latter was growing in memory by some hundreds of gigabits (so, the 
out of memory error mentionned yesterday). Maybe there is still more 
work needed for that. Other bug fixes and niciness in grabbing latest 
unity8 trunk.
* a big epic landing containing multiple backend services, latest unity8 
and mediascanner (fixes are not yet complete though) to get thumbnailing 
activated
* misc bug fixes in multiple apps (webapps, click, camera-app, 
system-settings)

* Online accounts error handling and cancelling
* wrong shell set in the environment
* other crash fixes

All that involved more than 45 packages uploaded today (and it's not 
over yet ;)).



We hope that we are to announce some very good news for the next image 
(potentially on Monday). This one is planned to include:
* we are getting software rendering for some codecs that are having 
issues with the hardware decoding. This is enabling us to support more 
video formats that we currently do.

* latest sdk with a lot of fixes
* some keyboard fixes
* be finally able to run unity8 autopilot tests.
* and more! ()

Meanwhile, we'll evaluate tests results from image 94 which sounds 
really really promising:


Have a good week-end!
Cheers,
Didier


--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Summary of Landing Task For Call 14.10.2013 (1)

2013-10-14 Thread Didier Roche


Fresh news on the image side from the week-end!

So, image 94 built as expected with the content detailed in previous 
email. In addition to those, we can note that we had:

- the keyboard fixes making some more autopilot tests passing
- latest unity8 for better input handling for autopilot tests as well
- some other minor fixes

The tests that ran over the week-end seems to show a little progression 
on the automated testing side.


Image 95 was kicked as well with more click fixes, pulse audio handling 
and boot speed improvment. The test results are a little bit beyond 
image 94, but it seems to be due to the general noise of flacky tests 
(for instance, unity8 autopilot tests hanged, and so, all were counted 
as failing)


We finally have the end of the media story with thumbnailing support! 
This built last night as image 96. The tests are nearly finished. To 
prevent spending too much time on manual dogfooding to qualify an image 
for promotion, we decided to focus on that one and wait for the 
automated test results (already 3/4 are published by now and they look 
good).


We are waiting for the next images (ETA not decided yet) on focusing on 
performance improvment and still some crash fixes (some components 
didn't pass our validation yet). So, our focus is to work with upstream 
for the upload we rejected + getting a better tests pass rate (retracing 
crashers, try to spot with upstream what's still need to be fixed).


I guess that's a good plan for the day. More info on the second meeting 
later on.


Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Summary of Landing Task For Call 14.10.2013 (2)

2013-10-14 Thread Didier Roche


hey everyone,

Short one this time. We worked on the quality and ask all upstreams 
(they should have been contacted) for crashers and AP tests failing. 
Most of them are due to one big crash which is under tracking 
(https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1233988 
for reference).


Meanwhile, we still had some nice addition, planned for next image (that 
will be kicked later today or maybe tomorrow):

* url dispatcher fix for click packages (that one got rejected)
* a new touch sound theme \o/
* prevent screen from turning off on idling when playing a video

That should make the bit dent of image 97.

Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] Installing click packages without Ubuntu-one

2013-10-14 Thread Didier Roche


Le 14/10/2013 22:05, Nicolas Delvaux a écrit :



Final if you get a new ubuntu phone it will hopefully be able to do
what google does with android and set you up with all the apps you
have purchased/installed.

AFAIK it is already possible on the desktop (the "Sync Between
Computers" menu item). And it still allows the software center to be
used without an Ubuntu One account.


Actually, this feature is using an Ubuntu SSO (Ubuntu One) account.

Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Summary of Landing Task For Call 15.10.2013

2013-10-15 Thread Didier Roche


Hey hey, good news from today!

Image 97 was built quite late yesterday, it contained as planned:
* url dispatcher fix for click packages
* a new touch sound theme \o/ (part 1 on 2)
* some hud crash fixes
* some new icon theme
Note that we have way less crashes, but the dashboard results still 
shows some hangs during tests. Consequently, we're not promoting this one.


So, we continued focusing on image 98, which is going to start building 
in some minutes. This one has:
* mir performance improvement! We see an epic performance improvement on 
Mir (particularly in the first minutes after booting). Well done Mir 
team, nice to see this getting better!

* support in system settings for the new sound theme
* better texture handling in multimedia
* prevent screen from turning off on idling when playing a video
* unity8 multiple fixes, especially for autopilot tests (better way of 
handling restarting it)

* misc fixes as usual

Finally, image 99 is planned to focus on:
* system image update high priority bug fixes
* keyboard dismiss with swiping
* unity8 fix for handling services more properly
* some application updates containing safe, but important bug fixes

See you all,
Didier

PS: no, there is no hidden secret cabal so that ubuntu touch V1 will be 
image 100 ;)


--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Summary of Landing Task For Call 16.10.2013

2013-10-16 Thread Didier Roche


Hey, one day before releasing V1 :)

We did get a 98 build with all the fixes that we listed yesterday, in 
addition to that, we got an extra 99 to fix an ofono regression.
This one has good AP test results (not yet stellar). Most of the issues 
are in the core apps, but due to some crashers that are getting fixed in 
next image, we still have bad results for them. I still ask our lovely 
core apps coordinators to check thoses :)


Image 99 was dogfooded as well and is, as of today, the best image we 
never had, so we promoted it.


So, 100, big milestone, with a lot of goodness in it:
* system update/download manager multiple bug fixes and support for 
pausing/resuming.
* multiples fixes in the phone/dialer stack. Being able to finally see 
in the history the time for past calls as well

* bluetooth reliably switching on and off
* some crashs fixed in the mediaplayer and others in unity8 and keyboard
* system settings fixes for language and wifi selection
* clicking on settings on the indicators now launch the right apps
* killing duplicate app manager (only using the memory we need then)
* u1 settings fixes for account setup
* indicators segfault fixes and better location service respawn
* phablet-tools support for additional mirror
* indicator-network polish
* we also prepared the change for the oom killer (only enable if we 
remove the swap), but ensure it's in without any regression
* finally, we are waiting on a last memory leak fix for mir/unity8 
binding to be merged, which was making the whole experience slow after 
opening/closing multiples applications


Some fixes were rejected and under work, we still want them for the release:
* ubuntu keyboard fixes to dismiss the keyboard and get it appearing 
more reliably (high prio)


The image will be kicked no later than 2am UTC.

Lots of goodies, let's make tomorrow's release day magic!

Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Ubuntu for phone is here!

2013-10-17 Thread Didier Roche


Hey everyone,

Image #100 was the right one! Spinned late yesterday (but with love), 
the tests results are good and dogfooding helped a lot confirming we 
really desired that image.
We fixed in that image (as described in yesterday's email) the most 
annoying bugs, even the big mir-related performance one when running the 
phone for a long time. \o/
So, #100 contains a lot, but just in time fixes! They were all validated 
systematically and that's what enables us to confidently release that 
image today.


After avoiding a heart-attack due to unity8 autopilot test results 
(which were false negatives, only test issues), we computed the pass 
rate and ran the tests manually giving us the best Ubuntu for phone 
image we ever had!


Note that we'll still have some memory leaks to tackle, but that, with 
other fixes, will come in future udpates. Right now, let's celebrate 
this very golden release image and have fun flashing/experiencing Ubuntu 
for phone.


We'll be a little quiet until next week on the landing side when 
settings things up for the future, see you around soon!

Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Resuming landing of our upstream components on trusty: last steps

2013-10-23 Thread Didier Roche


Hey guys,

We're almost ready on resuming landing upstream components to trusty, 
most delays were due to late release name announcements impacting us in 
multiple ways.


So, normally, where are we? This morning we finished:
- ensuring that all cowboys upload to distro without using upstream 
trunk are put back in coherence
- investigating why add-apt-repository wasn't working (blocking 
automated testing in otto when daily-releasing): python-apt was 
unblocked and moved to the release.
- some starts of explanation why we can't access network (lxc reverted 
to alpha1 and hold until further investigation). This helps to get one 
of the 3 tests machines back on shape.


What's still blocking us before we resume landing components to distro 
(and so, to phone):
- it seems that the generic-medium tests in the upstream merger on 
desktop can't start. Can be a boostrapping issue. Under investigation by 
the infrastructure CI team
- the desktop tests (otto machines) still have an issue starting the 
container on 2 machines. This is under investigation by the 
infrastructure CI team as well.


Hope that then, we can resume landing work, through the already existing 
process.


Oh, and btw: we promoted image 3 in trusty which is the first "blessed" 
trusty phone image (mostly containing sync from debian changes).

Thanks,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing plan - Monday 4th November

2013-11-04 Thread Didier Roche


Hey everyone,

As you probably saw on the phone mailing list. We were finally available 
to promote a new trusty image #10 (the last pieces making unity8 not 
passing wasn't due to the image itself).
This image contains (from previous unpromoted ones) a lot application 
design adjustments as well as transitions from trusty itself.
We are getting a very good autopilot test pass rate: 96% on both mako 
and maguro.

We'll keep people on the stable channel on saucy until next week.

We kicked image #11 to check what the transition brought to us during 
the week-end. In the meantime, we are checking the remaining tests not 
passing (core apps for most of them).


As well, we prepare transitioning to autopilot 1.4, which is not 
backward compatible with 1.3. The plan is:
- on Tuesday, we will release all impacted components (~15 of them). 
Team leads are responsible, as discussed last week, to ensure their 
trunk is releasable by then. The impacted components are mostly apps, 
unity8 and sdk. I think balloon will coordinate the Core Apps side. 
Then, nothing enters those trunks anymore.
- end of Tuesday, we put autopilot 1.4, autopilot-gtk 1.4, autopilot-qt 
1.4 and xpathselect 1.4 in the daily-build ppa.
- Wednesday (NZ time): Thomi is going, with the QA team support, to 
merge every 1.4 branch in those cmoponents
- Wednesday (Europe time), we are going to release those and kick off an 
image.
- Finally, we'll give the green light to all upstreams telling that they 
are ready to merge back to those trunks against.


Thanks for your cooperation during this transition.

Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing plan - Tuesday 5th November

2013-11-05 Thread Didier Roche


So, we kicked off image 11.

Unfortunately, we can't release that image, seems that friends created a 
lot of system idling issue impacting the image itself. We reverted it.
We have hope image 12 is then going to fix this (the imports from debian 
and other distro uploads doesn't seem to have had any impact).


At the same time, we tried to prepare the autopilot 1.4 rollout 
mentionned yesterday, we released all components with 1.3 before the big 
jump: all apps, unity8, keyboard…
Unfortunately, it seems that the ubuntu-ui-toolkit wasn't releasable 
this morning (we have some AP tests failing). So everything is delayed 
(we have a fix now but need to certify it).


We have people monitoring this, then, they will flip on 
autopilot/autopilot-gtk/autopilot-qt and xpathselect 1.4. Thomi and the 
QA team will work on getting their AP 1.4 compatible branches in. 
Tomorrow, we'll try to release everything (only containing those 
changes, so please please, as already told, nobody merge anything on 
those branches) and be done.


Consequently, image #12 will be kicked in later on, as soon as the 
toolkit makes it in, and will have a lot of refreshed apps as a 
consequence :)


Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing plan - Wednesday 6th November

2013-11-06 Thread Didier Roche


Hey guys,

*In summary*: please do not merge anything yet to trunk if your 
component was part of the AP 1.4 transition.



crusty details:
Images 12 and 13 contains all the releases from yesterday.

We got some troubles to get good results, because one of the indicator 
was going crazy (and the name was truncated, so hard to know which one 
and no way to reproduce locally). We didn't find the culpurit after a 
long long fight (we tried reverting network-manager, ido, unity8, 
lxc-android-config...) The issue is that the results are really 
unreliable (60% of failures, but some long run passing without any 
changes). Right now, we added a longer system settling period and it 
wokaround sometimes the issue.


We'll need someone to dive into why we got that regression, which will 
be easier if we can reproduce it reliably first. Note that nobody was 
able to reproduce it locally. Mathieu and Ted are currently looking at 
why the indicator-network is looping like crazy in some cases on the 
device in the lab itself (as we can't find the culpurit and it's a fix 
needed anyway).


At the same time, we started to transition to autopilot 1.4. Most of the 
branches were merged this morning, but not everything and so we helped 
fixing that.
Certifying every changes locally, we already know that next dashboard 
will show:
- not all AP tests for autopilot passing on the device 
(https://launchpad.net/bugs/1211140)
- camera-app which was written to not needding any transition for AP 1.4 
has now 3 reliable test failures: 
https://bugs.launchpad.net/camera-app/+bug/1248495
- dialer-app have some tests failing as well: 
https://bugs.launchpad.net/dialer-app/+bug/1248553
- some core apps are still having some failures (before and after the 
1.4 compatible versions were getting uploaded). We also miss 
com.ubuntu.stockticker and com.ubuntu.sudoku needs to have the 1.4 
branch merged.
- unity7 is getting reviewed and merged before a rebuild without picking 
up latest nux and compiz (for ABI breakages)
- some components are blocked in proposed, the team is helping 
faciliting the transition.


Then, we'll start building image 14.

I think Julien, Thomi and the rest of the QA team is going to work very 
closely with all upstreams to get all failing AP tests resolved ASAP. I 
think we shouldn't push any other code to any project that won't get a 
100% pass rate on image 14 until those are fixed.
So please, all upstreams, look at 
http://reports.qa.ubuntu.com/smokeng/trusty/touch/, test results for 
image 14 (once available), and if your pass rate isn't at 100%, refrain 
to merge any new code into those components (or anything that can impact 
those) and work with the QA team so that we can come back to a green 
image ASAP.


Thanks,
Didier
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing plan (and good news!) - Thursday 7th November

2013-11-07 Thread Didier Roche


Hey guys,

Remember the indicator-network going crazy on startup yesterday and 
making most of AP failing? This is now history! Thanks Mathieu for the 
initiale debugging, psivaa to have hung up with me yesterday trying all 
sort of crazy things, Martin to find a reliable way to reproduce it and 
Lars to have find a quick way to fix it.
We now understand why it happened randomly, then everytime after a 
while. We found a way to workaround it without the fix to get test 
results ASAP.


So results on image 14 are the results with AP 1.4: 
http://reports.qa.ubuntu.com/smokeng/trusty/touch/
As we can see, it's a bit below than the previous image (particularly 
image 10).


You should already know that the CI infra is going to migrate over the 
week-end, I think it's then the perfect timing to go back to a green 
image. I suggest that we don't merge anything in trunk on the components 
that don't have 100% of tests passing (or anything in other components 
that may impact the other tests). Then, with the help of the QA team and 
psivaa, plars on the infrastructure side, try to look at what tests 
failed, why and please only merge fixes for it to have all AP tests 
passing in the next run.


So, I see the following responsability:
balloons: ubuntu-weather-app, ubuntu-terminal, ubuntu-rssreader, 
ubuntu-filemanager, calendar-app
bfiller: notes-app and mediaplayer-app. webbrowser-app has a fix flying 
in already! kudos to the apps team!


The real indicator-network and a webbrowser-app fix is coming through 
image 15.


SDK broke backward compatibility (not impacting what we were testing 
though) and consequently, we can't even consider releasing the current 
image because of that. I have high hope to get a fix in image 16.


Then, let's target to have image 16 with a 100% pass rate! Green is 
fashion, let's get that!

Cheers,
Didier

-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] system-image 2.0 is ready

2013-11-13 Thread Didier Roche


Le 13/11/2013 19:50, Barry Warsaw a écrit :

I think system-image 2.0 is ready for release, and would like to request a
landing slot.

https://launchpad.net/ubuntu-system-image/+milestone/2.0

This version fixes a ton of bugs.  Attached is the NEWS file excerpt.  I've
tested this new version locally and on my device and all seems happy.

The big one of course is LP: #1217098, where the cached data files will be
used if present and still valid.  This avoids re-downloading all the data
files if an update isn't applied until after system-image process suicide.

Since LP: #1215586 is not yet fixed in system-settings, I am pushing this off
to system-image 2.1.  This shouldn't be a show-stopper, since we haven't had
descriptions enabled in a while anyway.

Cheers,
-Barry


Excellent Barry!

With all our testing down (CI infra not available), I would love to wait 
for getting the first test results since last week before we start 
landing this one.
Also, can you please file the landing spreadsheet with those info (your 
manager can help you if you never did), and the testing that was 
conducted on the phone?


Thanks!
Didier




2.0 (2013-11-13)

  * Avoid re-downloading data files if previously download files are found and
are still valid (by checksum and gpg signature).  (LP: #1217098)
  * In the D-Bus API, `ApplyUpdate()` is changed from a synchronous method
returning a string to an asynchronous method not returning anything.
Instead a `Rebooting(bool)` signal is added with the value being the status
if the reboot operation (obviously, this signal isn't ever received if the
reboot succeeds).  (LP: #1247215)
  * Remove the old channels.json format. (LP: #1221843)
  * Remove support for old version numbers. (LP: #1220238)
  * Switch to nose2 as the test runner.  (LP: #1238071)
+ Add -P option to provide much nicer test pattern matching.
+ Add -V option to increase `systemimage` logging verbosity during tests
  (separate from nose2's own -v options).
  * Write the `ubuntu_command` file atomically.  (LP: #1241236)
  * Remove the unused `-u` and `--upgrade` switches.
  * Clarify that `--channel` should be used with `--build 0` to switch
channels. (LP: #1243612)
  * `--info` output will include the alias name if the current channel.ini has
a `channel_target` variable.
  * `--dry-run` output now includes channel switch information when an upgrade
changes the channel alias mapping.
  * Add a workaround for LP: #1245597, caused by a bug in
ubuntu-download-manager when presented with an empty download list.
  * If an existing image-master or image-signing key is found on the file
system, double check its signature (LP: #1195057) and expiration date (LP:
#1192717) if it has one, before using it.
  * If the winning path includes two URLs which map to the same local
destination file name, the download should fail.  (LP: #1250181)
  * Provide a bit more useful traceback in various places of the state machine
so that error conditions in system-image-cli make a bit more sense.
(LP: #1248639)
  * Tweak the scoring algorithm to highly discourage candidate upgrade paths
that don't leave you at the maximum build number.  (LP: #1250553)
  * When running system-image-cli under verbosity 1, print dots to stderr so
that the user knows something is happening.
  * Remove unused `state_file` setting from client.ini.




-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] Experimental Ubuntu Touch Emulator

2013-11-20 Thread Didier Roche


Le 20/11/2013 06:04, Ricardo Salveti de Araujo a écrit :

Hey,

Just to let you guys know that I just uploaded a new version of the
android package, containing the first experimental version of a
functional emulator (with UI), running Unity 8 and Mir.

Please follow the guide described at
https://wiki.ubuntu.com/Touch/Emulator if you want to give it a shot.
Also please check the known issues at the wiki page, as we don't yet
have everything enabled by default (e.g. apparmor and powerd are
currently disabled).

There's still a lot to be done, but this should be a good start :-)

Thanks,


Awesome Ricardo!

A word of warning though: if you are on amd64, take care if you 
uninstall the emulator and run apt-get autoremove to automatically clean 
the dependencies, this will break your system.

If you are in that case, a way to recover:
1. reboot and eventually press shift to get to grub
2. press e to edit your command line
3. on the line "linux <...>", remove "quiet splash" and replace with 
break=bottom
4. press F10 or Ctrl-x to start, you will be dropped in the initramfs 
busybox

5. mkdir /mnt
6. you need to know your FS layout and mount /dev/ 
in /mnt
7. cd /mnt/lib64/ && rm ld-linux-x86-64.so.2 && ln -s 
/lib/x86_64-linux-gnu/ld-2.17.so ld-linux-x86-64.so.2

8. reboot

I'm updating as we speak the wiki page with those infos

Thanks to infinity and jibel to have helped and tried in a vm while my 
system was broken

Cheers,
Didier
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] Experimental Ubuntu Touch Emulator

2013-11-20 Thread Didier Roche


Le 20/11/2013 12:19, Sam Segers a écrit :

Hi

Could you also add how to prevent this from happening?
Linking that same library after autoremove or reinstalling some package?


It seems to not be straightfoward (especially if you don't want to break 
precise->next LTS upgrade), but infinity is looking into it.
You can't just symlink in postrm as you can't even start ls, ln, rm due 
to the lack of libc6... :p




Thanks
Sam Segers


2013/11/20 Didier Roche mailto:didro...@ubuntu.com>>

Le 20/11/2013 06:04, Ricardo Salveti de Araujo a écrit :

Hey,

Just to let you guys know that I just uploaded a new version of the
android package, containing the first experimental version of a
functional emulator (with UI), running Unity 8 and Mir.

Please follow the guide described at
https://wiki.ubuntu.com/Touch/Emulator  if you want to give it a shot.
Also please check the known issues at the wiki page, as we don't yet
have everything enabled by default (e.g. apparmor and powerd are
currently disabled).

There's still a lot to be done, but this should be a good start :-)

Thanks,


Awesome Ricardo!

A word of warning though: if you are on amd64, take care if you
uninstall the emulator and run apt-get autoremove to automatically
clean the dependencies, this will break your system.
If you are in that case, a way to recover:
1. reboot and eventually press shift to get to grub
2. press e to edit your command line
3. on the line "linux <...>", remove "quiet splash" and replace
with break=bottom
4. press F10 or Ctrl-x to start, you will be dropped in the
initramfs busybox
5. mkdir /mnt
6. you need to know your FS layout and mount //dev// in /mnt
7. cd /mnt/lib64/ && rm ld-linux-x86-64.so.2 && ln -s
/lib/x86_64-linux-gnu/ld-2.17.so <http://ld-2.17.so>
ld-linux-x86-64.so.2
8. reboot

I'm updating as we speak the wiki page with those infos

Thanks to infinity and jibel to have helped and tried in a vm
while my system was broken
Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
<https://launchpad.net/%7Eubuntu-phone>
Post to : ubuntu-phone@lists.launchpad.net
<mailto:ubuntu-phone@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~ubuntu-phone
<https://launchpad.net/%7Eubuntu-phone>
More help   : https://help.launchpad.net/ListHelp






-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing task call 22.11.2013

2013-11-22 Thread Didier Roche


Hey guys,

After some days of excellent virtual UDS, we are back (but don't 
mislead, we didn't stop in the meantime ;))!
The CI infrastructure moved to 1ss has slow down what we could deliver 
the last couple of weeks. But we still did some good work (I'm 
summarizing the big noticeable changes in recent images below). The 
impacts from this move are now almost all fixed (still some small 
niggles to get to), but our velocity should be back to 100% starting 
next week!


Here are the big changes spinned in previous images:
Images 20 to 23 were regular snapshots taken from the distribution to 
take latest packages flying, mostly synced or merged from Debian (but at 
this time, we couldn't get test results due to the infra move, so just 
for dogfooding purpose).
Images 24 got latest and greatest from our sdk, fixing some recent 
regressions in backward compatibility. In addition, click apps are now 
able to load their translations at startup.
Images 25 and 26 have some fixes for serial console shell on android and 
bring ubuntu console support for the emulator. In addition, new 
system-settings for settings lover :)

Image 27 has seen a new Mir transition + click apparmor fixes.

We prepared as well the base layer to get latest unity8 to the archive 
with their new packages.


There are some issues we need to keep on the radar:
* dpkg changed recently its logic to fix the way it's handling 
debian/source/format. This created some issues in incorrect packages 
like autopilot-gtk. We are going through them and fixing that. However, 
upstream merger is expecting something else and we need to work with the 
CI team to fix the logic there.
* we fixed some latest quirks on the migration move for the CI 
infrastructure, we need to ensure that the fixes are working and there 
is not new areas of failures.
* it seems there is a GSM/Wifi regression on the phone. But it looks 
like being magically fixed on image 27 (not showing up anymore). We are 
kicking image 28 with click updates and some unrelated changes (archive 
changes) to see if we can still reproduce those disconnection issues.
* powerpc had some failures due to the toolchain changing, some packages 
needs to be rebuilt so that we can fix the failure to builds and get the 
indicators released (that will enable having some crashes fixed as well 
in saucy desktop)
* some components were uploaded manually to distro, we are 
reconciliating the branches


And here is where we are, the test results are better overall, but not 
stellar, working with the core apps team to ensure that we can go back 
to green and all fixes are merged and delivered!


Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing plan 25.11.12 special episode

2013-11-25 Thread Didier Roche


Hey guys,

Trusty image #28 is now available. \o/

Granted that we didn't promote an image for quite a few days/weeks, we had to 
resolve that situation.
Especially now that the CI infrastructure move is mostly over, everything is 
operational, great work guys!
Raring to deliver the new promoted image, we looked at the Unity8 crashes we 
saw in images 27 and 28, and we ensured it only happens on exit, so didn't 
impact user experience as itself.
Only fixing this crash will mean diving deep into Qt 5.0 while we are moving to 
Qt 5.2, and getting a reliable stacktrace is hard as the phone is shutting down 
before the debug collect is over.
Noting that the remaining autopilot test failures are false positives from the 
core applicaitons we ship, we confirm manually that they all work as expected.
In those terms, we decide that we can promote image 28 with a sense of 
proudness, knowing all the issues we encountered in the past few weeks.
Meanwhile, we still work on resuming landing more and more packages (Mir stack, 
autopilot, qtubuntu in the coming one for instance) to wake up the engine, and 
be on a fast path again.
On the coming days, you can expect to get promoted images in a way faster 
cadence, now that everything is up again.

Another goal is to have again all tests green, and we have the core apps team 
furiously working on that.
Green image again? "Allons-y!"

Maybe we'll already be there in the next couple of images, "who knows..."
Didier


*Vwrorrrp Vwrorrrp Vwrorrrp Vwrorrrp*

-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing plan for 26.11.13

2013-11-26 Thread Didier Roche


Hey guys,

So, we told that we were going to resume rapid image promotion, here we 
are, image #31  for your pleasure!
This image contains part of some transition, but was mostly focused on 
rapidly fixing regressions we discovered:
* indicators tab order not matching is fixed in the toolkit (thanks 
Florian, Tim + Robert P. and Ken for testing). A test is now in place to 
ensure we can catch more regressions on that side :)
* Unity8 crashing when stopping making the following reboot really 
really slow (while whoopsie is collecting the crash) is now fixed thanks 
to Gerry in unity-mir
* the webapps not opening the right urls on links is fixed and tested in 
upstart-app-launch thanks to Ted (and Timo to test/release it)
* Not really a regression, but the ubuntu-keyboard making annoying noise 
while using it is now patched to not making sound by default thanks to Bill
* Finally, I did a workaround based on Tiago's first inspection to fix 
the case when there was no GSM connexion (annoying for a phone ;)) if 
you don't connect first on a WLAN network. It seems to have fixed part 
of the issue in some cases, but wasn't the full story. Upstream did a 
proper fix which is landing right now (so in next image).


Image #31 has a comparable test pass rate than #28 and is now promoted 
and available on the trusty channel.


We will restart kicking an image for the real GSM fix as soon as the 
package is published and run all the autopilot tests again (but this 
takes some hours). We plan to promote that one as well tomorrow morning 
if the test results are good. The PhoneFundation team together with QA 
are going to write tests to cover the whole GSM area.


There is one issue that we are aware about (but this was already on 
image #28, hence why we didn't block the promotion on it): 
https://bugs.launchpad.net/mir/+bug/1255045. This one impacts maguro and 
has a workaround described in the bug itself. Dave helped ensuring that 
we found the right component triggering the issue and that was linked to 
the Mir releasing (so mir, platform-api, unity-mir). The Mir team is 
aware about it and we block any new Mir release on that bug fix.


Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing plan 27.11.13

2013-11-27 Thread Didier Roche


hey everyone,

We promoted image #32, knwon as "I will always get GSM when I boot up my 
phone" \o/
I guess that title said it all, we still have the traditional comparable 
test results as we have seen in the past few days.


Image #33 fixes some toolkit regressions released during the night 
(scrolling in list items)
Some work is going in making core apps a little bit more green, baloons 
and sergio are testing and releasing fixes one after another
We have some landed we prevented due to test failing or spotted 
regressions, work is going on to discuss directly with upstream to get 
them landed as soon as possible.
Mir is waiting on the 2 issues previously mentionned to be fixed in 
trunk to be released.


We also landed some new components like unity-voice and some new test 
stack to prepare the ground for even better and more excited releases.

Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing plan 28.11.12

2013-11-28 Thread Didier Roche


Hey guys,

While some part of the world is busy cooking turkey, other are working 
and furiously getting new ubuntu touch images out!

We built images 33, 34 and 35!

Those contains some toolkit regression fixes, click packages to get less 
failing tests as well as a lot of online accounts bug fixes.
However, we're still tracking some regressions (like no more AM/PM and 
date format going to 24 hours in the locale) as well as new found issue 
like keyboard not showing up anymore on locale different than English ( 
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1255999).


Also, it seems that the merge for 
https://bugs.launchpad.net/upstart-app-launch/+bug/1253703 didn't really 
fix the issue, so reopening it.
We are engaging seriously with upstreams to track down those issues and 
get them fixed.


The Mirs blockers are now gone and we are working on getting a new Mir 
stack + latest of Unity8 released!
Be ready for the incoming images, those are going to be rock and roll 
(but in the good sense) ;)


Cheers,
Didier
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 29.11.13

2013-11-29 Thread Didier Roche


Hey,

as this ML is busy, I'll just post a short resume of actions from today.
So, we get 3 images built since last email yesterday evening (36, 37 and 38)

No real progress due mostly to people eating turkey and other trolling*, 
but we still made packages in:
* a new whole Mir stack was landed gracefully now that the 2 issues have 
been fixed! Really nice.

* fix that, we benefit from the last 3 weeks of Unity8 fixes!
* phablet-tools is now shipping an utility to create screenshots
* autopilot-gtk to unblock the installer testing
* some minor fixes to get to a greener dashboard (but still work to be 
done though)


On the downside, we had a lot of crashes reported in this morning image 
(37) of network-manager due to new glib. The current glib fixing the 
issue is in trusty-proposed pocket. As soon as it's migrated in the 
release pocket, we'll kick image 39. We didn't hold the build of image 
38 (even if we know we can't promote it due to network-manager crash) to 
check for the new init-system-helpers impact.


So no Friday evening image promoted, but stay tuned after a wonderful 
week-end :)


Cheers,
Didier

*It's Friday after all ;)

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing call 2.12.12

2013-12-02 Thread Didier Roche


Hey everyone,

So, here are the news in the landing world those few days.
We got images 40 and 41 built, 42 is a little bit reluctant to have test 
running in the CI Infra (but that's normal, this image should be special 
;)).


We have frist the glib commit revert and can confirm that we have no 
more network-manager crashes :)

We had a new SDK release, some new indicator-power and apparmor changes.

In term of what needs to be investigated before being in position to 
promote the next image and ensuring we won't publish any new regressions:
- we see quite a lot of HUD crashes, upstream was poked about it. We try 
to nag them already so that they are going to fix it.
- we also have a bunch of qmlscene (so Qtdeclaractive) crashes when 
running the tests ( 
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1243665). 
Timo and the SDK team are looking at those.
- Notes-app is hanging a lot in the tests on mako and maguro. It happens 
that we have to restart the tests 3-4 times to finally get them working. 
This can be due to SDK or Qt, but it's better that we investigate right 
now to ensure that it's not something with a bigger impact. The 
unstoppable Bill's apps team is on it. 
(https://bugs.launchpad.net/notes-app/+bug/1256048)
- The same team is looking at the keyboard which doesn't show up at all 
if you are in a non english locale: 
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1255999



2 other issues are already in the published image, but it seems the 
Unity8 team won't have time to look at those before next week:
- indicators lost its 24h clock (and don't have AM/PM, which can even 
more puzzle european people ;)). 
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1256061. The 
unity8 team is assigned to it
- There is a random issue in the message display time showing them 
around the start of the year. The unity8 team is responsible to get a 
quick fix for it (the MP attached to it isn't sure to be fixing it) 
https://bugs.launchpad.net/unity8/+bug/1253810


The Core apps team, with Nicholas back, will be able to push and 
continue fixing more autopilot tests failures.


Finally, note that Dave found an issue making you not able to answer the 
phone call when you are called and the phone is at sleep in some 
circumstances ( https://bugs.launchpad.net/unity8/+bug/1257000). This 
one started after in a newer proposed image than latest promoted one and 
so, it's an image promotion blocker. The Unity 8/Mir team have been 
poked with those info.


Here is for today, a big list of work to push within your team guys!
Cheers,
Didier
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing call 3.12.13

2013-12-03 Thread Didier Roche

Hey,

So, it seems that image 42 wasn't the answer to everything, it even
never showed up on the result dashboard. We kicked images 43 without any
change to get some tests results.

Image 44 contains some ofono changes and 45 enables Nexus 10 running on
Mir \o/ Nice work guys! We also got new components like unity-voice into
the archive.
The tests results are a little bit better than usual, but we are still a
little blocked by some regression (the last one in yesterday email).
Let's recap the progress first.

- we see quite a lot of HUD crashes, upstream was poked about it. We
try to nag them already so that they are going to fix it.
Lukasz retraced it and passed those information upstream:
https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1253676. Pete is
working on it.
- we also have a bunch of qmlscene (so Qtdeclaractive) crashes when
running the tests (
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1243665).
Timo and the SDK team are looking at those.
Greyback and Ted are synchronizing and it needs some work is needed in
upstart-app-launch to fix this race condition.

- Notes-app is hanging a lot in the tests on mako and maguro. It
happens that we have to restart the tests 3-4 times to finally get
them working. This can be due to SDK or Qt, but it's better that we
investigate right now to ensure that it's not something with a bigger
impact. The unstoppable Bill's apps team is on it.
(https://bugs.launchpad.net/notes-app/+bug/1256048)
The apps team tried a fix, but it needs to pass CI (tests are not
running properly now) to get delivered.

2 other issues are already in the published image, but it seems the
Unity8 team won't have time to look at those before next week:
- indicators lost its 24h clock (and don't have AM/PM, which can even
more puzzle european people ;)).
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1256061. The
unity8 team is assigned to it

No news on that one.
- There is a random issue in the message display time showing them
around the start of the year. The unity8 team is responsible to get a
quick fix for it (the MP attached to it isn't sure to be fixing it)
https://bugs.launchpad.net/unity8/+bug/1253810

No news on that one as well.

The Core apps team, with Nicholas back, will be able to push and
continue fixing more autopilot tests failures.

Alan did an excellent job getting
https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AnZdnhOl8MU5dFhvQklYVXdwRjR6VFoxN3pSZFRrN3c#gid=0
ready to be able to track failing AP tests.

Finally, note that Dave found an issue making you not able to answer
the phone call when you are called and the phone is at sleep in some
circumstances ( https://bugs.launchpad.net/unity8/+bug/1257000). This
one started after in a newer proposed image than latest promoted one
and so, it's an image promotion blocker. The Unity 8/Mir team have
been poked with those info.

I heard that one is under investigation.

We are kicking image 46, containing the new system image 2.0 version.
Enjoy,
Didier
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] Landing call 3.12.13

2013-12-04 Thread Didier Roche


Le 03/12/2013 20:26, Oliver Grawert a écrit :

hi,
On Di, 2013-12-03 at 14:06 -0500, Rick Spencer wrote:

Seems like with everything moving we are having a hard time getting a
good image out. Any thought to stopping changes that don't address the
blockers until we get a good image?

with everything stopped it means that changes start to pile up and we
end up getting gigantic change sets which then makes it hard to identify
a single breakage in a landing ...

we should put our focus indeed on the main blockers, but should still go
on landing stuff that is not actually related to the current issues and
check it so we can make sure it does not interfere or introduce new
breakage. the blockers usually only have one or two specialists that can
fix them which produces an artificial bottleneck for all of us if we
stop all unrelated landings because of them.

lets go on as we do and simply see that we can put as much focus onto
the blockers as possible, but lets not block unrelated landings for
this.

getting a better automated testing infrastructure and more dogfooders
that also find the corner cases appears more intresting than just
blocking the whole world for something that can only be fixed by a small
fraction of the team imho ...


Knowing that it seems we'll only get the 2 Unity8 fixes next week as the 
specialist isn't available this week. But those 2 are not blockers, just 
high priority bugs worth mentioning IMHO as regressing (but already in 
promoted image).


However, we ensure that we won't get any new release without a fix in 
components that have a blocker bug (so no Unity8 release before the bugs 
are fixed for instance).


Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] Landing call 3.12.13

2013-12-04 Thread Didier Roche


Le 04/12/2013 10:20, Tomas Ö a écrit :
I know you guys have your hands full to say the least, and I 
appreciate the hard work you put into this, but as a "private 
dogfooder" (Nexus 4) since mid October it would be nice to see some 
kind of roadmap regarding a couple of really important issues from a 
usability perspective:

1) When do you expect working bluetooth?
2) Automatic two-way synchronization with Google contacts/calendar?
3) Plans for an e-mail client that can handle multiple accounts?
4) Working MMS?
5) Fix for the browser lagginess? Due to the lack of apps, UT users 
have to rely on the browser for many things. For me, the usefulness of 
the browser is severely hampered by the fact that it takes 7 seconds 
to bring up the Activities panel and another 7 seconds to open the 
Bookmarks panel. Including load times, I usually have to wait closer 
to 20 seconds to view a bookmarked page.

6) The ability to listen to music with the screen off?

Again, I really appreciate the commitment and hard work many of you 
put into this project and I will gladly assist in making UT better if 
I can. I can live with occasional crashes and some of the bugs, but I 
would really like to know when you think the issues above will be 
resolved?




Hi Tomas, I don't have the exact details on those, but some of your 
questions were discussed at least vUDS ( 
http://summit.ubuntu.com/uds-1311/). You can access to the videos of the 
session. For the others, some were already discussed (but no ETA as far 
as I know) like Google contacts synchronization. Maybe worth that you 
open new threads on this mailing list?


Remember that there is as well #ubuntu-touch on freenode to be able to 
contribute to the projects (and get your feedback/regressions that you 
can spot)


Thanks a lot for your dogfooding effort ;)
Didier
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing call 4.12.13

2013-12-04 Thread Didier Roche

Hi,

We got some progresses through images 46 and 47 today and the pass rate
is slowly improving. Let's keep that trend up!
Image 46 contained a new initramfs and mostly unspecific touch changes
coming directly from the distro work.
Image 47 got a Qt declarative fix in the QEvent area (heavily tested
before delivered) and the keyboard fix (more info below). Tests are
still running at this moment on that one (even if image was kicked 6
hours ago).
The most noticeable news thanks to the keyboard fix is that you can
finally got some fancy azerty keyboard (as we should all have) depending
on your language settings, and apparently some umlaut for other weird
dialects. ;)

- we see quite a lot of HUD crashes, upstream was poked about it.
(https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1253676)
-> This one is now fixed in trunk and the delivery is in progress (in
proposed right now!). Should be in the soon-to-be-kicked image 48.

- we also have a bunch of qmlscene (so Qtdeclaractive) crashes when
running the tests (
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1243665).
Timo and the SDK team are looking at those.
Greyback and Ted are synchronizing and it needs some work is needed in
upstart-app-launch to fix this race condition.

-> This is still under discussion and seems an upstart-app-launch issue.
This one is a blocker to promote an image. Thomas' team is working on
it, but couldn't get feedback on it.

- The same team is looking at the keyboard which doesn't show up at
all if you are in a non english locale:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1255999
Some investigations were done, and it seems libpinyin needs to contain
one. Dmitrijs is the new lucky owner :)
-> Thanks Dmitrijs for this fix! The keyboard is now available back on
ubuntu touch in non english settings. I think that would be a nice
candidate for an integration test. Julien, can you coordinate the needed
team to write a test on that one?

No news on that one as well.

No news, it seems the person able to fix it won't be around until next week.

The Core apps team, with Nicholas back, will be able to push and
continue fixing more autopilot tests failures.

Alan did an excellent job getting
https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AnZdnhOl8MU5dFhvQklYVXdwRjR6VFoxN3pSZFRrN3c#gid=0
ready to be able to track failing AP tests.

We got some excellent progress on that one. Can't wait for Sergio to
build the click apps for the filemanager app fixes coordinated by
Nicholas and Alan merged. This should drastically raise our pass rate!

I heard that one is under investigation.

Seems some progress and maybe link on an older bug (
https://bugs.launchpad.net/unity-mir/+bug/1234538). But this time, it's
not random. I still keep it on the blocker list and people are
discussing on the bug.

Another regression was found since last promoted image:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1257493. I put
that one on the promotion blocker list as well.

While we slow down the touch integration work, we are working on
releasing some desktop-only apps meanwhile, less risky for the image,
while we are waiting eagerly on the blocker fixes. ;)
So, good progress today, let's hope we see the same trend in all teams
tomorrow.

Cheers,
Didier
--
Mailing list: https://launchpad.net/~ubuntu-pho

[Ubuntu-phone] Landing call 5.12.13

2013-12-05 Thread Didier Roche


Hey everyone,

So, good news! We finally got the HUD (some tests failures on arm64 made 
it hard to enter distro), we can confirm on image 49 (tests running) 
that it's not crashing anymore. One less blocker!. We also have a way 
better pass rate (95% on mako) thanks to the test fixes coming in from 
the Core apps team!
One the positive news, notes-app is confirmed to not randomly stuck at 
tests anymore. Well done!


We have system-image 2.0 which should be finally unblocked from 
-proposed and will get in as well as other unrelated landings 
(telepathy-ofono and mtp) which are waiting.


However, we still have some blockers for the image promotion:
* qmlscene crash 
(https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1243665) 
+ some apps not showing randomly (and reliably for the dialer app when 
receiving a phone call): https://bugs.launchpad.net/unity8/+bug/1257000. 
Upstart-app-launch fix seems to not be trivial. We still hope for a fix 
before EOD.
* We'll have to make a full Unity8 release landing to get the fix for 
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1257493 (another 
blocker). This release is pending a late merge proposal to get it in a 
releasable state. The landing team will land it as soon as it's ready.


The other Unity8 issues are still stalled until next week, but they are 
not blocking the image promotion.


Let's cross fingers for tomorrow.

Cheers,
Didier
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing call 6.12.13

2013-12-06 Thread Didier Roche


Hey,

So, we are nearly there, but first, let's talk about images. Image 50 
has been kicked out with the latest from the archive. This one contains 
notably some telephony fix to be able to receive SMS from special 
numbers. Tests results were especially good on image 49 (94.8% on mako 
and 96.5% on maguro), image 50 tests are still running, let's cross 
fingers! You are as well able to rename files through mtp :)


We are blocking any new submission like the toolkit update that was 
requested and had as well to kick back some merge proposals made to 
trunk on the components we need to land. This is only to focus on being 
able to promote the next image as soon as possible and it seems very 
doable now. :)


Indeed, on the promotion blockers:
* qmlscene crash 
(https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1243665) 
+ some apps not showing randomly (and reliably for the dialer app when 
receiving a phone call): 
https://bugs.launchpad.net/unity8/+bug/1257000. Upstart-app-launch fix 
seems to not be trivial. We still hope for a fix before EOD.
-> We had a couple of hours ago the fix committed to trunk in 
upstart-app-launch. However, it is an API and ABI breakage and so, we 
are coordinating the landings of the reverse dependencies: unity-mir, 
content-hub as well as url-dispatcher. We just cherry-pick the fix for 
some projects where we are not confident with trunk state itself. All 
those builds/merges are happening as we speak + the qualification of the 
bug fixes before publication to the archive.


* We'll have to make a full Unity8 release landing to get the fix for 
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1257493 (another 
blocker). This release is pending a late merge proposal to get it in a 
releasable state. The landing team will land it as soon as it's ready.


-> The late merge proposal finally got it in the start of this 
afternoon, Unity8 is built and autopilot tests for all components are 
now run. So far so good, let's hope we can release it then.


As soon as those 2 batch of fixes are merged in, we plan to kick an 
image build and let the infrastructure do its test magic (so, an 
additional 6-8 hours). This image should then confirm that we are good 
for promotion again. Looking at the time of the day, the promotion will 
surely happen (if results are good) on Monday morning to not risk a bad 
week-end touch image.


We're near there, let's keep it up!
Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing call 9.12.13

2013-12-09 Thread Didier Roche


Hey,

Let's keep it short,
we had multiples images kicked by a cron job this week-end, containing 
mtp fixes to get better adb stability, and so, better in term of our 
testing.


The tests results shows that, we are at ~95% of test passing!

We still fought due to an "ust" ABI transition + a new dependency on it 
of the upstart-app-launcher dragging unity-mir, content-hub and 
url-dispatcher being stuck in proposed (because of not being able to 
build anymore on arm64 due to that new build-dependency). It took the 
day to be able to track/fix it (both ABI transitions and dependencies). 
The latest touch image containing those fixes just finished to build and 
now, we have several hours of integration tests running + some dogfooding.


We know that https://launchpad.net/bugs/1258655 is an existing bug way 
easier to trigger since we have latest unity8. I proposed as seeing the 
test case to not block promotion on it, but having the unity8 team 
focusing on it as well as the other 2 bugs that was listed the past days.


Let's cross fingers that image #55 will be the new promoted one tomorrow 
morning.


Then, we can resume normal landings.
Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 10.12.13

2013-12-10 Thread Didier Roche


Hey everyone.

Good news first:
the qmlscene crash and a lot of other bugs while opening the apps are 
now fixed. A consequence is also that the test pass rate jumped above 
98% as the whole system is way more reliable! Well done everyone. :)


Bad news: image #55 couldn't be promoted because of a regression where 
updated phones to latest image can't install or upgrade click apps ( 
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1259253). Colin 
fixed the issue and image #57 with it is now built. Tests are running as 
we speak and we'll be able to take a decision on its promotion with 
those results.


Even if the impressive yearly light festival in my city just ended 
yesterday[1], I'll put some candles tonight on the windows as per 
tradition[2] so that image #57 will finally be THE promoted image :)



Now, to move on to the future (assuming we are getting there) on the 
going green story.
As we are really close to our target of 100% of tests reliably passing 
and there is not anymore any known "can't launch app" blockers, it's 
time to look at getting all flaky tests disabled or fixed. It's 
completely reachable to get that green for Thursday I guess. If you 
can't fix a test that is flaky, the test is useless, so please disable 
it: it's just bringing noise to people trying to release an image.


Here is project by project list. Note that I based it on both images 55 
and 56 test results.


I count those as blockers for those projects to get a new release to 
Touch until the fix is in or another guilty component is identified:


* ubuntu-ui-toolkit (Zoltan):
One flaky test (fail on maguro, not on mako)
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/55:20131209.1:20131203/5355/ubuntu-ui-toolkit-autopilot/559350/

* ubuntu-weather-app (Nicholas):
One test failing on both platform
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/55:20131209.1:20131203/5355/ubuntu-weather-app-autopilot/559254/
http://ci.ubuntu.com/smokeng/trusty/touch/mako/55:20131209.1:20131203/5356/ubuntu-weather-app-autopilot/559437/

* ubuntu-file-manager (Nicholas):
One flaky test on mako
http://ci.ubuntu.com/smokeng/trusty/touch/mako/55:20131209.1:20131203/5356/ubuntu-filemanager-app-autopilot/559266/

* music-app (Nicholas):
One flaky test on mako
http://ci.ubuntu.com/smokeng/trusty/touch/mako/55:20131209.1:20131203/5356/music-app-autopilot/559105/

* calendar-app (Nicholas):
4 flaky tests failing on maguro. Maybe will worth a look to see if 
something didn't disturb the environment and it's not protected against it.

http://ci.ubuntu.com/smokeng/trusty/touch/maguro/55:20131209.1:20131203/5355/calendar-app-autopilot/

* terminal-app (Nicholas):
Enter and backspace broken in terminal: 
https://bugs.launchpad.net/ubuntu-terminal-app/+bug/1257791


* messaging-app (Bill):
One flaky test on mako. (can be sdk related)
http://ci.ubuntu.com/smokeng/trusty/touch/mako/55:20131209.1:20131203/5356/messaging-app-autopilot/558958/

* notes-app (Bill)
One test failing on both mako and maguro:
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/55:20131209.1:20131203/5355/notes-app-autopilot/558827/
http://ci.ubuntu.com/smokeng/trusty/touch/mako/55:20131209.1:20131203/5356/notes-app-autopilot/558857/
3 flaky tests on mako:
http://ci.ubuntu.com/smokeng/trusty/touch/mako/56:20131210:20131203/5360/notes-app-autopilot/

* webbrowser-app (Bill)
2 flaky tests on maguro only:
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/56:20131210:20131203/5363/webbrowser-app-autopilot/

* unity8 (Kevin)
5 flaky tests on maguro:
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/55:20131209.1:20131203/5355/unity8-autopilot/558729/ 
(1 fail on run 55)
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/56:20131210:20131203/5363/unity8-autopilot/ 
(4 other failures on run 56)
In addition, remember that Unity 8 has a backlog of pending fixes that 
were waiting for this week. I count them as well as blockers for 
releasing unity8. Meaning:
- messages in Incoming not always display the correct date and content ( 
https://bugs.launchpad.net/unity8/+bug/1253810)
- Abort when blancking/unblanking blank screen: old crasher that is now 
really easy to reproduce ( 
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1258655)


* qtubuntu (Kevin)
- clocked switched to 24h format ( 
https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1256061) -> 
seems that was unassigned and set back to the qtubuntu pool.


I'll appreciate if all people listed here communicate the progress on 
those issues in this mailing list. That would make a way easier 
coordination.


Thanks to everyone for their cooperation :)
Didier

[1] http://www.fetedeslumieres.lyon.fr/EN_2013
[2] 
http://www.fetedeslumieres.lyon.fr/documents/lyon_et_la_lumiere/LumignonsColores.jpg
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://

Re: [Ubuntu-phone] Landing team 10.12.13

2013-12-11 Thread Didier Roche


Le 11/12/2013 10:20, Tomas Ö a écrit :
I just checked for updates on my Nexus 4 and I got r33!? I thought we 
were waiting for r58 to be promoted?




It's part of the issue we are facing right now.

The latest image has been labeled image 33 when promoting, but the 
content is image 57 (which is the one we wanted to promote). So 
content-wise, you have latest and greatest, just the label isn't 
reflecting the reality (seems it's a feature though, but I clearly think 
that feature brings confusion to multiple people, us included ;)).


In short: if you upgrade, don't pay attention to the version, you will 
have the latest image.


Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] Landing team 10.12.13

2013-12-11 Thread Didier Roche

Le 11/12/2013 12:38, Olivier Tilloy a écrit :

* notes-app (Bill)
One test failing on both mako and maguro:

http://ci.ubuntu.com/smokeng/trusty/touch/maguro/55:20131209.1:20131203/5355/notes-app-autopilot/558827/

http://ci.ubuntu.com/smokeng/trusty/touch/mako/55:20131209.1:20131203/5356/notes-app-autopilot/558857/
3 flaky tests on mako:

http://ci.ubuntu.com/smokeng/trusty/touch/mako/56:20131210:20131203/5360/notes-app-autopilot/

I am able to reproduce the failure on maguro, although not reliably.
It’s being looked at.
I don’t have a nexus 4 handy to look into the failures on mako,
unfortunately.

Does anyone on your team have a nexus 4? As it seems to be flacky and
not being reliably reproducible, looking at the code can help already to
see if a race happened.

* webbrowser-app (Bill)
2 flaky tests on maguro only:

http://ci.ubuntu.com/smokeng/trusty/touch/maguro/56:20131210:20131203/5363/webbrowser-app-autopilot/

Looks like this one has been re-run, it’s all green now. The
webbrowser-app tests have been green for weeks (if not months) in a
row. Do we have access to the logs of the previous run (with the two
failures you’re mentioning)?

Argh, I did ask to not rerun the test to the CI team. I'll reash it.
Webbrowser-app is flaky for quite some time, but the CI team generally
rerun the tests, that's why you did see it green for weeks/months in a
row. For instance, here is on image 57 webbrowser with a lot of failing
tests:
http://ci.ubuntu.com/smokeng/trusty/touch/mako/57:20131210.1:20131203/5375/webbrowser-app-autopilot/.
Would be interesting to know the root case, it seems something is
screwed at some point, and then all tests are failing, can you have a
look at that case and try to be more robust? (or pass to the CI team if
it's an infra issue).

Thanks!

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Ubuntu touch images - 11.12.13

2013-12-11 Thread Didier Roche


Hey,

On this  11.12.13 day, we not only promoted one image, but 2! \o/
I think, this deserves http://i.imgur.com/kj6bgw5.jpg ;)

Welcomed to images #57 and #58. Note that due to some technology 
difficulties, we had image #57 labeled as image #33 (but with the right 
content). Everyone should be able to upgrade to image #58 now which has 
even a better pass rate.


This contains mostly ubuntu direct uploads with qt and lxc fixes.

We can now resume regular landing with image #59, containing:
- some fixes to support blocked/hidden/unknown calls and sms messages
- support for new scopes framework (not used by default though)

And we already had a regression from it! Spotted quickly, the guilty was 
unity-scopes-shell. We found the commit from the changelog and a revert 
is on its way.
I guess an action to reintroduce the commit is to get an integration 
tests, launching a click apps from the scope (we have none with those as 
of today).



So, image #60 and following will contain:
- revert to  be able to launch click apps from the scope :)
- latest libhybris snapshot to communicate with the android side
- ofono: improved support like multi-party phone calls and sms 
notifications.

- latest friends with minor bug fixes
- click packages updates for some of the failing autopilot tests \o/

On the going green side, here is the current status (pasting from 
yesterday):


* ubuntu-ui-toolkit (Zoltan):
One flaky test (fail on maguro, not on mako)
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/55:20131209.1:20131203/5355/ubuntu-ui-toolkit-autopilot/559350/
-> No information on that one

* ubuntu-weather-app (Nicholas):
One test failing on both platform
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/55:20131209.1:20131203/5355/ubuntu-weather-app-autopilot/559254/
http://ci.ubuntu.com/smokeng/trusty/touch/mako/55:20131209.1:20131203/5356/ubuntu-weather-app-autopilot/559437/
-> Fix getting delivered by Sergio on the click side

* ubuntu-file-manager (Nicholas):
One flaky test on mako
http://ci.ubuntu.com/smokeng/trusty/touch/mako/55:20131209.1:20131203/5356/ubuntu-filemanager-app-autopilot/559266/
-> Fix getting delivered by Sergio on the click side

* music-app (Nicholas):
One flaky test on mako
http://ci.ubuntu.com/smokeng/trusty/touch/mako/55:20131209.1:20131203/5356/music-app-autopilot/559105/
-> Fix waiting for dev approval

* calendar-app (Nicholas):
4 flaky tests failing on maguro. Maybe will worth a look to see if 
something didn't disturb the environment and it's not protected against it.

http://ci.ubuntu.com/smokeng/trusty/touch/maguro/55:20131209.1:20131203/5355/calendar-app-autopilot/
-> Seems Nicholas can't reproduce it, I think it's still under 
investigation, right?


* terminal-app (Nicholas):
Enter and backspace broken in terminal: 
https://bugs.launchpad.net/ubuntu-terminal-app/+bug/1257791

-> Nicholas pinging desperatly developers on that one :)

* messaging-app (Bill):
One flaky test on mako. (can be sdk related)
http://ci.ubuntu.com/smokeng/trusty/touch/mako/55:20131209.1:20131203/5356/messaging-app-autopilot/558958/
-> Seems some lead on a workaround implemented already in 
ubuntu-ui-toolkit (which doesn't work anymore)?


* notes-app (Bill)
One test failing on both mako and maguro:
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/55:20131209.1:20131203/5355/notes-app-autopilot/558827/
http://ci.ubuntu.com/smokeng/trusty/touch/mako/55:20131209.1:20131203/5356/notes-app-autopilot/558857/
3 flaky tests on mako:
http://ci.ubuntu.com/smokeng/trusty/touch/mako/56:20131210:20131203/5360/notes-app-autopilot/
-> it's been looked at. Need the team to advance on mako though (see 
discussion on previous thread)


* webbrowser-app (Bill)
Replacing with 
http://ci.ubuntu.com/smokeng/trusty/touch/mako/57:20131210.1:20131203/5375/webbrowser-app-autopilot/ 
(as previous link was invalidated it seems)
-> been looked at by devs as well as the CI team to see if it's an 
infrastructure issue.


* unity8 (Kevin)
5 flaky tests on maguro:
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/55:20131209.1:20131203/5355/unity8-autopilot/558729/ 
(1 fail on run 55)
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/56:20131210:20131203/5363/unity8-autopilot/ 
(4 other failures on run 56)
In addition, remember that Unity 8 has a backlog of pending fixes that 
were waiting for this week. I count them as well as blockers for 
releasing unity8. Meaning:
- messages in Incoming not always display the correct date and content ( 
https://bugs.launchpad.net/unity8/+bug/1253810)
- Abort when blancking/unblanking blank screen: old crasher that is now 
really easy to reproduce ( 
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1258655)
-> They are all under work, and some tests will be disabled on maguro as 
the issue will never be fixed on that hardware.


* qtubuntu (Kevin -> Zoltan)
- clocked switched to 24h format (

[Ubuntu-phone] ubuntu touch image 12.12.13

2013-12-12 Thread Didier Roche


hey,

We had 3 images built (60, 61 and 62). Unfortunately, we only have full 
test results on maguro and mako on the latest image. The test results 
seem descent.
However, dogfooding on maguro seems to have revealed that GSM and sms 
don't work anymore for Dave. The QA team is looking at that through Dave 
right now with upstream to try first to reproduce/understand what 
happens (they don't get it on maguro). That's why we didn't promote it.


They contain:
- ofono changes that maybe impact the GSM failure on maguro as the 
change that was related and it's crashing 
(https://launchpad.net/bugs/1260388).

- the revert on the scope to launch click apps
- new friends and some autopilot tests fixes
- system-image v2 which finally got out of -proposed \o/

Let's talk about the going green now, trying to summarizing the diverse 
exchanges that happened on the mailing list in different threads:


* ubuntu-ui-toolkit (Zoltan):
One flaky test (fail on maguro, not on mako)
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/55:20131209.1:20131203/5355/ubuntu-ui-toolkit-autopilot/559350/
-> Zoltan confirmed the new failure and he's working with the QA team to 
get them fixing it. Seems a fix is proposed: 
https://code.launchpad.net/~kalikiana/ubuntu-ui-toolkit/eventuallyCompareText2/+merge/198750 



* ubuntu-weather-app (Nicholas):
-> released and in image 60. However image 62 is still showing 3 
failures on both mako and maguro:

http://ci.ubuntu.com/smokeng/trusty/touch/mako/62:20131212.1:20131211.2/5420/ubuntu-weather-app-autopilot/
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/62:20131212.1:20131211.2/5423/ubuntu-weather-app-autopilot/
-> back to Nicholas I guess ;)

* ubuntu-file-manager (Nicholas):
-> Fixed!

* music-app (Nicholas):
One flaky test on mako
http://ci.ubuntu.com/smokeng/trusty/touch/mako/55:20131209.1:20131203/5356/music-app-autopilot/559105/
-> Fix waiting for dev approval

* calendar-app (Nicholas):
4 flaky tests failing on maguro. Maybe will worth a look to see if 
something didn't disturb the environment and it's not protected against it.

http://ci.ubuntu.com/smokeng/trusty/touch/maguro/55:20131209.1:20131203/5355/calendar-app-autopilot/
-> Seems Nicholas can't reproduce it, I think it's still under 
investigation, right?

-> would appreciate knowing progress on that one.

* terminal-app (Nicholas):
Enter and backspace broken in terminal: 
https://bugs.launchpad.net/ubuntu-terminal-app/+bug/1257791
-> seems that it's not terminal-app related (jdstrand reproduce it with 
an older version of the terminal app). Nicholas, can you work on 
figuring out where the issue relies?


* messaging-app (Bill):
One failure test on mako
http://ci.ubuntu.com/smokeng/trusty/touch/mako/55:20131209.1:20131203/5356/messaging-app-autopilot/558958/
-> So, Martin mentioned, it's not a flaky test, but a flaky behavior and 
the bug is real. I think the discussion is continuing to figure out 
where the issue lies?


* notes-app (Bill)
One test failing on both mako and maguro:
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/55:20131209.1:20131203/5355/notes-app-autopilot/558827/
http://ci.ubuntu.com/smokeng/trusty/touch/mako/55:20131209.1:20131203/5356/notes-app-autopilot/558857/
3 flaky tests on mako:
http://ci.ubuntu.com/smokeng/trusty/touch/mako/56:20131210:20131203/5360/notes-app-autopilot/
-> Some fixes went in, but there are still 2 failures while Alan 
released the app in the click store. Upstream team pinged about them 
(but we should already be in a better test)


* webbrowser-app (Bill)
Replacing with 
http://ci.ubuntu.com/smokeng/trusty/touch/mako/57:20131210.1:20131203/5375/webbrowser-app-autopilot/ 
(as previous link was invalidated it seems)
-> The apps team thinks the issue is due to something else that 
webbrowser app. I saw Thomi was pinged on it as it's linked to the apps 
not being launched/not being recognized as being launch, Thomi, can you 
shed some light on this (even maybe adding more debugs I guess)?


* unity8 (Kevin)
5 flaky tests on maguro:
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/55:20131209.1:20131203/5355/unity8-autopilot/558729/ 
(1 fail on run 55)
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/56:20131210:20131203/5363/unity8-autopilot/ 
(4 other failures on run 56)
-> Kevin told that all those issues are due to screen locking. A fix in 
the test to ensure the screen is unlocked is now merged in trunk: 
https://code.launchpad.net/~saviq/unity8/helper-retry-unlock/+merge/198648 
. 
The developers still can't reproduce it locally, but worse case, we'll 
have more debug infos on why it failed.


In addition, remember that Unity 8 has a backlog of pending fixes that 
were waiting for this week. I count them as well as blockers for 
releasing unity8. Meaning:
- messages in Incoming not always display the c

[Ubuntu-phone] ubuntu touch image 13.12.13

2013-12-13 Thread Didier Roche

Hey,

I realized late in the day that it was Friday 13th. But I guess today
really represented the legend of unluckiness :)

On image #63:
- we notably had, among other changes from distro some click packages
fixes (music, notes and weather) to fix some AP issues! However, weather
had an issue in its tests, making them all failing on mako and maguro (a
missing function called in setUp(), this clearly couldn't pass). Seems
we need to add some more tools to ensure that the testing environment
that people run manually is really testing what you have installed as it
seems to have passed the testing phase of 3 different persons. ;)

On image #64:
- we had unity8, but missing the qmenumodel part. So published it early
this morning. The unity8 + qmenumodel (with some delay due to a new arch
enabled on launchpad, but with more harness to protect against it now)
upload is fixing quite a lot of AP test failures (more safety
prevention) as well as the race in messaging
https://bugs.launchpad.net/unity8/+bug/1253810. Nice!
- the ofono regression (race which will get you without GSM/sms) was
thought to be due to a missing lxc-android-config upload, published
early this morning as well. However, it seemed in the end that the real
fix was needed in ofono (the other change was still needed in the long
term to activate the new features though). The ofono fix from Tony was
reviewed and uploaded by Ricardo. So fixed in that image!
- we reverted in the click store the weather app version to get back to
one where the tests can run.

However, on that image, we had a blocking issue. On the next upgrade,
you would have seen an error message before reboot:
https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1260712.
This is due to a change in the service API without the needed UI change
(the API change was discussed on that ML, but nobody had the time to do
the UI work and nothing in the system-image package prevented it to go
in without the UI adaptation). So a quick hacky fix was done and
uploaded. However, we missed the promotion of image #64 because of that
one, the dogfood test results were good though.

Image #65:
This is the currently in testing image with the system-image fix. We
cross fingers that no other regression will come in and will block us
for promoting (however, the results will arrive late).

Now, on the going green:
* ubuntu-ui-toolkit (Zoltan):
One flaky test (fail on maguro, not on mako)
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/55:20131209.1:20131203/5355/ubuntu-ui-toolkit-autopilot/559350/
-> The proposed fix is merged:
https://code.launchpad.net/~kalikiana/ubuntu-ui-toolkit/eventuallyCompareText2/+merge/198750

-> we are waiting for a landing ask on a well tested ubuntu-ui-toolkit
version.

* ubuntu-weather-app (Nicholas):
-> released and in image 60. However image 62 is still showing 3
failures on both mako and maguro:

http://ci.ubuntu.com/smokeng/trusty/touch/mako/62:20131212.1:20131211.2/5420/ubuntu-weather-app-autopilot/
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/62:20131212.1:20131211.2/5423/ubuntu-weather-app-autopilot/
-> we already talked about the regression making all tests failing on
image 63 and the revert to the image 62 weather app version. It seems a
fix is under review:
https://code.launchpad.net/~nskaggs/ubuntu-weather-app/fix-rev164-test/+merge/198955.

* music-app (Nicholas):
Less flacky with latest version, but still getting randomely:
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/63:20131213:20131211.2/5429/music-app-autopilot/568784/

* calendar-app (Nicholas):
4 flaky tests failing on maguro. Maybe will worth a look to see if
something didn't disturb the environment and it's not protected against it.

http://ci.ubuntu.com/smokeng/trusty/touch/maguro/55:20131209.1:20131203/5355/calendar-app-autopilot/
-> Seems Nicholas can't reproduce it, I think it's still under
investigation, right?

-> would appreciate knowing progress on that one.

* terminal-app (Nicholas):
Enter and backspace broken in terminal:
https://bugs.launchpad.net/ubuntu-terminal-app/+bug/1257791
-> seems that it's not terminal-app related (jdstrand reproduce it with
an older version of the terminal app). Nicholas, can you work on
figuring out where the issue relies?

* messaging-app (Bill):
One failure test on mako
http://ci.ubuntu.com/smokeng/trusty/touch/mako/55:20131209.1:20131203/5356/messaging-app-autopilot/558958/
-> You saw some discussion between Martin and Bill on this ML. Seems
there is an agreement for the workaround (as it's an intended design). A
version will land shortly (it's in the landing ask), so for soon ;)

* notes-app (Bill)
-> Seems fixed by the new release \o/

* webbrowser-app (Bill)
Replacing with
http://ci.ubuntu.com/smokeng/trusty/touch/mako/57:20131210.1:20131203/5375/webbrowser-app-autopilot/
(as previous link was in

Re: [Ubuntu-phone] ubuntu touch image 13.12.13

2013-12-13 Thread Didier Roche


Le 13/12/2013 18:26, Didier Roche a écrit :


Phew, end of this list! I'm still hoping that we can announce a good 
news like promoting image #65 (late), let's cross fingers.




And crossing fingers really worthed it!

Image #65 has a very good pass rate: ~98% for both mako and maguro! All 
the known failures are part of what was already reported previously.
So, we just promoted it so that you can enjoy for the week-end latest 
and greatest of Ubuntu Touch!


And I guess, time for holidays for me! I'll let the rest of the team 
piloting and reporting in the coming days. ;)

Have a good end of year period everyone!

Cheers,
Thanks
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 07.01.2014

2014-01-07 Thread Didier Roche


Happy new year everyone!

Now that we are rested from some holidays (and I hope everyone had a 
good christmas period), we are back on the going green campaign!
First, image 116, containing all changes that happens in the past 2 
weeks and half, is looking good! Knowing how many uploads have been made 
during the holiday period in the distro, that's quite an achievement. 
Well done everyone working tirelessly in that period!


So, image 116 is now the latest and greatest ubuntu touch image ever and 
is now promoted.


We are cleaning the build system (some components are failing to build, 
some other, due to transitions had direct uploads), and this will take 
some time on the landing slots. This work will probably continue 
tomorrow. Only small landings (and Mir) are looked at right now with our 
reduced manpower.


Having mako and maguro building and running the tests twice a day helped 
seeing that we still have (few) flaky tests, even on mako. The image was 
at 100% tests passing 2/3 of the time, but let's track down the latest 
niggles!


notes_app (Bill):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/112:20140105:20131223.2/5882/notes-app-autopilot/638428/
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/notes-app-autopilot/
-> just poked, being looked at

gallery_app (Bill):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/gallery-app-autopilot/
-> just poked, being looked at

weather-app:
http://ci.ubuntu.com/smokeng/trusty/touch/mako/109:20140103.1:20131223.2/5859/ubuntu-weather-app-autopilot/
-> just poked, being looked at

ubuntu-ui-toolkit (zoltan):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-ui-toolkit-autopilot/
-> was tried to be fixed, but seems it wasn't enough, reopened.

clock-app (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-clock-app-autopilot/
-> just poked, being looked at

calendar-app (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/calendar-app-autopilot/
-> just poked, being looked at

dialer_app crash (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/114:20140106:20131223.2/5903/dialer-app-autopilot/
-> just poked, being looked at

powerd issue:  (Kevin)
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1258655
Kevin told that he had a fix last night in powerd
https://code.launchpad.net/~kdub/powerd/fix-1258655/+merge/199582 

, but experts on the matter of powerd not convincedalso, its been 
raised this is potentially related 
https://bugs.launchpad.net/libhybris/+bug/1208433 (which leads to 
potential bug in bionic)

-> Kevin, any news on that one?

terminal app (Nicholas):
We had this regression last month, it's on the list as well for blocking 
new terminal app release (keyboard not working with it): 
https://bugs.launchpad.net/ubuntu-terminal-app/+bug/1257791

-> Nicholas is aware and working on it with upstream.

Let's continue in 2014 the quality ramp up!
Cheers,
Didier
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 08.01.14

2014-01-08 Thread Didier Roche


Hey everyone,

Images 117 and 118 have been built. However, due to a new version of 
base-passwd (thanks Sivaa for finding it after reverting one after 
another all new components in the image!) which showed a bad behavior 
from ofono-phonesim, we had a lot of tests failing on messaging-app and 
dialer-app.
Colin investigated and fixed the issue in ofono-phonesim. The version is 
building in the archive as we speak.


If someone is then still around, we'll have image 119 kicked with that 
fix (or it will be automatically built tomorrow morning with the cron job)


At the same time, we continued to get the whole system back in shape (as 
we had a lot of manual uploads to distro during holidays). This work 
will continue tomorrow.


We also had quite some releases that will be part of image 119:
* new Mir stack (with the traditional mir, unity-system-compositor, 
platform-api and unity-mir). This version contains the last month of 
work with a lot of bug fixes, integration tests enhancement to help 
bring ups of touch on community devices, and good improvement on the 
flakyness of some tests. Awesome work!

* powerd fix that we waiting on (see below!)
* some theming changes for cordova
* some test framework updates.
* 2 ubuntu-system-settings releases to test different case for the new 
CI train delivery system. This has been done hand in hand as a prototype 
with Sébastien and it worked quite well. Some refinement is going to be 
done, but good perspective on that project. :)


Ok, now, let's look again at the list of pending issues to be fully green:

notes_app (Bill):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/112:20140105:20131223.2/5882/notes-app-autopilot/638428/
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/notes-app-autopilot/
-> being looked at

gallery_app (Bill):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/gallery-app-autopilot/
-> a fix have been proposed to be released, scheduled now for next batch

weather-app (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/109:20140103.1:20131223.2/5859/ubuntu-weather-app-autopilot/
-> being looked at

ubuntu-ui-toolkit (zoltan):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-ui-toolkit-autopilot/
-> was tried to be fixed, but seems it wasn't enough, reopened.

clock-app (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-clock-app-autopilot/
-> being looked at

calendar-app (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/calendar-app-autopilot/
-> being looked at

dialer_app crash (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/114:20140106:20131223.2/5903/dialer-app-autopilot/
-> being looked at

powerd issue:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1258655
-> should be fixed in next image.

terminal app (Nicholas):
We had this regression last month, it's on the list as well for blocking 
new terminal app release (keyboard not working with it): 
https://bugs.launchpad.net/ubuntu-terminal-app/+bug/1257791

-> Nicholas is aware and working on it with upstream.

And that's it for today, see you tomorrow!
Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] ANN: Changes to our Upstream Landing and Merge Review Practices in January

2014-01-08 Thread Didier Roche


Le 08/01/2014 20:38, Robert Park a écrit :

On Wed, Jan 8, 2014 at 11:28 AM, Barry Warsaw  wrote:

 "Note that some people are merging the packaging branch into the upstream
 trunk. Both have pros and cons. I'm not attached to any particular form as
 debian/changelog is already the history of a package. But before merging,
 you should revert all generated files (modified or new)."

Will the new process require stronger language here?


Uh, yes, there are two possible ways of doing the merge, but there is
no ambiguity about the fact that debian/ directory must live within
trunk.



The idea is really about consistency and ease of use.

Historically, we had different approach in our internal development and 
everyone had its own set. This created some issues like, if you jump for 
a small patch in another project, questions like "where is trunk", 
"where is the packaging, I need to make a change here", "oh, this 
packaging is totally different from what I know" have happened.


So, the idea that we enforced from this process are quite simple:
- source package name == project name. So, if you have "foo" source 
package in Ubuntu where we are upstream for, you know that you can 
confidently bzr branch lp:foo and that's what is in the latest 
development version of ubuntu.
(I wish we can enforce maintenance branch around 
lp:foo/, but I guess I'll save the debate for later ;))
- inline packaging: You know and are sure that the packaging is . We 
also sanitize and try to standardize the packaging to have the effect of 
no surprise. You know the package is going to use dh9, debian/rules will 
be structured that way, we are use --fail-missing to avoid new files not 
being shipped without noticing…


This really helped upstream in multiple ways: consistency is key. For 
people not being really in packaging, they have been able to make the 
general changes themselves. Finally, the packaging changes are synced 
with the code change (/me remembers old days with "oh, you need to push 
now the packaging change to the packaging branch as I'm going to merge 
that branch which renames some files…" which was a nightmare).


Does this make sense on the general goal? You can keep one word to sum 
that up: consistency (to avoid surprises and so moving faster without 
hunting) ;)

Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] ANN: Changes to our Upstream Landing and Merge Review Practices in January

2014-01-09 Thread Didier Roche


Le 09/01/2014 15:04, Ted Gould a écrit :

On Thu, 2014-01-09 at 08:34 +0100, Didier Roche wrote:

(I wish we can enforce maintenance branch around
lp:foo/, but I guess I'll save the debate for later ;))


For those who are interested I attached my script that we use to do 
this.  It makes it easy and makes Didier smile, best script in the world!



:)


$ lp-project-new-series indicator-location 14.10 14.04




Waow 14.10! You're on edge Ted! ;)

Didier
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 09.11.14

2014-01-09 Thread Didier Roche


Hey everyone!

First, good news: image 119 is promoted. We are back with a new Mir, 
powerd fix and other changes like haptic feedback! Enjoy ;)


Image test results shows that the flaky failing in maguro can happen 
some times on mako.


The system is now fully back in shape (apart from bamf, which is getting 
resolved) and latest issues with our autopilot machine fix confirmed.


Another image 120 has just been kicked, containing some AP fix (see below).

On going green btw, I would appreciate feedback and updates where we 
stand at on the following (let's really get the list down):

notes_app (Bill):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/112:20140105:20131223.2/5882/notes-app-autopilot/638428/ 

http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/notes-app-autopilot/ 


-> No news since yesterday

gallery_app (Bill):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/gallery-app-autopilot/ 


-> Fix will be part of image 120.

weather-app (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/109:20140103.1:20131223.2/5859/ubuntu-weather-app-autopilot/ 


-> No news since yesterday

ubuntu-ui-toolkit (zoltan):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-ui-toolkit-autopilot/ 

-> was tried to be fixed, but seems it wasn't enough, reopened. No news 
since yesterday


clock-app (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-clock-app-autopilot/ 


-> No news since yesterday

calendar-app (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/calendar-app-autopilot/ 


-> No news since yesterday

dialer_app crash (Bill):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/114:20140106:20131223.2/5903/dialer-app-autopilot/ 


-> No news since yesterday

powerd issue:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1258655
-> should be fixed in next image.
-> it's indeed fixed! we can remove it from the list :)

terminal app (Nicholas):
We had this regression last month, it's on the list as well for blocking 
new terminal app release (keyboard not working with it): 
https://bugs.launchpad.net/ubuntu-terminal-app/+bug/1257791
-> Nicholas is aware and working on it with upstream. No news since 
yesterday.


Thanks everyone!
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 10.11.14

2014-01-10 Thread Didier Roche


Hello everyone

The unstable Ubuntu Touch image is now at its latest and finest with 
image 121 which has just been promoted!


It contains:
* some new system-settings updates (as part of the continuing citrain 
new CI developer experience)

* session migration user data support
* some theme changes.
* gallery-app AP tests fix (and for now, in image 120 and 121, we didn't 
see the issue again \o/)


Note that 121 has some tests failing on maguro, which are still part of 
the list below, so let's continue working on those. There are as well 
some crashers, listed under it. The Unity 8 crash with the smashed 
stacktrace are investigated (see the other thread).


The CI machinery has now merged all uploads that happened during 
holidays and is fully functional. The whole team is at full steam now 
enabling new projects that will be ship in the incoming images 
(properties-cpp, mediascanner v2...)


So, let's continue on the going green side, we have a lot of information 
in different threads, so I tried to sum them up here:


notes_app (Bill):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/112:20140105:20131223.2/5882/notes-app-autopilot/638428/ 

-> This one seems to need some more information to understand what 
happens (the toolbar is not closing). The CI team is asked if they can 
help providing some video for it.


http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/notes-app-autopilot/ 


-> Fix is submitted \o/. We are waiting for the green light for a release :)

weather-app (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/109:20140103.1:20131223.2/5859/ubuntu-weather-app-autopilot/ 


-> Networking failure. Seems it will need a mock to not rely on network.

ubuntu-ui-toolkit (zoltan):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-ui-toolkit-autopilot/ 

-> The team has reproduced this and determined that the osk is not 
always being hidden when an app is quit or terminates unexpectedly.
-> https://bugs.launchpad.net/ubuntu/+source/unity-mir/+bug/1267550, 
should Kevin get the ownership on this then? Greyback is working on it.


clock-app (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-clock-app-autopilot/ 

-> From Nicholas: "Still looking to reproduce -- the emulator won't run 
clock atm, investigating. Xnox, I see you seem to have results 
(passing), but I've only gotten crashes."


calendar-app (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/calendar-app-autopilot/ 


-> Reproduced in the emulator and fix is in the work!

dialer_app crash (Bill):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/114:20140106:20131223.2/5903/dialer-app-autopilot/ 


-> The team is looking into it

terminal app (Nicholas):
We had this regression last month, it's on the list as well for blocking 
new terminal app release (keyboard not working with it): 
https://bugs.launchpad.net/ubuntu-terminal-app/+bug/1257791
-> The issue was investigated and found that konsole qml plugin is what 
needs work. The plugin author is having a look would be useful to fixing 
this, so waiting for his response before continuing.


Thanks everyone and enjoy your week-end!
Didier

-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] ANN: Changes to our Upstream Landing and Merge Review Practices in January

2014-01-13 Thread Didier Roche


Le 10/01/2014 22:18, Barry Warsaw a écrit :

On Jan 09, 2014, at 08:34 AM, Didier Roche wrote:


So, the idea that we enforced from this process are quite simple:
source package name == project name. So, if you have "foo" source package in
Ubuntu where we are upstream for, you know that you can confidently bzr
branch lp:foo and that's what is in the latest development version of ubuntu.
inline packaging: You know and are sure that the packaging is . We also
sanitize and try to standardize the packaging to have the effect of no
surprise. You know the package is going to use dh9, debian/rules will be
structured that way, we are use --fail-missing to avoid new files not being
shipped without noticing…

I think this is fine policy, as long as it's documented and easily
discoverable.  But also note that this won't eliminate *some* confusion about
branch locations because you're also going to have the imported source
branches too, e.g. ubuntu:foo (a.k.a. lp:ubuntu/trusty/foo).

Modulo importer delays and failures, lp:foo and ubuntu:foo *should* be
identical content-wise, even though they won't have a common ancestor and
won't support merges between them.


Agreed, not sure about what we can do about that one though (apart from 
--overwrite in those branches everytime on ubuntu:foo).


Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 13.01.14

2014-01-13 Thread Didier Roche

Hey everyone.

We started this new week analyzing what happened since Friday evening.
We noticed a regression in the Unity 8 tests which happened on the 4
images produced. This was due to python-gi. Martin found the guilty
commit and reverted it. We are just reckiking an image and hope for
better test results. Another proof that it's getting easier to track
regressions as we can produce multiple images a day.

Due to that, we didn't promote an image yet.

On what entered into the image:
* notes app AP test fixes. We still need the click side to be promoted
though (should be soon)

* new usensord daemon to give access to application the device sensors
* a first go version of phablet-flash (I'll let Sergio make an official
announce on it I guess ;))

* new qtlocation and qtsensors
* you will notice that autopilot python 3 support was seeded in the
image by default.

We hope that next image test results will be better, meanwhile, let's
look at the progress on the going green:

Note that despite Alexander's announce on maguro, I'll keep listing the
maguro issues until we have the emulator wired up on the system. This
enables us to look on a "slower device", the test results

notes_app (Bill):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/112:20140105:20131223.2/5882/notes-app-autopilot/638428/

-> This one seems to need some more information to understand what
happens (the toolbar is not closing). The CI team is asked if they can
help providing some video for it.

http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/notes-app-autopilot/

-> Click packages should be available in next images

weather-app (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/109:20140103.1:20131223.2/5859/ubuntu-weather-app-autopilot/

-> Networking failure. Seems it will need a mock to not rely on network.

ubuntu-ui-toolkit (zoltan):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-ui-toolkit-autopilot/

-> The team has reproduced this and determined that the osk is not
always being hidden when an app is quit or terminates unexpectedly.
-> https://bugs.launchpad.net/ubuntu/+source/unity-mir/+bug/1267550,
should Kevin get the ownership on this then? Greyback is working on it.

clock-app (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-clock-app-autopilot/

-> From Nicholas: "Still looking to reproduce -- the emulator won't run
clock atm, investigating. Xnox, I see you seem to have results
(passing), but I've only gotten crashes."

calendar-app (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/calendar-app-autopilot/

-> Reproduced in the emulator and fix is in the work!

dialer_app crash (Bill):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/114:20140106:20131223.2/5903/dialer-app-autopilot/

-> The team is looking into it (doesn't seem to happen on the emulator
though)

terminal app (Nicholas):
We had this regression last month, it's on the list as well for blocking
new terminal app release (keyboard not working with it):
https://bugs.launchpad.net/ubuntu-terminal-app/+bug/1257791
-> The issue was investigated and found that konsole qml plugin is what
needs work. The plugin author is having a look would be useful to fixing
this, so waiting for his response before continuing.

[Ubuntu-phone] Landing team 14.01.14

2014-01-14 Thread Didier Roche

Hey!

Another landing day in the ubuntu phone world. We had images 126 and 127
produced. Those contains:

- the latest HUD unblocked from -proposed
- the fix from Martin in python-gobject getting the unity8 AP tests back
on shape \o/

- no more crash in qmlscene and some other apps
- the notes-app AP test fix (which is working for now \o/)
- latest qtlocation, columbus et voice services

The only known crasher is the dialer app (see below).

However, due to rssreader failing reliably since image 122 (
http://ci.ubuntu.com/smokeng/trusty/touch/mako/127:20140114:20140107.1/6052/ubuntu-rssreader-app-autopilot/),
we are not in a position to promote this image. I know Nicholas is
working tirelessly to understand what regressed it (taking the diff of
the image and going one by one).

Image 128 is going to be kicked in an hour (but won't be promoted
because of rssreader) with the changes from the day. Those are safe
changes to ensure we don't regress our pass rate:
- seeding usensord and the account evernote support plugin (so that the
click apps can be release)

- initial work on being able to purchase applications from the click store
- dimension support changes for sidestage in tablet mode

On going green, updating on the current progress and reports from Nicholas):

notes_app (Bill):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/112:20140105:20131223.2/5882/notes-app-autopilot/638428/

-> This one seems to need some more information to understand what
happens (the toolbar is not closing). The CI team is asked if they can
help providing some video for it.

http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/notes-app-autopilot/

-> Fixed, removing from the list

weather-app (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/109:20140103.1:20131223.2/5859/ubuntu-weather-app-autopilot/

-> Networking failure. This is changing to TWC api, and yes, there will
need to be some mocking. This is WIP by development team. A big rollover
to the new API will be landing soon.

ubuntu-ui-toolkit (zoltan):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-ui-toolkit-autopilot/

clock-app (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-clock-app-autopilot/

-> From Nicholas: "No luck in reproducing yet. -- the emulator won't run
clock atm, investigating. Xnox, I see you seem to have results
(passing), but I've only gotten crashes."

calendar-app (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/calendar-app-autopilot/

-> Merge is stalemated because of inconclusive results from folks with
maguro devices (possible MIR issue?). Going to try and land this and be
ready to revert.

dialer_app crash (Bill):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/114:20140106:20131223.2/5903/dialer-app-autopilot/

-> The team is looking into it (doesn't seem to happen on the emulator
though)

terminal app (Nicholas):
We had this regression last month, it's on the list as well for blocking
new terminal app release (keyboard not working with it):
https://bugs.launchpad.net/ubuntu-terminal-app/+bug/1257791
-> The issue was investigated and found that konsole qml plugin is what
needs work. Plugin author isn't able to look at the issue until next
week, so we're on hold until then.

Didier
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Stopping the line to get back to a promotable state, help needed!

2014-01-15 Thread Didier Roche


Hey guys,

As you can see on the landing team emails, we are getting a though time this 
week to be able to promote an image. We have been struck by a few independent 
regressions that plague us for a days already with new regressions coming in 
while we investigate them. The remaining ones that we are seeing are reliable 
regressions on messaging-app (from image 126 on maguro) and rssreader (from 
image 122 on all devices).
Remember that last promoted image is 121.

However, none of those components had a new release, so it means something else 
regressed them. We are working hard bi-secting changes etc. to get those 
identified and fixed ASAP. This work is even more difficult considering the 
number of recent direct uploads we are going through in the archive.

Based on those facts:
* since yesterday mid-day, we stopped doing any new release for requests in the 
landing spreadsheet
* it will be really helpful to keep the amount of direct uploads to a minimum 
on components that are on the touch image.

This will help getting the noise down and will enable us to promote a new image 
sooner.

Any other help in term of debugging will be really appreciated so that we can 
unblock the situation (please ping us on :#ubuntu-ci-eng on freenode)

Thanks for your understanding and cooperation,
Didier

-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] Stopping the line to get back to a promotable state, help needed!

2014-01-15 Thread Didier Roche


Le 15/01/2014 11:12, Didier Roche a écrit :

Hey guys,

As you can see on the landing team emails, we are getting a though time this 
week to be able to promote an image. We have been struck by a few independent 
regressions that plague us for a days already with new regressions coming in 
while we investigate them. The remaining ones that we are seeing are reliable 
regressions on messaging-app (from image 126 on maguro) and rssreader (from 
image 122 on all devices).
Remember that last promoted image is 121.

However, none of those components had a new release, so it means something else 
regressed them. We are working hard bi-secting changes etc. to get those 
identified and fixed ASAP. This work is even more difficult considering the 
number of recent direct uploads we are going through in the archive.

Based on those facts:
* since yesterday mid-day, we stopped doing any new release for requests in the 
landing spreadsheet
* it will be really helpful to keep the amount of direct uploads to a minimum 
on components that are on the touch image.

This will help getting the noise down and will enable us to promote a new image 
sooner.

Any other help in term of debugging will be really appreciated so that we can 
unblock the situation (please ping us on :#ubuntu-ci-eng on freenode)

Thanks for your understanding and cooperation,
Didier



Some updates:

Siva found that the messaging-app issue disappear if we revert the 
latest HUD release. There are some investigation why this happens (HUD 
is now stricter in some env variable check and some can be missing). 
Meanwhile, we reverted it by a direct upload so that there is less 
pressure for upstream to reproduce/figure out what's wrong (as the HUD 
isn't used in this test, it seems a weird side-effect).


Nice catch Siva ;)

Still the rssreader one to go!
Cheers,
Didier
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] Stopping the line to get back to a promotable state, help needed!

2014-01-15 Thread Didier Roche


Some more updates.

The rss reader issue was found (a change in a public rss feed used in 
the tests).
Nicholas' fix is under review to use a mock rss feed in the test so that 
we are not impacted by those anymore.


We will be back in a normal situation soon, let's hope!

Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 15.01.14

2014-01-15 Thread Didier Roche

Hi,

Changes from yesterday and direct uploads to distro were released today
in images 128 and 129. Unfortunately, we only have full results on image
129.

Image 128 contains:
- seeding usensord and the account evernote support plugin (so that the
click apps can be release)

- initial work on being able to purchase applications from the click store
- dimension support changes for sidestage in tablet mode

Image 129 contains some hybris (and soon some android to come) changes
for grouper support.

However, as you could have seen on the "stopping the line" email, we had
to do it for being able to repromote an image due to various recent
regressions. I want first to thank everyone for playing the game and
raging on getting the issues fixed and refraining from uploading... The
last blocking issue (rssreader) is now understood and Nicholas fix is
under polish/review. Once the click package will be published, we will
rekick an image, and check the tests result to ensure that the image is
promotable (probably the tests will finish quite late).

On going green, I'm mostly pasting what was from yesterday, note the
latest bug addition, which is not a regression from latest promoted
image (121), but still something to track.

*notes_app* (Bill):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/112:20140105:20131223.2/5882/notes-app-autopilot/638428/

-> This one seems to need some more information to understand what
happens (the toolbar is not closing). The CI team is asked if they can
help providing some video for it.

*weather-app* (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/109:20140103.1:20131223.2/5859/ubuntu-weather-app-autopilot/

-> Networking failure. This is changing to TWC api, and yes, there will
need to be some mocking. This is WIP by development team. A big rollover
to the new API will be landing soon.

*unity-mir* (Kevin):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-ui-toolkit-autopilot/

*clock-app *(Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-clock-app-autopilot/

-> From Nicholas: "No luck in reproducing yet. -- the emulator won't run
clock atm, investigating. Xnox, I see you seem to have results
(passing), but I've only gotten crashes."

*calendar-app* (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/calendar-app-autopilot/

-> A fix is ready for the flaky. Pending though on the next promoted image.

*dialer_app* crash (Bill):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/114:20140106:20131223.2/5903/dialer-app-autopilot/

-> The team is looking into it (doesn't seem to happen on the emulator
though)

*terminal app* (Nicholas):
We had this regression last month, it's on the list as well for blocking
new terminal app release (keyboard not working with it):
https://bugs.launchpad.net/ubuntu-terminal-app/+bug/1257791
-> The issue was investigated and found that konsole qml plugin is what
needs work. Plugin author isn't able to look at the issue until next
week, so we're on hold until then.

And the new one:
Possible *Mir* bug on maguro making some apps fail starting (Kevin)
https://bugs.launchpad.net/unity8/+bug/1268693
-> a lot of people are looking into it, assign Kevin as tracking that
one as it seems to be related to latest Mir.

Re: [Ubuntu-phone] Stopping the line to get back to a promotable state, help needed!

2014-01-16 Thread Didier Roche


Le 15/01/2014 17:42, Didier Roche a écrit :

Some more updates.

The rss reader issue was found (a change in a public rss feed used in 
the tests).
Nicholas' fix is under review to use a mock rss feed in the test so 
that we are not impacted by those anymore.


We will be back in a normal situation soon, let's hope!



We didn't cross fingers enough apparently. Another regression was spot 
just in time by Alan (https://bugs.launchpad.net/music-app/+bug/1269744) 
while doing dogfooding.
For now, we only know it was working on image #121 and the bug is in 
latest image (#131). We 3 furiously bisecting image by image before 
finding the guilty component, helping for a quick resolution.


Please continue following the same rules that was asked to ensure that 
image #132 can be safely promoted. We still hold the landing asks at the 
same time.

Thanks everyone for your cooperation.

Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] Stopping the line to get back to a promotable state, help needed!

2014-01-16 Thread Didier Roche


Le 16/01/2014 11:14, Didier Roche a écrit :
We didn't cross fingers enough apparently. Another regression was spot 
just in time by Alan 
(https://bugs.launchpad.net/music-app/+bug/1269744) while doing 
dogfooding.
For now, we only know it was working on image #121 and the bug is in 
latest image (#131). We 3 furiously bisecting image by image before 
finding the guilty component, helping for a quick resolution.


Please continue following the same rules that was asked to ensure that 
image #132 can be safely promoted. We still hold the landing asks at 
the same time.

Thanks everyone for your cooperation.


So, we spot that the issue was in the image #128 and found that the 
unity-mir change is responsible for that bug. Reverting it makes the bug 
disappear
We are now evaluating, as the change is part of a set of 3 components 
change (unity-mir, platform-api and qtubuntu) and can regress the tablet 
experience compared to latest promoted image if half-reverted.


We are trying to catch up upstream (which is in meetings), if we can't 
find any solution quickly, we'll go with a global revert.


Will continue giving you informations.
Cheers,

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 16.01.14

2014-01-16 Thread Didier Roche


Hey,

short message today.

As you can see on the other thread "stop the line", we had to continue 
stopping the line due to another bug that was detected. The unity-mir 
fix is in thanks to the excellent work from Ricardo. The image is 
building now and we wait for the test results to unblock the line (so 
probably tomorrow morning with the dogfooding on both maguro and mako).


I guess a test for that use case would be a nice one now that the issue 
was dealt with.


unity-mir has been run locally with all AP tests and everything passed. 
Let's cross fingers we are getting the same results on the official 
infrastructure.


We have hope in image 132!
Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] Stopping the line to get back to a promotable state, help needed!

2014-01-16 Thread Didier Roche


Le 16/01/2014 11:58, Didier Roche a écrit :


Will continue giving you informations.
Cheers,



Similar information than the one giving on the ubuntu-phone mailing list 
under the title "Landing team 16.01.14".
Ricardo fixed the issue promptly, we reran all AP tests manually to 
certify that this fix doesn't introduce more regressions. Now that the 
package is in archive, the next image is building.


We are waiting on AP tests results in the infrastructure (so, another 
5-6 hours) and we need to dogfood the image on both maguro and mako. 
We'll probably be able to promote an image only tomorrow morning 
european time surely.


Thanks everyone for your patience,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Back on shape, touch image 132 will be promoted

2014-01-16 Thread Didier Roche


Le 16/01/2014 17:53, Didier Roche a écrit :


We are waiting on AP tests results in the infrastructure (so, another 
5-6 hours) and we need to dogfood the image on both maguro and mako. 
We'll probably be able to promote an image only tomorrow morning 
european time surely.




Image test results and dogfooding both +1 on the image promotion for 
image #132.


The trace related to tests failures on maguro are due to the random 
lockup since the new Mir 
(https://bugs.launchpad.net/unity8/+bug/1268693). The Unity8 crashers 
are as well the known one on startup and screen locked. Manual AP tests 
run confirms those.


So, we are going to promote that image (surely in ~3h as I don't have 
access right to that). Meanwhile, we are resuming the publishing of 
prepared release landing. Developers holding off their upload can now 
safely go back to a normal Friday release day ;)


Thanks again everyone,

Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Introducing the new upstream release process: CI Train

2014-01-17 Thread Didier Roche

Hey everyone.

As most of you may know from the announce and slides that Alexander
posted on the ubuntu phone mailing list[1] last week, we are changing
the release process for our upstream landing. This is a step towards the
CI Airline vision which was discussed at vUDS.

We called it "CI Train" because it's going to bring us some advantages
of the final vision (self-service checkin, semi-isolated environments,
availability for upstreams to do their landing themselves), but it won't
fully fly yet. ;) This new program still ensure that the ubuntu
distribution rules are respected and while the system gives more
autonomy in their landing, there is still the same checks and security
than with daily release, meaning that this doesn't give indirect upload
rights if you don't have them. However, we'll have some gains like Core
Developers will be able to do the publication to ubuntu themselves now.

Since beginning of this year we worked tirelessly to get the code and
infra in shape and did a successful pre-pilot of the process and "raw"
tools with Sébastien last week. With his feedback we have been able to
eliminate initial rough edges and improve the tooling to be even more
convenient. With that, we feel comfortable to go ahead and will start
rolling out the new landing process to all teams iteratively in waves -
with first wave starting as early as next week on Tuesday. We're happy
to collect any feedback on how to smoothen even more that process.

As per Alexander's proposal, dedicated landers in each team have been
identified and will be trained to use the new system so that they become
able to drive and do the landings of their components in a more
self-service manner. Some components, when across different landings,
will be co-shared of course. Those refinements and the list of people
being able to land will evolve as we go.

You can find the current timeline and waves with dates on when we plan
to move teams to the new process over in a spreadsheet [2]. Remember
that dates might change and your ramp up might get delayed as we find
issues as we go. However, once it is your teams turn we will go ahead and:

- disabling the upstream merger (as trunk means "shipped in distro")

- disabling daily release

Meaning: from then on, you will use the new landing process that folds
the landing into your MP process.

We're certain a lot of you are looking forward to move to this new
process, we're contacting directly with more instructions the landers as
we move forward this program. Feel free to ask if you have any question.

Let's give more control over our CI process in upstream's hand while
keeping the whole integration quality bar high!

Cheers,

Didier

[1] https://lists.launchpad.net/ubuntu-phone/msg05776.html

[2]
https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0Au6idq7TkpUUdC05a2ZQSmgwU2NFYnJQOE9qMDRYa3c#gid=0

*
--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 16.01.14

2014-01-17 Thread Didier Roche


Hey,

Nice way to end the week again, we promoted an image today. #132 is the 
latest and greatest since image #121 and now the current trusty Touch 
image. It contains the changes mostly summed up in the previous emails 
throughout the week and is normally regression-free.


The test results are equivalent (and were rerun locally), meaning some 
flaky tests on maguro and mako passing, but some known crashers: the 
unity8 crasher on stop due to greeter lockup and a keyboard (maliit 
crasher) with an incoming fix.


Meanwhile, we released noticeable changes  in the incoming image #134:
* nested Mir session mode
* fix for DTMF tones which were not correcly being sent (that was an 
issue with automatic phone answer recognizing number sounds)
* enhancements in messaging-app: when text messages are sent a spinner 
is shown while sending then a timestamp in the message after success

* mediaplayer-app gains some initial desktop mode support
* update to the latest mediascanner scope API
* new system-settings, using the new release process
* set target on indicator-messages
* a lot of build failure fixes since last trusty rebuild


*notes_app* (Bill):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/112:20140105:20131223.2/5882/notes-app-autopilot/638428/ 

-> This one seems to need some more information to understand what 
happens (the toolbar is not closing). The CI team is asked if they can 
help providing some video for it.


*weather-app* (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/109:20140103.1:20131223.2/5859/ubuntu-weather-app-autopilot/ 

-> Networking failure. This is changing to TWC api, and yes, there will 
need to be some mocking. This is WIP by development team. A big rollover 
to the new API will be landing soon.


*unity-keyboard/maliit crash* (Kevin/Bill):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-ui-toolkit-autopilot/ 

Refailed today. A fix is in ubuntu-keyboard but we were asked to hold on 
on the release for now. So we hold on our breath and will release as 
soon as possible.
We think that this crash on mako on image #133 of webbrowser-app is the 
same cause.


*clock-app *(Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-clock-app-autopilot/ 

-> From Nicholas: "No luck in reproducing yet. -- the emulator won't run 
clock atm, investigating. Xnox, I see you seem to have results 
(passing), but I've only gotten crashes."
-> this one refailed today on mako (on test_run_preset which is calling 
test_add_preset): 
http://ci.ubuntu.com/smokeng/trusty/touch/mako/133:20140117:20140115.1/6118/ubuntu-clock-app-autopilot/677464/


Nicholas told: (quoting)
Found several probable causes for these failures. Seems to be a 
combination of the bug below on MIR, and a potential UITK issue with tab 
switching.


Probable MIR bug:
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/130:20140115.1:20140115.1/6087/ubuntu-clock-app-autopilot/671736/
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/126:20140113.1:20140107.1/6050/ubuntu-clock-app-autopilot/664258/
Tab switching:
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-clock-app-autopilot/642628/
Today's run contains an actual test failure possibility, looking into
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/131:20140116:20140115.1/6095/ubuntu-clock-app-autopilot/673039/

*calendar-app* (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/calendar-app-autopilot/ 


-> Sergio is going to release a fix as we speak

*dialer_app* crash (Bill):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/114:20140106:20131223.2/5903/dialer-app-autopilot/ 

-> The team is looking into it (doesn't seem to happen on the emulator 
though)


*terminal app* (Nicholas):
We had this regression last month, it's on the list as well for blocking 
new terminal app release (keyboard not working with it): 
https://bugs.launchpad.net/ubuntu-terminal-app/+bug/1257791
-> The issue was investigated and found that konsole qml plugin is what 
needs work. Plugin author isn't able to look at the issue until next 
week, so we're on hold until then.


Possible *Mir* bug on maguro making some apps fail starting (Kevin)
https://bugs.launchpad.net/unity8/+bug/1268693
-> a lot of people are looking into it, assign Kevin as tracking that 
one as it seems to be related to latest Mir.
-> affect quite a lot maguro. Will worth seeing if people can reproduce 
on the emulator?



See you next week for new touch adventures!
Didier
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] Landing team 16.01.14

2014-01-20 Thread Didier Roche

Le 20/01/2014 09:09, Olivier Tilloy a écrit :

On Sat, Jan 18, 2014 at 12:42 PM, Oliver Grawert <mailto:o...@ubuntu.com>> wrote:

hi,
Am Samstag, den 18.01.2014, 11:57 +0100 schrieb Oliver Grawert:
> Am Freitag, den 17.01.2014, 18:34 +0100 schrieb Didier Roche:
>
> > Meanwhile, we released noticeable changes  in the incoming
image #134:
> > * nested Mir session mode
> > * fix for DTMF tones which were not correcly being sent (that
was an
> > issue with automatic phone answer recognizing number sounds)
> > * enhancements in messaging-app: when text messages are sent a
spinner
> > is shown while sending then a timestamp in the message after
success
> > * mediaplayer-app gains some initial desktop mode support
> > * update to the latest mediascanner scope API
> > * new system-settings, using the new release process
> > * set target on indicator-messages
> > * a lot of build failure fixes since last trusty rebuild
>
> there seems to also have been dbus and apparmor updates that
seemingly
> break the world wrt tests now ... all failed tests seem to have
a new
> logfile (upstart-dbus-system-bridge.log) with:
>
> "upstart-dbus-bridge: Unable to write pid file: No such file or
> directory"
>
> in them ...

additionally it seems that none of the webapps that use the
webbrowser-app call in their .desktop file can not start, i only get a
white screen (amazon, ebay, various apps from the store)

Ooops... webbrowser-app was split into two executables: one is the 
actual browser application, and the other one is the webapps container.
For backward compatibility, the browser application re-executes the 
webapp container in place if it detects an intent to launch a webapp. 
This works nicely if the webapp container is present, but it appears 
we forgot to add it to the seed. Installing webapp-container solves 
the problem.
I've filed bug #1270737 
<https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1270737> to 
track the issue.

Shouldn't rather the browser app recommending the container (and we can 
put an oxide | webapp-container) once the later is present ?

Didier
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] Landing team 16.01.14

2014-01-20 Thread Didier Roche


Le 20/01/2014 06:02, Steve Langasek a écrit :

This is the result of the split of the qtubuntu-android package into
qtubuntu-android and qtubuntu-desktop packages.  Apparently libqubuntu.so is
now only distributed in the latter.

If libqubuntu.so is still needed for SF, even on Mir-based devices, perhaps
qtubuntu-desktop should be added to the seed.  Or perhaps now's the right
moment to get rid of SF once and for all?

Simultaneously, a regression was introduced by a change to
/etc/profile.d/qpa_plugin.sh in ubuntu-touch-session 0.88.  The changed code
used the presence of a $MIR_SOCKET variable to determine which qpa plugin to
use, but nothing sets this variable in an adb session.

ubuntu-touch-session 0.89 reverts to the previous behavior, which should fix
things for adb on Mir-based systems (such as maguro).



Even with Steve's fix and another from Ogra (it seems there is a race to 
setup an environment variables and so some AP tests are failing as the 
components are crashing under the wrong environment), we had to revert 
ubuntu-touch-session for nested Mir. We noticed on latest images 
multiples issues:

- stacking issues:
* start on a vanilla configuration, try to setup a wiki -> the WPA 
dialog is never shown (probably displayed under the shell)
* no u1 account, click on "install" in the click scope, then, depending 
on config/boot:
- either Unity8 is toping at 80% CPU and no refresh/phone locked (had to 
reboot)
- either the u1 account dialog is showing up, but the keyboard is 
showing under the shell or under the app and the whole system is stuck
- the env variable isn't set properly reliably, as told previously, this 
occurs:
* (probably due to that): no way to install click apps if you already 
have an u1 account associated on your phone
* some random crashes happening in multiple pieces (Unity8, HUD, 
mediascanner, unity-system-compositor…)


We decided to revert the nested Mir mode for now. Investigation and a 
lot of manual testing in addition to the automatic one will be needed, 
as we are clearly lacking of safe bet here.


I *strongly* suggests that we use that opportunity to create at least 2 
AP tests for basic vanilla setup (and we accept the nested Mir only when 
at least those 2 are here):

* connect to a wifi network and type a WPA (or WEP) key
* try to install a click app with no u1 account associated, and then, 
associating one. Finally ensuring the selected click app is installed 
and launch it.


Can anyone step up and help creating those AP test cases? ^
Thanks,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 20.01.14

2014-01-20 Thread Didier Roche


Hey,

Multiples images were built over the week (from 134 to 137). However, we 
now have the confirmation it was good to hold on uploads last week to 
get back to a promotable images as in 2 uploads on Friday (uploads that 
we hold on on purpose), we didn't get 2 but 3 regressions! (Nice strike):


The content of those images were mostly the ones summed up on Friday image.

To sum up:
- #1: webapps container was separated in another package which was 
missing, so no webapps available
- #2: nested Mir mode which was enabled created some stacking issues, 
some positioning (0x0) was overlapping the shell as well and some race 
resulting in missing env variables was making a lot of service crashing.
- #3: Any webapp had a big grey empty title bar on top ( 
https://bugs.launchpad.net/webbrowser-app/+bug/1270848)


All were found (apart from the missing env variable) by manual testing 
as no AP tests are covering any of those.


We fixed #1 by seeding the missing package, and #2 by reverting the 
nested Mir mode in ubuntu-touch-session. We kicked image #138 which 
showed the 3rd regression (unable to see it first).


Olivier fixed #3 promptly and we are right now releasing the fix to the 
distribution, will kick a new image (#139). We hope that the test 
results will be comparable to the ones we got for #138, but that 
dogfooding (resetting the configuration) will show that there is any 
regression.


We are preparing more landing meanwhile, but don't publish them to not 
create any other issue.


As there is no improvement on "going green" since Friday, I'm skipping 
that part, let's get to a promotable image first.


Cheers,
Didier
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 20.01.14

2014-01-21 Thread Didier Roche


Hey,


We got an image promoted! Image #141 was the one.
We detected another regression on image #140 from this morning (a lot of 
qmlscene crashes like [1]). We found that the regression was laying down 
in at-spi2-core, reverted it, get clearance due to alpha2 freeze and 
then rekick an image. Test results just finishes and show the 
traditional flaky tests.


So, what was new due compared to latest promoted image (#132)? Mainly we 
got:

* fix for the flaky calendar-app AP test \o/
* new version of messaging app with status, retry and delivery 
confirmation of SMS messages
* separation of webbrowser-app webapps container in a separate 
components to be able to get Oxide support

* getting the input method (OSK) not being hidden if app killed
* pile of bug fixes to get click scope better tested and intial work to 
get click app purchases support
* initial work on the scope API to be able to properly starts and 
shutting down them.

* Some application start up time optimization


We are now releasing all the niceness that we prepared but not published 
until we got an image promoted. More news on that in my tomorrow's email :)


*notes_app* (Bill/Zoltan):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/112:20140105:20131223.2/5882/notes-app-autopilot/638428/ 

-> Olivier tried a little bit more on that one (we saw more of setUp() 
function randomly failing). It seems he need help, maybe the SDK team as 
it can toolbar related can help? A bug report to track that is filed as 
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1270737.


*weather-app* (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/109:20140103.1:20131223.2/5859/ubuntu-weather-app-autopilot/ 

-> Networking failure. This is changing to TWC api, and yes, there will 
need to be some mocking. This is WIP by development team. A big rollover 
to the new API will be landing soon.


*ubuntu-keyboard/maliit crash* (Kevin/Bill):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-ui-toolkit-autopilot/ 


An incoming ubuntu-keyboard fix is in the releasing pipe :)

*clock-app *(Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-clock-app-autopilot/ 

-> From Nicholas: "No luck in reproducing yet. -- the emulator won't run 
clock atm, investigating. Xnox, I see you seem to have results 
(passing), but I've only gotten crashes."
-> this one refailed today on mako (on test_run_preset which is calling 
test_add_preset): 
http://ci.ubuntu.com/smokeng/trusty/touch/mako/133:20140117:20140115.1/6118/ubuntu-clock-app-autopilot/677464/


Nicholas told: (quoting)
Found several probable causes for these failures. Seems to be a 
combination of the bug below on MIR, and a potential UITK issue with tab 
switching.


Probable MIR bug:
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/130:20140115.1:20140115.1/6087/ubuntu-clock-app-autopilot/671736/
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/126:20140113.1:20140107.1/6050/ubuntu-clock-app-autopilot/664258/
Tab switching:
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-clock-app-autopilot/642628/
Today's run contains an actual test failure possibility, looking into
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/131:20140116:20140115.1/6095/ubuntu-clock-app-autopilot/673039/

*calendar-app* (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/calendar-app-autopilot/ 

-> This is now released. However, even with the fix, there is still some 
flaky tests (running them doesn't seem to be reproducible): 
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/141:20140121.1:20140115.1/6204/calendar-app-autopilot/


*dialer_app* crash (Bill):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/114:20140106:20131223.2/5903/dialer-app-autopilot/ 

-> The team is looking into it (doesn't seem to happen on the emulator 
though)


*terminal app* (Nicholas):
We had this regression last month, it's on the list as well for blocking 
new terminal app release (keyboard not working with it): 
https://bugs.launchpad.net/ubuntu-terminal-app/+bug/1257791
-> The issue was investigated and found that konsole qml plugin is what 
needs work. Plugin author isn't able to look at the issue until next 
week, so we're on hold until then.


A new one to add to the "high list" (targeted to dialer-app, but can be 
unity-mir as well), but this one was already in latest promoted image:

*dialer* in call is blanked by lock screen (bfiller)
https://bugs.launchpad.net/dialer-app/+bug/1271210

Cheers,
Didier

[1] 
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1271154 

-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 22.01.14

2014-01-22 Thread Didier Roche

Fresh news of the day!

Unfortunately, we can't promote an image today. More investigation on
the go.

We built images #142 and #143.

142 contains:
* latest enhancement on scopes backend API

143 contains:
* latest keyboard enhancement with spell checking in multiple languages
(if enabled, still disabled by default). This keyboard should fix a
maliit crasher on flacky tests
* libusermetric fix for shipping the latest HUD version (HUD blocked by
alpha2 freeze for now in proposed)

Olivier found a fix for Oliver (please follow ;)) on the webapp
container not having a back
button(https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1271436).
The fix is in the proposed pocket for now (blocked by alpha2 freeze)

We also had some issues in the self-service citrain system due to
canonistack shutdown on lcy02. We moved to lcy01 and it was a good
exercise to see how we can setup a new version. However, the latest part
rsync is still not functional.

So, why no image promotion? Tests result on image 142 are mostly looking
good. However, we do have some maliit crashers which are almost looking
like the ones that were mentioned previously on this ML. The keyboard
change in image 143 is supposed to fix it, so we didn't want to take any
risk to promote a new crasher.

Image 143 has however the OSK totally broken (which wasn't the case in
individual tests it seems), and so, we can expect a lot of test
failures. The keyboard is crashing and non functional. We give 1h30 from
now to upstream to investigate, if nothing, we'll revert the
ubuntu-keyboard + ubuntu-touch-meta changes so that the image spinned up
during the night should give us a promotable image again.

I update the going green section with the discussions that happened
meanwhile on the ML:

*notes_app* (Bill/Zoltan):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/112:20140105:20131223.2/5882/notes-app-autopilot/638428/

-> Olivier tried a little bit more on that one (we saw more of setUp()
function randomly failing). It seems he need help, maybe the SDK team as
it can toolbar related can help? A bug report to track that is filed as
https://bugs.launchpad.net/notes-app/+bug/1271054.

*weather-app* (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/109:20140103.1:20131223.2/5859/ubuntu-weather-app-autopilot/

-> Networking failure. This is changing to TWC api, and yes, there will
need to be some mocking. This is WIP by development team. A big rollover
to the new API will be landing soon.

*ubuntu-keyboard/maliit crash* (Kevin/Bill):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-ui-toolkit-autopilot/

ubuntu-keyboard supposed to fix that landed... but as you saw, we need
to have the keyboard working first ;)

*clock-app *(Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-clock-app-autopilot/

-> From Nicholas: "No luck in reproducing yet. -- the emulator won't run
clock atm, investigating. Xnox, I see you seem to have results
(passing), but I've only gotten crashes."
-> this one refailed today on mako (on test_run_preset which is calling
test_add_preset):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/133:20140117:20140115.1/6118/ubuntu-clock-app-autopilot/677464/

Nicholas told: (quoting)
Found several probable causes for these failures. Seems to be a
combination of the bug below on MIR, and a potential UITK issue with tab
switching.

Probable MIR bug:
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/130:20140115.1:20140115.1/6087/ubuntu-clock-app-autopilot/671736/
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/126:20140113.1:20140107.1/6050/ubuntu-clock-app-autopilot/664258/
Tab switching:
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-clock-app-autopilot/642628/
Today's run contains an actual test failure possibility, looking into
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/131:20140116:20140115.1/6095/ubuntu-clock-app-autopilot/673039/

Sergio is working to land a fix for this -- Chris Gagnon confirmed the
changes allowed the tests to pass properly on maguro, so fingers crossed
:-) (thanks Chris!)

*calendar-app* (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/141:20140121.1:20140115.1/6204/calendar-app-autopilot/
Nicholas is working on it, the CI team and others will help him to get
access to maguro devices.

*dialer_app* crash (Bill):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/114:20140106:20131223.2/5903/dialer-app-autopilot/

-> The team is looking into it (doesn't seem to happen on the emulator
though)

Re: [Ubuntu-phone] Landing team 22.01.14

2014-01-22 Thread Didier Roche


Le 22/01/2014 20:04, Marco F a écrit :




*terminal app* (Nicholas):
We had this regression last month, it's on the list as well for
blocking new terminal app release (keyboard not working with it):
https://bugs.launchpad.net/ubuntu-terminal-app/+bug/1257791
-> The issue was investigated and found that konsole qml plugin is
what needs work. Plugin author isn't able to look at the issue
until next week, so we're on hold until then.


Already last week it said 'next week'. :(


I guess that the plugin author will really welcome any help to get that 
fixed then! :)


Cheers,
Didier
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 23.01.14

2014-01-23 Thread Didier Roche

Hey!

Good news today, we promoted image #144. This one has a very good pass
rate, good dogfooding results and the keyboard issue discovered
yesterday was fixed!
Also, there is the fix for the webapps getting back the "back" button
now. The clock has also been updated to its latest to fix AP tests and
add some more for the stopwatch.

Let's keep the ball rolling, we are kicking a new image now to get
latest libhybris and android config changes to support android 4.4.
We had some network-related issues on the daily release system. Those
are now fixed and the landing are starting back.

We are continuing working on the CI Train program with the upstreams
(autopilot and system-settings + some desktop components in particular)
to speed them up to this process.

Some nice improvements on the going green:
*notes_app* (Bill/Zoltan):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/112:20140105:20131223.2/5882/notes-app-autopilot/638428/

*weather-app* (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/109:20140103.1:20131223.2/5859/ubuntu-weather-app-autopilot/

-> Networking failure. This is changing to TWC api, and yes, there will
need to be some mocking. This is WIP by development team. A big rollover
to the new API will be landing soon.

*ubuntu-keyboard/maliit crash* (Bill):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-ui-toolkit-autopilot/

-> no maliit crash on latest run for now with the latest keyboard, let's
keep fingers crossed

*clock-app *(Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/114:20140106:20131223.2/5905/ubuntu-clock-app-autopilot/

-> no failures for now with clock app, let's keep as well fingers crossed :)

*dialer_app* crash (Bill):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/114:20140106:20131223.2/5903/dialer-app-autopilot/

-> The team is looking into it (doesn't seem to happen on the emulator
though)

So, 2 less on the list, let's hope that the incoming image will confirm
those being out!

[Ubuntu-phone] Landing team 24.01.14

2014-01-24 Thread Didier Roche

Hi,

We built images #145 and #146. Those contains:
* some android 4.4.2 bug fixes support which will enable us to bring the
new devices

* lxc-android-config change to initiate support for the N7 2013
* new usensord to fix the concurrence between the manually set
brightness which was overriden by the automatic brightness environment
detection
* the new click version with framework supports discussed in another
thread on this mailing list

* some media fixes for the N10

However, it seems that a known random qmlscene crash on maguro discussed
in the past days became systematic with those images. We tried to revert
one by one all components without finding the guilty one. Even if the
dogfooding was positive, we prefer to not risk into a promotion and get
the crasher fixed first.

This is under investigation by ricmm to fix this qtubuntu crash:
* https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1271879

The next autopilot version is ready to be released. However, we hold it
on to get final confirmation to get it released on Monday (and promote
the next image). We are not releasing anything for now (we still have a
lot of changes in the queue due to alpha2 unfreeze) and will fetch the
crash fix and rekick an image ASAP.

On going green:
*notes_app* (Bill/Zoltan):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/112:20140105:20131223.2/5882/notes-app-autopilot/638428/

*weather-app* (Nicholas):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/109:20140103.1:20131223.2/5859/ubuntu-weather-app-autopilot/

-> Networking failure. This is changing to TWC api, and yes, there will
need to be some mocking. This is WIP by development team. A big rollover
to the new API will be landing soon.

*dialer_app* crash (Bill):
http://ci.ubuntu.com/smokeng/trusty/touch/mako/114:20140106:20131223.2/5903/dialer-app-autopilot/

-> The team is looking into it (doesn't seem to happen on the emulator
though)

Let's hope that we get the qtubuntu issue fixed soon to be able to
retrigger promotions!

[Ubuntu-phone] Landing team 27.01.14

2014-01-27 Thread Didier Roche


Hey guys,

We had multiple images over the week-end, those contains minor changes. 
Partial results on the maguro images which is preventing us to take a 
release decision on image #149.


Some random crashes on Unity8 which are not reproducible after rerunning 
a lot of them. So, this topic is on the radar (we'll have a look as well 
at tomorrow's image results).


We are still suffering from the same issues than last Friday on the 
qmlscene crash. Ricardo is looking at it at the moment. In addition, a 
new introduced flaky test from music app appeared. This test is skipped 
as we speak with upstream agreement as it needs a lot of work and 
testing to go green on maguro.


Meanwhile, we tried to be really conservative and touch unrelated work 
for tomorrow's image:

- address-book-app AP tests fixes
- new indicator-power for android 4.4 support
- the components revert + fixes that are discussed above.

Won't sum up the going green as no visible progress today, let's 
continue to converge on a promotable image.

Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 28.01.14

2014-01-28 Thread Didier Roche

Hey,

We are seeing similar test results than the past image. However, we
still have the pending qtubuntu issue making qmlscene crashing. Ricardo
is still working on it. We are waiting (and polling :p) for a sign of hope.

So, unexpected Unity8 crashes were really random and not happening
anymore. We still keep them on the radar.

However, we saw a real new regression: If you open the accounts page in
the settings app and close it you can't reopen it[1]. Robert is
bisecting the latest image to find the guilty component (we have some
idea of what's causing it). We are actively working on getting this
fixed for tomorrow.

We think that
https://code.launchpad.net/~pitti/dialer-app/drop-expected-crash/+merge/199754
may fix the dialer-app crash. We are working with upstream to get this
fixed through the self-service CI Train system.

On the bright side, the 150 image is bringing us:
- address-book-app way more AP tests (and they all pass)
- new indicator-power for Nexus 7 2003 support
- new autopilot landed, without app crashing or more issues

Meanwhile, more and more training is happening in the CI Train and we
start to see the first builds and landings like the new autopilot
previously mentioned through the new process. We still have of course
the old good ubuntu-system-settings which is landing successfully
regularly. We will publish some big parts like Mir, only when the next
image is promotable though.

More news on going green when we can start promoting a new image.

Cheers,
Didier

[1]
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1273781

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] Landing team 28.01.14

2014-01-28 Thread Didier Roche

Le 28/01/2014 17:41, Kévin PEIGNOT a écrit :

I think you mean Nexus 7 2013 ^^

yeah, hard and long day today and that accumulates ;)
Thanks for the typo fix!

Le 28 janv. 2014 18:35, Didier Roche a écrit :

Hey,

We are seeing similar test results than the past image. However, we still have
the pending qtubuntu issue making qmlscene crashing. Ricardo is still working
on it. We are waiting (and polling :p) for a sign of hope.

So, unexpected Unity8 crashes were really random and not happening anymore. We
still keep them on the radar.

However, we saw a real new regression: If you open the accounts page in the
settings app and close it you can't reopen it[1]. Robert is bisecting the
latest image to find the guilty component (we have some idea of what's causing
it). We are actively working on getting this fixed for tomorrow.

Meanwhile, more and more training is happening in the CI Train and we start to
see the first builds and landings like the new autopilot previously mentioned
through the new process. We still have of course the old good
ubuntu-system-settings which is landing successfully regularly. We will publish
some big parts like Mir, only when the next image is promotable though.

More news on going green when we can start promoting a new image.

Cheers,
Didier

[1]
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1273781

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 29.01.14

2014-01-29 Thread Didier Roche


Hey everyone,

We are promoting image #151. \o/

We based the promotion decision on the facts that:
* dogfooding results are as good as the previous promoted image
* the online-account settings bug isn't a new bug after some more testing
* we discussed in the previous days about the qmlscene crash[1]. After 
more talk and investigation from Ricardo, the bug isn't new and is in 
the way the application manager register application which then fail 
during initialization. This particular bug is going to be fixed, but is 
not a new one. The crash is a side-effect of this. However we don't have 
crash files for applications behaving wrongly at startup. We think, it's 
related to the maguro issue that Dave reported and mentioned 
previously[2]. Those only seems to be related to a slower hardware (so 
maguro for now).
-> This second bug will need to be fixed (but happen in 3 different apps 
randomly). The QA team can help in having us understanding if we have an 
application crash or if a test or behavior is really flaky with 
autopilot using upstart stop  instead of killing them. 
Julien, can your team help in providing that change? We opened 
https://bugs.launchpad.net/ubuntu/+source/autopilot/+bug/1274139 to 
track and discuss this.
* on the AP test results themselves, we had a webbrowser failure on mako 
related to random crashes on the system (maliit-server and in another 
try webbrowser-app). However, it's really inconsistent and not 
reproducible. Lukasz is retracing the maliit-server one which doesn't 
seem to be related to any recent landing. Siva is going to retrace the 
second one.


This promoted image compared to yesterday contains:
* disabling the osk predictive text so results are shown while typing in 
the search field

* more configuration changes for Nexus 7 2013

We are helping upstream to get to the new CI Train workflow and will get 
a bunch of landing shortly. However, because publishing everything, we 
are going to rekick an image as we speak.


Cheers and hopefully, some news again on going green tomorrow!
Enjoy your new promoted image!
Didier


[1] 
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1271879

[2] https://bugs.launchpad.net/unity8/+bug/1268693
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] 154 image - mako doesn't boot

2014-01-30 Thread Didier Roche


Le 30/01/2014 13:43, Alan Pope a écrit :

On Thu, Jan 30, 2014 at 1:30 PM, Łukasz 'sil2100' Zemczak
 wrote:


On 30.01.2014 13:18, Alan Pope wrote:

Hi,

On Thu, Jan 30, 2014 at 1:08 PM, Sebastian Gomułka
 wrote:

Is it just me or others also have problem with booting the phone after
updating to 154 image?


I'm seeing it boot, but it's sticking at the google screen.

Looks like mir isn't starting.
Getting this at the end of my unity8 log.

file:///usr/share/unity8/Panel/MenuContent.qml:105:21: QML Loader:
Binding loop detected for property "indexActive"
Library unity-mir not found/loaded

Cheers,


Looking at the package changes in the image, I really don't like the
'dropped libunity-mir1 package'. Why was it dropped? I guess it might be
related.


Yeah, installing libunity-mir1 via apt-get on the phone fixes it. Thanks.




FYI a fix in unity8 is currently under CI Train and will be released 
ASAP. We'll kick the next image after that.


--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 30.01.14

2014-01-30 Thread Didier Roche


Hey,

short message again today.

So, we got image #153 promoted today \o/
Tests results have the known flaky tests. There is no a lot of 
difference in term of image content, but nice to confirm that nothing 
regressed. Dogfooding on mako and maguro helped to confirm that.


We built image #154 with a lot of changes including unity8, systemd, 
scopes, upstart-app-launch, powerd, cordova, X11 build fixes. However we 
got one library accidently dropped and the image couldn't start (see 
other message in the same mailing list). This was fixed and image #155 
is now building. We are slowing down the landings to get test results 
first as we got a lot of changes in one shot and need to know the 
current state before moving further.


So, let's be patient to avoid jamming the machine :)
Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 03.02.2014

2014-02-03 Thread Didier Roche


Hey,

The regression hunting continued today. We had multiple random 
application tests failing on the 3 images over the week-end. The issue 
was in the image from Friday.


We found that the applications doesn't seem to randomly starts even on 
mako and upstart-app-launch was reverted to last good-known version. We 
asked to modify the testing plan to include explicitly running 
applications AP tests to be able to catch this in the future.
https://bugs.launchpad.net/upstart-app-launch/+bug/1275017 is the bug to 
track it upstream. They are currently debugging and working on fixing those.


With that done, image #161 was kicked in containing that fix. However, 
due to infrastructure issues, we don't have yet all test results, they 
are getting rerun. Let's hope all AP tests pass now.


However, dogfooding on that image showed another regression (click apps, 
when installed, are redirecting to a wrong installation slot). After 
some bisecting in images and then in packages, we found the unity8 
version creating it (even trying versions that were never into the 
image). It's reported in https://bugs.launchpad.net/unity8/+bug/1275832. 
We reverted it and upstream is looking at fixing this.


On another note, the dialer-app crash fix didn't fix the crash on mako 
when running the tests. The upstream team is trying to investigating 
more on why they can't reproduce it locally where we get it every time 
on the CI infra.


Something else to look for: another regression, but it seems to be 
random (we couldn't all reproduce it and need more infos): 
https://bugs.launchpad.net/webbrowser-app/+bug/1275855.


Current plan is to kick image #162 once the unity8 reverts is in and get 
test results tomorrow morning. Let's cross fingers that all tests pass, 
no regression in dogfooding, and the latest mentioned issue isn't new.


Cheers,
Didier
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] Landing team 03.02.2014

2014-02-03 Thread Didier Roche


Le 03/02/2014 18:17, Didier Roche a écrit :

Hey,

The regression hunting continued today. We had multiple random 
application tests failing on the 3 images over the week-end. The issue 
was in the image from Friday.


We found that the applications doesn't seem to randomly starts even on 
mako and upstart-app-launch was reverted to last good-known version. 
We asked to modify the testing plan to include explicitly running 
applications AP tests to be able to catch this in the future.
https://bugs.launchpad.net/upstart-app-launch/+bug/1275017 is the bug 
to track it upstream. They are currently debugging and working on 
fixing those.


With that done, image #161 was kicked in containing that fix. However, 
due to infrastructure issues, we don't have yet all test results, they 
are getting rerun. Let's hope all AP tests pass now.


However, dogfooding on that image showed another regression (click 
apps, when installed, are redirecting to a wrong installation slot). 
After some bisecting in images and then in packages, we found the 
unity8 version creating it (even trying versions that were never into 
the image). It's reported in 
https://bugs.launchpad.net/unity8/+bug/1275832. We reverted it and 
upstream is looking at fixing this.


On another note, the dialer-app crash fix didn't fix the crash on mako 
when running the tests. The upstream team is trying to investigating 
more on why they can't reproduce it locally where we get it every time 
on the CI infra.


Something else to look for: another regression, but it seems to be 
random (we couldn't all reproduce it and need more infos): 
https://bugs.launchpad.net/webbrowser-app/+bug/1275855.


Current plan is to kick image #162 once the unity8 reverts is in and 
get test results tomorrow morning. Let's cross fingers that all tests 
pass, no regression in dogfooding, and the latest mentioned issue 
isn't new.


Cheers,
Didier



Ok, some follow up:
the image #162 failed to build due to ubuntu-html5-theme package that 
was supposed to not be uploaded that entered the archive, making the 
Touch image not buildable.


Same rules for everyone, we revert it. A new build will be kicked by the 
foundation team as soon as it's published.

Cheers,
Didier
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] Landing team 03.02.2014

2014-02-03 Thread Didier Roche


Le 03/02/2014 20:18, David Barth a écrit :

Le 03/02/2014 14:36, Didier Roche a écrit :

Ok, some follow up:
the image #162 failed to build due to ubuntu-html5-theme package that 
was supposed to not be uploaded that entered the archive, making the 
Touch image not buildable.

Can you provide a pointer to the build failure?

I'd like to know which broken dependency is still holding back this 
release.


David


You can find the logs (and all links to build failure) here: 
http://irclogs.ubuntu.com/2014/02/03/%23ubuntu-release.html#t19:10. It 
doesn't hold back the image as it's reverted for now and we kicked in a 
new image.


Cheers,
Didier


--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 03.02.14

2014-02-04 Thread Didier Roche


Hey,

We were able to get back to a promotable state. Image #161 is now the 
latest and greatest of ubuntu touch.
This image contains all the changes and the reverts discussed in 
yesterday's email. We dogfooded the image ourself on both mako and 
maguro and everything seems green.


After that and some protobuf transition (in image #162), we don't see 
any regression compared to usual crashes and flakyness. The new AP test 
failure on unity 8 is a test that was ignored recently but failing again 
by the revert.


So, now that we were back to green, we worked on:
- fixing the packaging conflicts and republishing ubuntu-html5-theme
- getting Unity8 containing yesterday's regression fix (with a test!), 
various cleanup and improvements as well as getting upstart timeout when 
a crash happened (hopefully not anymore smashed stacktrace)

- an indicator-datetime rewrite in C++
- various build fixes for platform-api and location-service with latest 
dbus-cpp


To sum up, on yesterday's revert:
- unity8 is now fixed
- ubuntu-html5-theme will be in tomorrow's image
- upstart-app-launch is the latest that is still reverted.

We also assigned various slots, like for getting latest Mir, some fixes 
in the apps, and other backend components. That should enable us to 
continue to flush the queue while keeping everything under sanity. For 
getting fresh results, we are about to kick a new image soon as most of 
those components are published in the release pocket.


Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] Landing team 03.02.14

2014-02-04 Thread Didier Roche


Le 04/02/2014 17:37, Michał Sawicz a écrit :

On 04.02.2014 18:23, Didier Roche wrote:

After that and some protobuf transition (in image #162), we don't see
any regression compared to usual crashes and flakyness. The new AP test
failure on unity 8 is a test that was ignored recently but failing again
by the revert.


Ignored? I'd venture to say it was fixed, but the revert reverted the 
fix, too.


I saw on the CI train, part of this landing description:
"- skip broken test"

I was thinking it was that test, but maybe it was another one?

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 05.02.14

2014-02-05 Thread Didier Roche


Hey

We hit 2 regressions today on the 2 images that were produced: 163 and 164
- location-service is taking 90% of the CPU. The fix is just finished 
upstream. dbus-cpp (where we can't flush trunk, so we have direct 
uploads needed to a silo) and location-service will fix those. There is 
no easy way to back them out, so we had to wait for a fix.
- latest protobuf version, as in the desktop, is preventing any 
application to start. The fix is in for a few hour, so just waiting for 
an image to be kicked in.


However, dbus-cpp isn't in a good shape in term of ABI. We are taking a 
pragmatic decision to unblock the whole chain. This change won't be 
merged upstream though.
Once location-service fix is in (will probably be still a couple of 
hour, time to build, test and migrate), we are going to build a new image.


The upload of xorg-server into the archive delayed the Mir landing. 
Testing is done, but we will get it published only once a new image is 
kicked and we are sure we are in a good state. All other landings are 
blocked on the new image to be kicked in as well.


We are growing the knowledge around CITrain, and now, the whole landing 
team should have all required knowledge to help executing this process.


That's it for the news of the day,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 06.02.14

2014-02-06 Thread Didier Roche


Hey,

Good news today! we were able to promote images 166 \o/
* 165 contains:
- location-service/dbus-cpp fixes that were spinning CPU to 90%
- the libprotobuf fix to be able to …hem… run an application
* 166 contains:
basically a new Mir which landed *flawlessly* :)

Thanks to all upstream landers involved and the landing team to work 
that hard to get everything's in. We are now back in a good state. The 
Unity8 crash on stop seems to be mostly gone as well. Let's wait for a 
couple of images to confirm that.


We kicked as well image 167 which contains a whole new autopilot 
version. The results looks pretty good for now (mostly all done) as 
well. However, we have one unity8 test failure. To know if it's due to 
the autopilot landing or being flaky (behavior or test) is under 
investigation by both upstream and Paul who will followup on this email.

http://ci.ubuntu.com/smokeng/trusty/touch/maguro/167:20140206.1:20140115.1/6480/unity8-autopilot/741839/

We helped and got a lot of landings for the next image that we just 
kicked in. Everything seems pretty smooth so far. Let's hope that will 
continue that path.

Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 07.02.14

2014-02-07 Thread Didier Roche

Hey,

We had 2 images built today. No promotion yet though.
168:
- got latest of mediascanner version 2 without grilo support
- a newer version of friends with many bug fixes
- added support in HUD to quit apps (backend only)
- Some Qt fixes
- few changes in icon theme

169:
- new lxc beta
- dialer-app support for call hold and bug fixes

However, we saw and worked on multiple regression:
* music-app didn't get any test passing for good reason (application
spinning at startup). After investigation, we needed to seed grilo back
which was dropped due to lack of dependency. (only music-app which is
click is using it). Lukasz fixed it
* we investigate the qmlscene crash which is the usual crash getting fix
in an incoming upload of unity-mir
* we got more tests as ubuntu-system-settings is now running their AP
tests on their phone. However, there is one test which looks flaky. The
desktop team is looking into it.
* Mathieu fixed lxc crashing at every startup (even if that wasn't
affecting the user experience apart from the CPU used to collect the
stacktrace).
* there is another (in addition to the one yesterday) test failing in
the Unity8 AP suite. We hold on on this one while the QA, upstream and
us are investigating to know if the issues are real bugs, flakyness of
the tests or behavior. The issues are on maguro and so, once the
emulator is one, can as well impact this latter.

http://ci.ubuntu.com/smokeng/trusty/touch/maguro/168:20140206.2:20140115.1/6490/unity8-autopilot/744272/
and the one from yesterday:
http://ci.ubuntu.com/smokeng/trusty/touch/maguro/167:20140206.1:20140115.1/6480/unity8-autopilot/741839/

We kicked image 170 with the fixes mentioned above with some other safe
landings:

* fix incorrect orientation of keyboard on tablet
* some html5 themes enhancements

Let's wait for the test results to see if we can promote that new image.
Meanwhile, safe landings are building in their own silos.

Cheers and have a good week-end,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 12.02.14

2014-02-12 Thread Didier Roche


Hey,

First, I want to thanks Lukasz for his excellent work on the last couple 
of days. I know it was tough, but we keep getting work done!

Since the last email, we got 2 images built:

175:
* This one was all about nested Mir mode being back. That's aligned as 
well with the 4.4 android port.


176:
* Fix for the qmlscene crash that we discussed a while back, blocking 
applications that failed on startup to be able to register a surface on 
Mir if they fail early. Note that this doesn't fix the application 
itself failing at startup, but at least, you are able then to relaunch it.

* New Unity8, mostly with more support for the incoming scope preview work.
* New webapps container bug fixes.

This image is getting promoted!

We see that the system settle is higher than what it was in previous 
images. Multiple components seems to sit on top, 
unity-system-compositor, ophono-simd… That can be nested mir related… 
Oliver discussed about it with upstream and a bug 
(https://bugs.launchpad.net/mir/+bug/1279391) was filed. This won't be 
considered as a blocker for now, but we'll keep it closely on our radar 
with upstream's help.


We still have the regular flaky test which seems to be similar than the 
application not starting first (but we don't have the same issue that 
all following tests are failing then). Also, the previously accepted 
unity8 test failure is still around. I see more Unity 8 work getting in 
in the incoming images, let's hope they are going to fix this.


We had some troubles due to Google App Scripts failing and creating 
random issues on the CI Train. We spent quite some time to debug and try 
to workaround it. However, the issue is not present anymore after few 
hours (and this service seems to be known to have some transient 
issues). Everything should be back to normal. We tried to recreate (the 
spreadsheet was reverted) the same state than this morning and let then 
more and more work getting in for the next image… which we are just 
kicking in!


Cheers,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] MAKO #179

2014-02-13 Thread Didier Roche


Le 13/02/2014 12:11, gio.sc...@gmail.com a écrit :

Hi all,

after updating to #179 Mako won't boot.

Only for me ?

Thanks

Ciao
Gio






Doesn't seem so, we are still looking at promoting 178.
Investigation on 179 is under progress.
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] MAKO #179

2014-02-13 Thread Didier Roche


Le 13/02/2014 13:00, gio.sc...@gmail.com a écrit :

Thanks for the reply,

 unfortunately i have seen too late the fail on image testing.

My mistake.


No worry!

So, we found that ubuntu-touch-session is the issue on that image. We 
are looking quickly what's the logic in the simple change (which should 
have impacted the x86 emulator only). If not, we are reverting in the 
next 30 minutes, publish and rekick an image.


Unfortunately, we'll have mixed autopilot and Mir result on the next one 
then, let's hope that 180 won't shows any regression.

Cheers,
Didier
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] MAKO #179

2014-02-13 Thread Didier Roche


Le 13/02/2014 13:15, Didier Roche a écrit :

Le 13/02/2014 13:00, gio.sc...@gmail.com a écrit :

Thanks for the reply,

 unfortunately i have seen too late the fail on image testing.

My mistake.


No worry!

So, we found that ubuntu-touch-session is the issue on that image. We 
are looking quickly what's the logic in the simple change (which 
should have impacted the x86 emulator only). If not, we are reverting 
in the next 30 minutes, publish and rekick an image.


Unfortunately, we'll have mixed autopilot and Mir result on the next 
one then, let's hope that 180 won't shows any regression.

Cheers,
Didier


The exact issue and fix was found (missing an executable bit in one 
script). It's currently building/moving to distro. We'll kick an image 
build as soon as it's done.


Cheers,
Didier
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

Re: [Ubuntu-phone] MAKO #179

2014-02-13 Thread Didier Roche


Le 13/02/2014 13:41, Didier Roche a écrit :

Le 13/02/2014 13:15, Didier Roche a écrit :

Le 13/02/2014 13:00, gio.sc...@gmail.com a écrit :

Thanks for the reply,

 unfortunately i have seen too late the fail on image testing.

My mistake.


No worry!

So, we found that ubuntu-touch-session is the issue on that image. We 
are looking quickly what's the logic in the simple change (which 
should have impacted the x86 emulator only). If not, we are reverting 
in the next 30 minutes, publish and rekick an image.


Unfortunately, we'll have mixed autopilot and Mir result on the next 
one then, let's hope that 180 won't shows any regression.

Cheers,
Didier


The exact issue and fix was found (missing an executable bit in one 
script). It's currently building/moving to distro. We'll kick an image 
build as soon as it's done.


Cheers,
Didier




The image is now built, automated testing is in progress.

Didier
-- 
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 13.02.14

2014-02-13 Thread Didier Roche


Hey,

4 images built since yesterday, on promotion (image #178), some image 
even didn't boot but now is fixed! Read the hot news of the day :)


What entered into those few images?

Image 177:
- new autopilot, enabling display resolution using fbset. This enables 
to support more device that before. Also, it has some UTF8 fixes.

- new hud to fix some potential crashers
- new gstreamer plugins and refreshed langpacks

Image 178:
- new unity8 with some more tests and improved preview image work

Image 179:
- this one contains some dialer-app changes
- ubuntu-touch-session configuration change for x86 emulator support 
(but this had a collateral issue)

- some webapps work

-> This image never started as an executable bits was missing, we 
identified the issue in ubuntu-touch-session and Oliver fixed it.


image 180 contained:
- the ubuntu-touch-session fix for above.
- new autopilot fixes for unity7 mostly.

This one is built and executing tests as we speak. As soon as the tests 
results are telling we don't have regressions, a new image (181) with 
latest Mir will be kicked in.


We have a lot of desktop components flying (unity 7) as well as a long 
of incoming touch work (apps, scopes, middleware) are in the pipeline, 
but we'll get that in the incoming and fresh images!


On the testing front, we have one new regression on the toolkit. Timo 
talked with upstream and it seems that the next ubuntu-ui-toolkit has a 
fix to make that flaky behavior better. The other failures are flaky 
tests on mako and maguro and Nicholas will give a report soon on them.


Enjoy #178!
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 14.02.14

2014-02-14 Thread Didier Roche


Hey,

NOTE TO LANDERS: we probably LOST some requests of landing due to google 
spreasheet reverted without any action 17 hours ago. Please read the end 
of this email.


So, we got multiple images built since yesterday and one image promoted 
(181):

181:
- new Mir stack with performance fixes, new pid interface for shell and 
some screen cast possibility (in alpha)

- new mediascanner scope backend work

-> seems the system settle issues are now good with this new Mir

182:
- new upstart-app-launch adding unregister signal for resume
- minor changes in the icon set

183:
- an ubuntu-keyboard fix
- the rc1 version of lxc
- camera-app and mediaplayer-app more desktop mode support.
(tests are currently running)

We got good dogfooding results on image 181. Results on mako are great, 
however, maguro regressed a little bit in unity8. Upstream is aware of 
it (see other messages), but it seems there are more urgent issues to be 
dealt with for them. Not seeing improvements, we had to take the 
decision to discare those results. Part of those failures can be that 
latest Mir seems to be slower on maguro.


We didn't get full maguro results on 182 before end of day and nobody 
present in the EU timezone knew how to rerun the tests, changing the 
phone to another target. That's the reason why we concentrated on 181 
for promotion. 182 now has all test results now.


We are then going to publish the SDK (ui-toolkit) and build another 
image with the minimal amount of changes, so that we can get pre/post 
toolkit results.


Please note that we again have some backend issue with google app 
scripts and so the spreadsheet for CI Train can get out of sync/has 
flawed results or revert the content. So the status that you are seeing 
in CITrain may not reflect the reality. This should sort out by itself 
(a RT has been opened yesterday), but feel free to ping the landing team 
for any help.


Due to that, we probably lost some of the requests, please do check the 
spreadsheet again if you have anything missing that we can't put it back.


Have a nice week-end everyone,
Didier

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-phone] Landing team 17.02.14

2014-02-17 Thread Didier Roche

Hey,

Multiple images built, and one promotion (image 188).

With the incoming 4.4 port and not enough traction to get issues on
maguro fixed, we decided to stop looking at those test results. Also, as
QA dogfooders with maguro are in the US west coast timezone for that
week, just a small and quick dogfooding is done on maguro.

So, what entered and what happens on those images?
184:
* new android config with more per-device persistence configuration
* new ui toolkit theme

185:
* some AP test fixes for camera-app
* new friends-app icon
* fix navigating photos requiring 2 swipes on gallery-app
* text copy and paste enabled
* new version of download-manager service was published, containing a
lot of work and the fix for being unable to download that people
mentioned on the same ML.

186:
* minor fix in android-config

187:
* some more work on gstreamer to be compatible with android 4.4

188:
* no change
-> dogfooding and tests on mako looked good, this one has been promoted.

We see some flaky test on camera-app[1]. A rerun has fixed is. Sivaa
pinged Olivier about it to get more infos. There are as well some crazy
process running on when it seems we are low on phone credit. Alan is
keeping an eye on it to open a bug if he can reproduce with more info.

It seems we have one minor regression[2], we decided that it's not going
to block the landing itself as we don't know if it's a design decision
or intended. Olivier is going to ask his colleagues and track that one.

Next image has just been kicked in, we asked it to be dogfooded in the
US timezone as well as getting test results. More details on how unity7
and other qtsensors changes impacts in tomorrow's email :)

Finally, the spreadsheet for landed had again some errors today. We
again had the spreadsheet reverted automatically and lost some lines +
getting some random errors on it. The RT requests has been transformed
in a support case opened at Google.

Cheers,
Didier

[1]
https://jenkins.qa.ubuntu.com/view/Trusty/view/Smoke%20Testing/job/trusty-touch-mako-smoke-daily/45/

[2] https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1281026

--
Mailing list: https://launchpad.net/~ubuntu-phone
Post to : ubuntu-phone@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-phone
More help : https://help.launchpad.net/ListHelp

1 2 3 >

1 - 100 of 217 matches

Mail list logo