ubuntu-phone team mailing list archive
-
ubuntu-phone team
-
Mailing list archive
-
Message #07506
Landing team 04.04.14
Hi!
Two image was published today and we worked mostly on covering last test
results due to lack of automation (the devices are dying in the lab on
reboot) as well as debugging the reboot hang. Some landings still went
through though! No promotion until we have the list of known blockers.
#276:
- Fix for the duplicate icons bug and click scope showing "?" instead of
characters (both previous blockers) in unity-scope-click
- qtdeclarative date format fix
- new lxc-android-config to generate ssh key while connecting the first time
- Fix unity8 under X11 and improve some tests, flush unity-api and
-notifications queue
- some udev fixes for cgmanager interactions
- improved mediascanner logging
- drop of ubuntuone application
- new base system changes like glib, gtk, systemd, plymouth…
Autopilot test results were manually processed by Timo. Possible
dialer/messaging app regressions were spotted in particular. This
enabled as well to land a new autopilot for #277.
#277 is just out, hot from the press!
- the reboot issue should be fixed (more info on the first item of
blocker list)
- a workaround in upstart-app-launch for a crasher due to incorrect
permissions
- new autopilot bug fix for invalid usernames showing sometimes in the
session menu
- apparmor, lxc, libvirt, lightdm, apparmor-easyprof-ubuntu delivered in
sync with new apparmor signal and ptrace mediation for userspace
- refreshed langpacks, the udev fix discussed in the blocker list, fixes
inherited from desktop in pulseaudio, lightdm, ibus…
-> the test in the CI datacenter are now reenabled. We hope to get test
results on that one soon.
* On the blocker list:
** Some phones are stuck while rebooting (Oliver G.)
https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1302174
This impacts the facility to be able to run the tests and can impact on
the user side as well (basically, you reboot and your phone is stuck at
the google logo).
-> We restarted this morning the investigations (discussions on the bug
report). It seemed to be linked to multiple uploads between
lxc/cgmanager/udev interactions. We even tried latest uploaded udev
fixing an issue when having no cgmanager
(https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1302264).
However, we didn't get any better result.
Oliver found a way to have 278 phone reboots without any hanging. This
involves disabling cgmanager and reverting to using cgroup-lite. This is
now uploaded and should be in #277. Automatic AP testing will be turned
on again and this should be part of history :)
** Music/Calendar bug (Qt event look stopping when the device is
suspend) (Saviq)
Discussion is happening and work is ongoing while discussing with
upstream. Was set as a blocker while whitelisted on the previous
promotion blocker.
-> QA told that they only will make that decision once we won't have not
any blocker left on the list.
** Scopes grey out and are unresponsive (Saviq)
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1300326
-> It happens on swiping the welcome screen and swiping apps to close them
** Dead area at bottom when scrolling in scopes (Saviq)
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1300302
-> Sometimes in the click scope the applications will shrink to 3 1/3
lines instead of 4 and other time it will shrink to 1 this is a user
facing issue but is easily fixed by scrolling up.
* Issues not impacting on the user experience or whitelisted by QA as
not a promotion blocker:
** qtubuntu crash causing the dialer app to crash (only during tests)
(Kevin)
https://bugs.launchpad.net/ubuntu/+source/qtubuntu/+bug/1297900
-> seems to only impact on tests, when the application isn't started by
upstart.
** Multiple crashes on images since the scope transition (Saviq)
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1256360
The other crashers are not reproducible anymore. However, we still have
the systematic unity8 on stop crasher everytime you run the autopilot
unity8 test suite.
-> QA decided to whitelist that one.
That's it for this week!
Cheers,
Didier
Follow ups