ubuntu-phone team mailing list archive

[Olivier Tilloy <olivier.tilloy@xxxxxxxxxxxxx>]

On Mon, Jun 16, 2014 at 6:57 PM, Łukasz 'sil2100' Zemczak <
lukasz.zemczak@xxxxxxxxxxxxx> wrote:

> Hi everyone!
>
> After some discussion among our landing team, we decided to whitelist
> the filemanager autopilot failures and unblock image promotion. The
> problem is really hard to debug especially because the main upstream
> developers have no hardware to test it on. Problems with this test suite
> were visible from the very beginning of the utopic series as well, so it
> was no particular landing that could have caused the flakyness to start.
>
> We will keep this issue on our radar though and try getting rid of it as
> soon as possible.
>
> With this being said we decided to promote a new image to the stable
> channel today! Image #83 passed both our dogfooding and smoketesting
> criteria. It includes the revert of the split greeter, moving the
> feature back to Unity8's territory. This should decrease the memory-load
> of your Ubuntu Touch back to the previous footprint. #83 also includes
> the new platform-api v2 and upgrades to some of our core apps - enjoy!
>
> We also built image #84 today which includes the new, touch-only
> language packs instead of the desktop ones. It seems we gained around 40
> MB of disk space this way \o/
>
> In the meantime: upstreams, please mind the list! The counters are ticking!
>
>
> * What landed in our images:
> #84
> - http://people.canonical.com/~lzemczak/landing-team/84.commitlog
> #83
> - http://people.canonical.com/~lzemczak/landing-team/83.commitlog
> #82
> - http://people.canonical.com/~lzemczak/landing-team/82.commitlog
>
>
> * Smoke-testing results:
> http://ci.ubuntu.com/smokeng/utopic/touch/
>
> #84
> -
> http://ci.ubuntu.com/smokeng/utopic/touch/mako/84:20140616.1:20140530/8575/
> #83
> -
> http://ci.ubuntu.com/smokeng/utopic/touch/mako/83:20140616:20140530/8570/
> #82
> -
> http://ci.ubuntu.com/smokeng/utopic/touch/mako/82:20140614:20140530/8561/
>
>
> * Some useful documentation:
> (Still under development)
> https://wiki.ubuntu.com/citrain/ComponentSupportList
> https://wiki.ubuntu.com/citrain/LandingTeam
> https://wiki.ubuntu.com/citrain/FAQ
>
>
> * Known issues:
>
>
> ** Wrong WWAN value in saved-states
> https://bugs.launchpad.net/ubuntu/+source/urfkill/+bug/1321627
>  -> We had notice that this problem is still around... not a promotion
> blocker as it is with us already since some time
>
>
> * Issues not impacting user experience
> (will become blockers if not fixed after a while):
>
> ** File manager test problems
> https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1256856
> https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1329818
> [Whitelisted for now]
>  -> Work in progress... cause still unknown.
>
> ** Address-book-app autopilot failures (Bill)
> https://bugs.launchpad.net/address-book-app/+bug/1328158
> [Time counter: 6/7]
>  -> Test failures non-reproducible locally so it seems to be an
> autopilot problem. Still no movement here - can we get someone looking
> at this? The address-book-app landing that's prepared might fix the
> issue though...
>
> ** Autopilot failures in webbrowser-app during smoketesting runs since
> image #72 (Olivier)
> https://bugs.launchpad.net/webbrowser-app/+bug/1328605
> https://bugs.launchpad.net/webbrowser-app/+bug/1328867
> [Time counter 5/7]
>  -> Test failures non-reproducible locally so it seems to be an
> autopilot problem. With each image a different test is failing...
> Happened again, a different test failure. Correlation: wrong input in
> input field?
>

That’s the typical autopilot heisenfailure that’s really hard to debug as
it can’t be reproduced locally (several persons have tried multiple times)
and the logs we have from the smoke test runs don’t reveal much on what
could have gone wrong.

The wrong input is only one symptom of several other types of failures
which really seem to happen at random since image #72 (interestingly, not
in the last two images, #84 and #85).

I have summarized my findings in bug #1328605, the most likely explanation
for those random failures is the 0.2.0 landing of Mir in image #72.

I’m not sure where to take it from here.


** test_add_recurring_type_alarm_must_add_to_alarm_list(weekday) failed
> on mako, utopic#75 (Leo, QA)
> https://bugs.launchpad.net/ubuntu-clock-app/+bug/1328209
> [Time counter 5/7]
>  -> Leo has this on his radar - not reproducible locally. Did not happen
> recently... might be removed from the list.
>
> ** test_fake_home_fixture_must_copy_xauthority fails to create file on
> mako (Leo, QA)
> https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1326072
> [Time counter 3/7]
>  -> Fix commited, waiting for release in a silo. The silo still requires
> some love regarding other things inside. Counting time on this one as
> the silo is hanging for too long... Leo will try to get it released today.
>
> ** Network indicator crash during dialer-app and messaging-app
> smoketesting (Antti)
> [Time counter 5/7]
>  -> As updated by Antti, this is a troublesome crash - but being worked
> on. Still no update here... sometimes we get even 3-4 crashes per-image.
>
> ** qmlscene crashed while running test_can_launch_multiple_applications
> https://bugs.launchpad.net/ubuntu-app-launch/+bug/1329141
> [Time counter 2/7]
>  -> Bug incomplete, waiting for crash file to include more info
>
>
> Best regards,
>
> --
> Łukasz 'sil2100' Zemczak
>  lukasz.zemczak@xxxxxxxxxxxxx
>  www.canonical.com
>
> --
> Mailing list: https://launchpad.net/~ubuntu-phone
> Post to     : ubuntu-phone@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ubuntu-phone
> More help   : https://help.launchpad.net/ListHelp
>