ubuntu-phone team mailing list archive

[Łukasz 'sil2100' Zemczak <lukasz.zemczak@xxxxxxxxxxxxx>]

Hi everyone,

Today another day filled with battling our blocker bugs. But there are
good news - we seem to have all of the problems covered! The Ubuntu UI
Toolkit failure blockers both have people assigned and work-arounds
prepared; we hope to have them landed as soon as possible.

Another blocker being investigated are the boot problems on our manta
devices [1]. This seems to have been a problem since #137, actually
since the Mir 0.5.0 landing that happened around that time. It has been
assigned and is being worked on actively.

We have a lot of blockers currently, but almost all of them are in the
right hands currently. Let's work hard on getting those out of our way.

The list:


* What landed in our images:
http://people.canonical.com/~lzemczak/landing-team/

#141
- http://people.canonical.com/~lzemczak/landing-team/141.commitlog
#140
- http://people.canonical.com/~lzemczak/landing-team/140.commitlog
#139
- http://people.canonical.com/~lzemczak/landing-team/139.commitlog


* Smoke-testing results:
http://ci.ubuntu.com/smokeng/utopic/touch/

#141 mako
-
http://ci.ubuntu.com/smokeng/utopic/touch/mako/141:20140721:20140717.1/9172/
#140 mako
-
http://ci.ubuntu.com/smokeng/utopic/touch/mako/140:20140720:20140717.1/9155/
#139 mako
-
http://ci.ubuntu.com/smokeng/utopic/touch/mako/139:20140719:20140717.1/9141/


* Some useful documentation:
(Still under development)
https://wiki.ubuntu.com/citrain/ComponentSupportList
https://wiki.ubuntu.com/citrain/LandingTeam
https://wiki.ubuntu.com/citrain/FAQ
http://people.canonical.com/~platform/citrain_dashboard/


* Blocking issues:

** [1] Mir fails to start on Nexus 5 as it fails to turn vsync signal on
https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1345533
 -> Not only hammerhead but also on manta

** indicator-location crashing during default, sdk and click_image_tests
tests on smoketesting
https://bugs.launchpad.net/indicator-location/+bug/1338610
[Time counter 10/7]
 -> Charles and Thomas are looking into this one...

** Reproducible UITK failures on smoketesting
https://bugs.launchpad.net/autopilot/+bug/1328600
 -> Work-around prepared in a merge request for staging

** qmlscene crashed while running test_can_launch_multiple_applications
https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1329141
 -> CRITICAL! A work-around is prepared!

** test_go_to_root / home_must_open_the_root / home_directory fails
since mako #132
https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1342336
 -> Since this failure is reproducible locally and happens all the time
= blocker

** test_add_new_event_with_default_values & test_fill_form fail since
mako #137
https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1343916
 -> Since this failure is reproducible locally and happens all the time
= blocker


* Known issues:

** mtp-server crash when transferring music on #15
https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1317263
 -> Very old bug but gains on importance in the upcoming days

** Ringer only ringing once after upgrade to u94
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1334248
 -> Caused by some race condition, rarely reproducible, whitelisted from
the blocker list by QA

** Wrong WWAN value in saved-states
https://bugs.launchpad.net/ubuntu/+source/urfkill/+bug/1321627
 -> Issue still not fixed.

** U-S-S sluggish after some hours, high CPU
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1337200
 -> This issue needs help debugging and identifying


* Issues not impacting user experience

** Network indicator crash during dialer-app and messaging-app
smoketesting (Antti)
[Time counter 28/7 - Whitelisted]
 -> The crash will never happen in a normal environment, so we decided
to whitelist the problem. But a fix is in the works nevertheless.

** unity8 crashed with SIGSEGV in
mir::frontend::ClientBufferTracker::client_has()
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1339610
[Time counter 9/7 - Temporarily whitelisted]
 -> This problem has caused some rare test failures in smoketesting,
rarely reproducible it seems. Is this still valid? Might be related to
one of our blockers.


Best regards,

-- 
Łukasz 'sil2100' Zemczak
 lukasz.zemczak@xxxxxxxxxxxxx
 www.canonical.com