ubuntu-phone team mailing list archive

[Dave Morley <davmor2@xxxxxxxxxxxxx>]

On 04/03/14 17:30, Didier Roche wrote:
> Another day, another image.
> 
> Still landing degraded mode, some reverts, more landings and spreadsheet
> issues. Busy day again!
> 
> Note that the google spreadsheet created issues over the day again.
> Seems to have settled down now. The backend results have been manually
> reconciliated with the frontend part and I took regular backup to try to
> not miss any request. Please check if your request disappeared during
> the day.
> 
> 
> #219:
> * android/hybris fixes for the camera issue itself. This big one is
> fixed now \o/
> -> However, it seems there is maybe still another camera issue. Selene,
> Alan and Dave are working on providing more infos.
> * ofono fix for the crashers yesterday. There is still one pending, but
> this one was appearing before (however, it seems apport wasn't reporting
> it), hence the fact we didn't see it earlier. We decided it's fine to
> ignore it for now until Martin is back (doesn't impact tests and only
> happen with the ofono phonesim mock installed).
> * some packaging work which will enable us to not depends on the whole
> set of gstreamer1.0-plugins-bad packages
> * new autopilot to export non visual components from qml projects + bug
> fixes
> 
> The tests results was similar than previous image (with the same Qt 5.0
> crashes making some tests randomly fail).
> 
> However, some unity8 tests reliably failed and Michal reported it[1]. We
> reverted autopilot-qt and autopilot (part of the transaction). We
> avoided reverting xpathselect which was part of the transaction as well
> but only contained packaging changes.
> Corey, can you ensure that unity8 AP tests are part of the autopilot
> test plan? I think you will need to have a wiki page like most projects
> with the autopilot test plan now and including a big suit of tests to
> run (or add them to the autopilot tests themselves).
> Feel free to ask for another landing or reuse the same silo to reland
> your changes once you have the fix and the tests.
> This revert will be part of image #220.
> 
> To come back to the image, with the camera issues fixed, we have as
> blockers for promotion:
> 
> 1. Clock apps flaky tests (Nicholas + Leo)
> Didn't see any clock apps published yet, pending on update on that one,
> knowing that a new bug is exposed though with the tests[2].
> 
> 2. Weather-app seems have reproducible failures (Nicholas + Leo)
> This impacts both user experience and tests (application stuck at
> start). No way to know when it started with the switch, so not easy to
> revert with all the churn (as the erratic behavior started at the same
> time than 4.4 switch). Lea reported [3]. Seems it can be due to server
> side issue, but the application should degrade more gracefully (and the
> tests not depending on it then). Upstream is looking to it with Nicholas.
> 
> 3. Ensuring that we can promote the image with the Qt 5.0 crasher. (Dave
> + Selene)
> Dave seems to have reproduced the Qt 5.0 crash and that impacts the user
> experience. Dave, care to expand here if it's a clear +1 or -1 from the
> QA team… meaning, if the 2 bugs above are fixed, can we safely promote
> an image before the 5.2 switch?
>

So there are two issues that result in the same error (d8f8 as it has
become known).

One is a qmlscene crash this tends to happen on opening data heavy apps,
weather app, calendar app, google plus app, facebook app, twitter app.
However it doesn't happen all the time and can easily be remedied by
swiping away the damaged window (Tends to just be grey/white) back to
the dash and clicking on the app till it opens correctly (2-3 times will
normally cover it).  This is mostly annoying but on the whole will lead
to a working app sooner rather than latter.

The second more serious unity8 crash with the same error restarts the
unity8 session, this would mean that anything the user was doing is
lost, the end.  Although it is serious if users are aware of the issue
then on the whole it is pretty hard to trigger.  Use the phone all day
get to a crashed window switch apps and switch back to the broken app
will normally trigger it (Online Accounts page seems to be a prime
candidate for that).

On Point one I think it is annoying but it would not lose people any work.
On Point two I think it is pretty hard to trigger, so as long as you are
not using your phone for critical production stuff you are safe.

I would give this a +1 if the other issues are resolved.  However I
would issue a warning for users of the known issues so they are aware.
The other thing I would recommend is if the issue exists in Qt5.2.1 on a
given image that it becomes a priority fix at that point rather than
trying to fix it now and maybe hit it again in 5.2.1.  (Hope that is
clear enough for you :))

> Cheers,
> Didier
> 
> [1] https://bugs.launchpad.net/autopilot-qt/+bug/1287727
> [2] https://bugs.launchpad.net/ubuntu-clock-app/+bug/1285958
> [3] https://bugs.launchpad.net/ubuntu-weather-app/+bug/1287446
> 
> 
> 


-- 
You make it, I'll break it!

I love my job :)
http://www.ubuntu.com
http://www.canonical.com

Attachment: signature.asc
Description: OpenPGP digital signature