ubuntu-phone team mailing list archive

[Didier Roche <didrocks@xxxxxxxxxx>]

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.

> - 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 :)
> 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