[02:04] <imgbot> [03:29] <imgbot> [03:29] <imgbot> [07:05] <dbarth> good morning
[07:40] <asac> hola
[07:40] <asac> hw does the image look like today? :)
[07:41] <sil2100> o/
[07:41] <didrocks> asac: quite good, but a lot of images in
[07:41] <didrocks> asac: seems, that all blockers but the Qt issues are vanished, we'll need dogfooders to confirm though for the webapps stuff
[07:41] <didrocks> asac: however, seems we still have the dialer-app flaky test for instance
[07:42] <didrocks> (so the branch that was supposed to fix it doesn't)
[07:46] <sil2100> On latest image smoketesting I also see some clock app flakyness
[07:46] <didrocks> yeah
[07:46] <didrocks> sil2100: hey!
[07:47] <didrocks> sil2100: I was wondering btw, do you mind looking at them before the meeting?
[07:47] <didrocks> like, ensuring it's real flakyness and see how they goes?
[07:47] <didrocks> (if you can reproduce, and so on)
[07:47] <sil2100> didrocks: ok, sure, I'm upgrading my device anyway
[07:47] <sil2100> So I will have a look
[07:48] <didrocks> thanks!
[07:56] <Mirv> there was even address book app failing test in #290
[07:58] <Mirv> I'll run a couple of test runs two for those three
[07:59] <sil2100> I'm running the test suite for dialer already if anything, but you could check the other two
[08:00] <didrocks> thanks Mirv!
[08:01] <Mirv> I think there's time to run all of those quite easily about ~two times before the meeting
[08:14] <ogra_> dialer seems really flaky ... i had random tests failing on and off over the weekend
[08:14] <ogra_> i wonder if its the new AP
[08:16] <sil2100> I just ran the whole suite 3 times just now and didn't get any failures, all the time just OK
[08:16]  * sil2100 has a lucky phone
[08:16] <sil2100> ;(
[08:19] <sil2100> Anyway, latest autopilot upload got rid of the python-evdev dependency (leaving only python3-evdev), but it's still required as python2.7 is used for dialer tests still
[08:20] <didrocks> sil2100: hum, so it's reinstalled?
[08:20] <didrocks> when installing the dialer-app AP test
[08:21] <didrocks> ogra_: I doubt that's the new AP then
[08:21] <didrocks> ogra_: only commit: http://bazaar.launchpad.net/~autopilot/autopilot/trunk/revision/480
[08:21] <didrocks> and so it's reinstalled :p
[08:22] <ogra_> bah
[08:23] <sil2100> I had to install python-evdev manually, since dialer-app-autopilot's deps didn't pull it in itself - I wonder how it's done on smoketesting infra
[08:24] <didrocks> sil2100: hum, interesting
[08:24] <didrocks> psivaa: would you know? ^
[08:24] <didrocks> something to bring up
[08:24] <ogra_> what happens if you dont ?
[08:24] <didrocks> are you sure it's not running the python3 flavor?
[08:25] <sil2100> ogra_: all tests fail straight away
[08:25] <ogra_> ok
[08:25] <sil2100> didrocks: I checked the logs, it says Loading tests from: /usr/lib/python2.7/dist-packages
[08:25] <didrocks> so either "something installs it beforehand"
[08:25] <didrocks> or they are using another path
[08:25] <didrocks> hum… ok
[08:25] <didrocks> so something should install it
[08:26] <didrocks> psivaa: can you check on the latest mako device if python-evdev was installed?
[08:26] <psivaa> didrocks: sil2100: looking
[08:26] <didrocks> thanks :)
[08:26] <sil2100> It has to be installed somehow since the tests start running - on my device without evdev bindings it was just barfing on the start
[08:27] <psivaa> didrocks: sil2100: 'Installed: 0.4.1-0ubuntu3'
[08:27] <didrocks> ok, maybe psivaa can tell us when it was installed
[08:28] <didrocks> (I guess it's at the global setup)
[08:30] <psivaa> that's being installed as a dep for unity8-autopilot
[08:30] <sil2100> Ah
[08:31] <ogra_> thats not python3 either yet
[08:31] <ogra_> ?
[08:31] <sil2100> Interesting
[08:31] <ogra_> i thought the tests were all switched when we dropped it
[08:31] <Saviq> cihelp, hey, we're having issues in otto runners... for some time now no unity8 autopilot test completes - the tests can't find the process, but there's no crash or nothing...
[08:31] <didrocks> ogra_: seems all that is puzzling
[08:31] <didrocks> oh, meeting time
[08:31] <didrocks> coming in 2 minutes
[08:31] <ogra_> Saviq, still the timeout ?
[08:31] <Saviq> ogra_, "the timeout"?
[08:32] <ogra_> Saviq, the CI bot had timeouts in the logs last week
[08:32] <psivaa> sil2100: didrocks: http://pastebin.ubuntu.com/7248624/ is the relevant snippet
[08:32] <Saviq> I can see "GLib-GIO-CRITICAL **: g_bus_watch_name: assertion 'g_dbus_is_name (name)' failed" in unity8 logs, that would eject into oblivion it wouldn't it
[08:32] <Saviq> ogra_, that's different, we're testing fine on devices, not on desktop, though
[08:33] <ogra_> ah
[08:33] <vila> Saviq, ogra_: weird, I thought fginther diagnosed it as requiring the otto nodes to be upgraded to trusty...
[08:33] <didrocks> psivaa: thank a lot!
[08:33] <psivaa> yw :)
[08:33] <ogra_> vila, yeah, seems i was wrong
[08:33] <vila> ogra_: not at all, the timeouts was the symptom
[08:33] <vila> were
[08:34] <ogra_> right, but they are not the issue here apparently
[08:34] <vila> ogra_: well, not the issue per se indeed
[08:43] <Saviq> sil2100, icanhassilo for row 32 please?
[08:44] <sil2100> Saviq: hi! It has some features in it, yes?
[08:44] <Saviq> sil2100, one, yes
[08:44] <Saviq> sil2100, test tweaks and other UI fixes otherwise
[08:44] <Saviq> sil2100, the one is real small, too
[08:46] <Mirv> additionally, dialer seems to sometimes work (all 9 AP:s just passed)
[08:46] <sil2100> Oh, ok - will it be easily 'revertable' in case something bad happens? SInce I see you have 2 components in the silo
[08:46] <sil2100> Mirv: same for me...
[08:46] <Mirv> I've the .crash files too, yes
[08:46] <Mirv> telepathy-ofono + dialer
[08:48] <sil2100> Saviq: for now I set QA sign-off needed to 'No', but I will consult with didrocks if it's the case here
[08:48] <sil2100> Assigning
[08:48] <Saviq> sil2100, thanks
[08:51] <sil2100> Saviq: had to correct the last merge URL as it was missing the last character ;) But besides that it should be assigned now to 001
[08:51] <Saviq> sil2100, craps, thanks
[08:52] <Saviq> ooh and a prime silo, too ;D
[08:52] <sil2100> ;p
[08:56] <Mirv> remember to use the premium silo only for premium landings!
[09:02] <Mirv> not getting clock to fail for me
[09:10] <mhr3> Saviq, aren't the indicator changes going to break the preview session?
[09:11] <Saviq> mhr3, no, the original manager only emitted the same signal, too
[09:11] <Saviq> mhr3, ah you mean that the session has to emit them, too?
[09:11] <mhr3> Saviq, right, but the preview session upstart job doesn't emit them now
[09:11] <Saviq> mhr3, right, forgot it's using a different job... :|
[09:11] <Saviq> it shouldn't, btw...
[09:12] <Saviq> ok /me drops that MP for now
[09:12] <Saviq> mhr3, thanks
[09:12] <mhr3> or add one to fix the preview session job ;)
[09:13] <Saviq> mhr3, yeah, will do that in the next instalment
[09:13] <Saviq> want to land this asap
[09:13] <mhr3> k
[09:14]  * Saviq needs to look into what the desktop session does...
[09:14] <popey> ogra_: do we block ping on the phone!?
[09:14] <ogra_> popey, so i was trying to land the gcmanager vs lxc-android-config change you tested ... but i couldnt even get the device to boot when i added the changes stgraber proposed in the bug ... do you remember if you had to do something special ?
[09:14] <popey> http://popey.com/~alan/phablet/device-2014-04-14-101410.png
[09:14] <popey> ogra_: i did
[09:14] <ogra_> popey, probably confinement blocks the teminal app ... i checked from adb last time it happened to me
[09:15] <popey> ogra_: http://paste.ubuntu.com/7219206/
[09:15] <popey> ogra_: i cant use adb if I am out and about ☻
[09:16] <ogra_> popey, sudo ping ...
[09:16] <ogra_> the user doesnt have permission to access the ICMP socket
[09:16] <ogra_> s/socket/protocol/
[09:17] <ogra_> (and the sudo in the terminal will reveal a beautiful bug to you too :) )
[09:17] <ogra_> (autocorrection printing the pw in clear text)
[09:17] <popey> would that be bug 1307386
[09:17] <popey> which I just filed
[09:17] <popey> oh, related
[09:18] <ogra_> well i'm more concerned by it printing the full password at the sudo password prompt
[09:18] <popey> do you have a bug for that?
[09:18] <ogra_> :)
[09:18] <ogra_> i dont think so
[09:18] <popey> I'll modify mine
[09:18] <ogra_> i noticed it last week the first time but forgot about it again
[09:19] <popey> there's a hint I think we can give the kb to switch those off I believe
[09:20] <popey> can you confirm bug 1307386 pls
[09:46] <sil2100> didrocks, Mirv, psivaa: sadly, even with a cleared out /var/crash I still succeed in dialer-app tests, tried 3 times already!
[09:47] <Mirv> :(
[09:47] <didrocks> sil2100: ok, and always the second one?
[09:47] <didrocks> ah
[09:48] <didrocks> but yeah
[09:48] <didrocks> that's prooving the point :)
[09:48] <didrocks> or not
[09:48] <didrocks> can be a different network as well
[09:48] <didrocks> while it's uploading
[09:48] <didrocks> let's see once psivaa has his results
[09:48] <psivaa> sil2100: curious if the the crash file generated during the tests after you clearing /var/crash ?
[09:48] <didrocks> in the same network conditoin
[09:49] <psivaa> device is flashing here btw
[09:49] <didrocks> thanks ;)
[09:52] <sil2100> psivaa: yes, on every test suite run I then have the dialer-app crash present again
[10:07] <dbarth> o/ sil2100: i have silo 006 ready for publication
[10:07] <dbarth> sil2100: this is a set of desktop fixes, so let me know which route it takes (archive or -updates)
[10:08] <sil2100> dbarth: oh, it's desktop only, yes?
[10:09] <sil2100> Awesome
[10:12] <sil2100> didrocks: oh, the 'packaging diff' generated by citrain/cu2d doesn't include debian/copyright changes?
[10:13] <sil2100> didrocks: anyway, two packaging ACKs needed for a desktop landing: https://ci-train.ubuntu.com/job/landing-006-2-publish/5/artifact/packaging_changes_webapps-applications_2.4.17+14.04.20140411-0ubuntu1.diff and https://ci-train.ubuntu.com/job/landing-006-2-publish/5/artifact/packaging_changes_unity-webapps-googledocs_2.4.16+14.04.20140411-0ubuntu1.diff
[10:14] <sil2100> didrocks: one of them also has some debian/copyright changes which are not visible here, but it seems fairly alright anyway
[10:20] <didrocks> sil2100: it should contains, are you sure it's missing?
[10:20] <seb128> sil2100, didrocks: can I get a silo for l34?
[10:20] <seb128> it's a security issue for unity lock screen
[10:20] <seb128> I hope it's working fine, it didn't get a code review yet, but trying to get some head start since nobody from the unity team seems to be around yet
[10:21] <sil2100> didrocks: yes, since see the webapps-googledocs diff and the merge https://code.launchpad.net/~abreu-alexandre/unity-webapps-googledocs/fix-pattern-and-store-cookies/+merge/214864
[10:21] <sil2100> seb128: assigning
[10:21] <seb128> sil2100, thanks
[10:21] <didrocks> sil2100: interesting, I may have some filters for that
[10:22] <didrocks> sil2100: +1 on both
[10:27] <dbarth> we did take the same terms as the previous google webapps we had packaged
[10:27] <dbarth> and so still going to the archive or updates?
[10:34] <seb128> sil2100, still working on assigning that silo?
[10:34] <seb128> sil2100, that might be a candidate for respinning trusty iso, so would be nice to get thing moving
[10:36] <popey> davmor2: "Play in Grooveshark" button in the grooveshark scope does nothing here...
[10:36] <Chipaca> sil2100, Mirv, didrocks, could I have a silo for row #35 please?
[10:36] <didrocks> seb128: seems he didn't see the conflict: https://ci-train.ubuntu.com/job/prepare-silo/197/console
[10:36] <didrocks> seb128: unity7 is in landing-008
[10:36] <didrocks> should we flush/join to that one?
[10:36]  * didrocks looks
[10:37] <didrocks> interesting… doesn't seem landing-008 is assigned in the spreadsheet
[10:37] <didrocks> I guess someone removed a line…
[10:37] <didrocks> Mirv: can you handle Chipaca's request meanwhile?
[10:37] <davmor2> popey: I justed typed in Happy clicked on it, click on play in grooveshark an now I am playing the track
[10:38] <popey> davmor2: works now I have rebooted
[10:38] <didrocks> seb128: someone added that one:https://code.launchpad.net/~beidl/unity/unity-lockscreen-gestures/+merge/215569
[10:38] <seb128> didrocks, no, landing 008 is the mp I was asking to get, seems like it's the mainscreen that just didn't get the info reflected
[10:38] <popey> ignore me
[10:38] <seb128> didrocks, thanks
[10:38] <didrocks> seb128: hum
[10:39] <didrocks> oh right
[10:39] <didrocks> misread
[10:39] <seb128> didrocks, c34 seems to be empty
[10:39] <sil2100> seb128: it's assigned since longer
[10:39] <seb128> e.g not formula
[10:39] <didrocks> but I guess it was assigned too long
[10:39] <sil2100> seb128: ah, the field is empty... sometimes that happens
[10:39] <didrocks> argh
[10:39] <seb128> didrocks, sil2100: thanks
[10:39] <didrocks> indeed
[10:39] <sil2100> didrocks: I noticed that happening from time to time ;/
[10:39] <didrocks> sil2100: why people remove the formula?
[10:40] <Mirv> didrocks: sure
[10:40] <sil2100> I have no idea ;/
[10:40] <didrocks> sil2100: that's annoying…
[10:40] <sil2100> But usually not only there it's removed
[10:40] <popey> davmor2: now lock the phone
[10:40] <didrocks> same with the formula
[10:40] <sil2100> didrocks: look, not only this one, also the M column went missing
[10:40] <didrocks> on the status
[10:40] <popey> davmor2: audio in webapps stops playing when phone in welcome screen
[10:40] <didrocks> I guess someone selected the line and set "clean"
[10:40] <sil2100> I doubt it it's removed by someone on purpose, hm
[10:40] <sil2100> Or that
[10:41] <didrocks> sil2100: there is nothing touching the status column
[10:41] <didrocks> really nothing
[10:41] <didrocks> so it has to be manual…
[10:42] <sil2100> hum, I already had to do re-create this twice last week, but I thought it got cleaned by accident
[10:43] <popey> davmor2: but it works fine when the phone is locked/suspended
[10:47] <davmor2> popey: that I can confirm
[10:47] <popey> filing a bug
[10:47] <davmor2> popey: no idea what is going on there
[10:47] <popey> not sure where app lifecycle stuff goes?
[10:47]  * popey files on webbrowser-app first
[10:48] <ogra_> unity-mir
[10:48] <popey> ok, ta
[10:48] <ogra_> popey, but this is expected behavior, webapps dont use the media-hub
[10:48] <popey> (yet?) ?
[10:49] <ogra_> dunno, if that even possible with the sandboxing model
[10:49] <popey> what package is unity-mir is in?
[10:49] <popey> -typo
[10:49] <ogra_> err, isnt that unity-mir ?
[10:49] <popey> Package unity-mir does not exist
[10:50] <ogra_> yet i see uploads for it :)
[10:50] <popey> not installed on my phone
[10:50] <popey> libunity-mir1 I imagine?
[10:50] <davmor2> ogra_, popey: but it works when the phone locks it's only when you hit the power button and go back to the welcome screen that it stops
[10:50] <ogra_> https://launchpad.net/ubuntu/+source/unity-mir
[10:50] <popey> davmor2: indeed
[10:50] <t1mp> should phablet-click-test-setup create a gallery_app directory in /home/phablet/autopilot on device?
[10:51] <ogra_> davmor2, it should stop when it locks as well
[10:51] <popey> wat
[10:51] <davmor2> ogra_: no that's why it so confusing
[10:51] <sil2100> Chipaca: hi! Could you add a description to the landing?
[10:51] <popey> that makes it useless
[10:51] <ogra_> unless someone hacked up powerd to not stop it
[10:51] <t1mp> ah nevermind gallery-app is in ~/autopilot/legacy-py2
[10:51] <sil2100> Chipaca: it is required that we know what for the landing is needed
[10:51] <davmor2> ogra_: try it
[10:51] <Chipaca> sil2100: hi! I'm ... trying to :)
[10:51]  * Mirv has now executed clock app AP tests without fails 14 times... filing a bug anyhow
[10:52] <Chipaca> sil2100: "because did.rocks told me to" sounds a little bit lame :)
[10:52] <ogra_> davmor2, i belive you :P
[10:52] <t1mp> fginther: do you know what may cause RuntimeError: Unable to instantiate any backends
[10:52] <t1mp> UInput: ImportError('No module named evdev',)
[10:52] <Mirv> psivaa: was it that after a rerun is made the old logs are gone forever? I did take a note of the failing clock app test before refreshing the page, but the logs aren't there I guess?
[10:52] <t1mp> fginther: when running gallery_app tests? see http://paste.ubuntu.com/7249001/
[10:52] <sil2100> ;p
[10:53] <sil2100> Mirv: you can get them on the jenkins instance
[10:53] <sil2100> (at least you should)
[10:53] <psivaa> Mirv: http://q-jenkins.ubuntu-ci:8080/job/trusty-touch-mako-smoke-daily/249/testReport/junit/ubuntu_clock_app.tests.test_alarm/TestRecurringAlarm/test_add_recurring_type_alarm_must_add_to_alarm_list_weekday_/ is the one you want?
[10:53] <Mirv> Chipaca: I guess it'd be something like "re-enable ubuntu-push for touch images"?
[10:53] <Mirv> psivaa: ooh!
[10:53] <sil2100> Mirv: don't assign until descriptions are there!
[10:53] <Mirv> sil2100: psivaa: thanks!
[10:53] <sil2100> ;)
[10:53] <psivaa> yw )
[10:53] <Chipaca> Mirv: sil2100: there
[10:54] <sil2100> Mirv: how do you know if you're not assigning a silo for a time bomb?! ;p
[10:54] <Mirv> sil2100: I'll not publish such a thing, but a fine description doesn't prevent a time bomb being planted to the silo :D
[10:54] <davmor2> ogra_, popey: same thing happens when you play music from a scope but I'm assuming that is change in the scope as when you remove the welcome screen the scope is now on the main music scope again
[10:54]  * Chipaca makes a note never to put “explode ALL the things” as the landing description
[10:55] <sil2100> ;)
[10:55] <ogra_> davmor2, i think ricmm knows that code quite well ... probably talk to him
[10:55] <davmor2> ogra_: infact the only way to have music play on the welcome screen is via music player
[10:56] <ogra_> right
[10:56] <ogra_> it should be the same for suspend though
[10:56] <ogra_> music-player is the only whitelisted application
[10:56] <ogra_> well, and the video player
[10:56] <davmor2> ogra_: but they all play on a screen blank (either power button press of wait for the phone to sleep)
[10:57] <ogra_> right, they shouldnt
[10:57] <ogra_> only the music and video apps should
[10:57] <davmor2> ogra_: yes they should honest :D
[10:57] <ogra_> but not the browser
[10:57] <ogra_> not by policy, no
[10:57] <popey> davmor2: ogra_ bug 1307430
[10:58] <popey> the policy is wrong then ☻
[10:58] <ogra_> with the media-hub landing landing this will change though
[10:58] <popey> \o/
[10:58] <sil2100> brb, going to prepare lunch
[10:58] <ogra_> only the media-hub will be able to keep on playing stuff
[10:58] <ogra_> other whitelists will be dropped
[11:12] <popey> libmtp seems a bit broken at the moment
[11:12] <popey> causing nautilus to lock up when transferring music
[11:16] <didrocks> Chipaca: uploaded ubuntu-touch-meta with the seed change and clicked on build package. The status is now "Packages built" once built. You can then test/set testing pass: yes. QA will be able to sign off afterwards.
[11:16] <Chipaca> didrocks: ok, will test as soon as my devices become available
[11:16] <Chipaca> (in the middle of a deep-cycle power test right now)
[11:16] <didrocks> thanks :)
[11:18] <davmor2> popey: blame ogra_ for that, he doesn't fix it but it helps ;)  then point the finger at cyphermox
[11:31] <ogra_> yay, ok, with the proper instructions the cgmanager stuff works
[11:32] <ogra_> i just tested it wrong
[11:43] <asac> are we green yet :)?
[11:47] <sil2100> asac: not entirely yet!
[11:47] <sil2100> Still some flakyness being battled
[11:49] <asac> sil2100: dialer still>?
[11:49] <asac> sil2100: anything that blocks promotion in there?
[11:49] <ogra_> can i have a silo for line 36
[11:49] <sil2100> Yeah, dialer... but at least we have some ideas
[11:49] <sil2100> ogra_: looking
[11:49]  * sil2100 still lunching
[11:50] <ogra_> take your time ...
[11:50] <asac> are those crashes in dialer crashes we dont care abotu (e.g. only on shut down?)
[11:51] <ogra_> no
[11:51] <ogra_> they happen randomly (not all image had both of them on the weekend for example) and there is an app crash too
[11:51] <asac> ogra_: so they are real crashes seen during end user use?
[11:51] <ogra_> nope
[11:51]  * asac wonders if we ever have hooked up error tracker
[11:52] <ogra_> they are real app crashes happening when testing though
[11:59] <psivaa> sil2100: didrocks: dialer app tests when run on their own without apport had more failures: http://q-jenkins.ubuntu-ci:8080/job/psivaa-trusty-touch-mako-smoke-daily/4/
[11:59] <psivaa> didrocks: sil2100: i'm running the whole apps tests to see if there is any improvement.
[12:00] <popey> davmor2: i see no videos in my video lens
[12:00] <asac> ogra_: what crashes are those?
[12:00] <psivaa> didrocks: sil2100: i need to go out for a  lunch time appt. will update you when i come back
[12:00] <asac> ogra_: do we have bugs?
[12:00] <ogra_> asac, there is a disaler-app crash when the test runs
[12:00] <davmor2> popey: I do
[12:00] <davmor2> popey:  you on 3g or wifi
[12:01] <asac> ogra_: no i mean real end user exposed crashes
[12:01] <asac> that happen when you use the fphone
[12:01] <popey> wifi
[12:01] <popey> i mean, not even local ones
[12:01] <davmor2> popey: oh that's bad.  I see both local and online content
[12:02] <ogra_> asac, i doubt it has real impact
[12:02] <davmor2> popey: I wonder if it is a race condition in mir/scopes or something
[12:02] <asac> ogra_: right. misread what you said then. onloy care for stuff that end users will see
[12:02] <asac> like useing the phone for 20 minutes -> .crash file
[12:03] <ogra_> yeah, that shouldnt happen
[12:03] <didrocks> psivaa-lunch: thanks, keep us posted :)
[12:04] <didrocks> popey: I've seen that on other scope once
[12:04] <didrocks> popey: had to reboot
[12:04] <didrocks> couldn't reproduce it
[12:04] <sil2100> hmmm
[12:04] <popey> didrocks: yeah, reboot "fixed" it
[12:06] <didrocks> popey: there is certainly a race… Doesn't seem to be common (but I guess due to new scopes)
[12:10] <davmor2> popey: put your phone to sleep, send an SMS to it.  When the indicator snap decision appears click on it, does it unlock the phone and open messages?  Once messages is open repeat the process does it do the same again or just display the keyboard?
[12:15] <popey> davmor2: the indicator snap decision appeared and disappeared before I could tap it. it's way too fast
[12:15] <popey> or i am old
[12:15] <ogra_> you have to snap it
[12:15] <ogra_> thus the name
[12:16] <davmor2> popey: bit of both ;)
[12:16] <popey> davmor2: confirmed
[12:16] <popey> http://popey.com/~alan/phablet/device-2014-04-14-131627.png
[12:16] <davmor2> didrocks: ^ bug
[12:16] <didrocks> davmor2: was it unlocking before?
[12:17] <davmor2> didrocks: yeap but I'll have to dig into when it broke
[12:17] <didrocks> popey: mind checking on latest promoted image?
[12:17] <popey> ya
[12:17] <didrocks> Saviq: any idea if this is on your side? ^
[12:18]  * Saviq looks
[12:18] <didrocks> no unlock when clicking on a snap decision
[12:18] <Saviq> davmor2, popey, it's bug #1233564
[12:19] <ogra_> i wonder if it is just another fallout of the blocked Qt event s
[12:19] <Saviq> or well, yeah ↑, too
[12:19] <didrocks> Saviq: seems it was working on latest promoted image though
[12:19] <didrocks> from what popey is telling
[12:19] <Saviq> didrocks, yeah, before Qt 5.0
[12:19] <asac> so a regression or not?
[12:19] <didrocks> or maybe the "ya" was "I'm going to test"
[12:19] <ogra_> didrocks, that had Qt 5.0
[12:19] <Saviq> didrocks, asac, yeah, Qt event loop
[12:19] <didrocks> ogra_: not latest promoted image
[12:19] <popey> didrocks: works as expected on 250
[12:20] <didrocks> and 250 is 5.2
[12:20] <asac> Saviq: didrocks: davmor2: so last prokmoted image had this?
[12:20] <ogra_> didrocks, oh, indeed, ignore my babbling
[12:20] <didrocks> ok, so a regression, and not linked to 5.2
[12:20] <Saviq> we promoted a Qt 5.2 image?
[12:20] <didrocks> yeah
[12:20] <didrocks> 3 weeks ago
[12:20] <ogra_> Saviq, yeah, with the special exception for the events bug
[12:21] <davmor2> Saviq: you really need to read the phone mailing list more ;)
[12:21] <didrocks> it's weird they are linking that to the qt event fix
[12:21] <Saviq> davmor2, was sprinting for 2 weeks :P
[12:21] <didrocks> so either it's not the real one
[12:21] <didrocks> either popey is lying :p
[12:21] <Saviq> davmor2, popey, please file a bug with unity8
[12:21] <didrocks> but I doubt that the Mir fix is going to fix it then…
[12:21] <ogra_> didrocks, whats weird about that ... phone behaves strange on wakeup ... can always be related to it replaying the events
[12:22] <ogra_> since it queues them
[12:22] <didrocks> ogra_: how would it be working on 250?
[12:22] <ogra_> no, not on 250 indeed
[12:22] <ogra_> generally though
[12:22] <didrocks> yeah, but here, it does, trying to handle that one first :)
[12:22] <didrocks> Saviq: so, we were nearly going to promote an image, that one is the blocker (if the Qt one is whitelisted)
[12:23] <ogra_> if anything is weird on wakeup i usually suspect this bug ... i can understand if others do it too
[12:23] <Saviq> didrocks, the other place where this could get introduced was right edge
[12:23] <didrocks> Saviq: as it was working with 5.2 already, it seems that we need to dig further
[12:23] <didrocks> ah
[12:23] <didrocks> davmor2: you are making that test on every dogfooding?
[12:24] <Saviq> unity8 7.85+14.04.20140401.3-0ubuntu1 was the first to have right edge, can you guys check?
[12:24] <didrocks> davmor2: popey ^
[12:25] <davmor2> didrocks: normally yes but I've not done a full dogfooding for a few days with one thing and another
[12:25] <didrocks> davmor2: urgh, do you know at least what was the last image where you tested that?
[12:26] <didrocks> right edge is in for a week and half for instance
[12:26] <asac> davmor2: how can this happen without escalation?
[12:26] <asac> davmor2: i mean you were surely aware that we are trying with highest pressure to get an image baked
[12:27] <davmor2> asac: it was testing the fixes that were landing before the silo testers were in place that was causing me not to complete a full dogfooding
[12:29] <davmor2> didrocks: so popey made a comment on 287, My last full test was 280 and ToyKeeper did 281 and 283
[12:29] <asac> davmor2: but you didnt escalate that - or at least delegated to selene to do full dogfood. anyway
[12:29] <asac> what can we do?
[12:29] <asac> is it a regression over last promoted image at all?
[12:29] <popey> didrocks: seems glitchy even on 250
[12:29] <didrocks> so, it was working on 283?
[12:29] <popey> sometimes it launches messaging sometimes nothing happens at all
[12:29] <asac> Saviq: can you repro this problem?
[12:29] <didrocks> popey: hum… so it can be this Qt bug?
[12:29] <popey> its certainly not reliable on 250
[12:30] <didrocks> ok, maybe it's the same with the latest one?
[12:30] <popey> I'd say this isnt a regression
[12:30] <popey> i just sent 6 messages to #250 and only raised messaging app once
[12:30] <asac> that would be kind of good, but lets be honest :)
[12:30] <didrocks> ok
[12:30] <didrocks> so first one
[12:30] <didrocks> was just being "lucky"
[12:30] <popey> lemme reboot and do again
[12:30] <popey> yeah, perhaps
[12:30] <didrocks> yeah, thanks :)
[12:30] <asac> also regardless of wheter it is a regression or not, we have to assess if this is a problem for a stable promotion
[12:31] <asac> and understand what introduced it etc.
[12:31] <didrocks> asac: agreed, seems Saviq is blaming the Qt bug
[12:31] <ogra_> probably rightly so :)
[12:31] <davmor2> didrocks: so it might be that when I tested on 250 I got the working one, but now on 294 it always seems broken
[12:31] <asac> if we can proof it started to  happen only with qt5.2 then that might be the case
[12:31] <asac> where is the qt bug fix?
[12:31] <asac> isnt mir having that ready in a silo?
[12:31] <asac> so wecould promote and then try that one
[12:31] <Saviq> didrocks, asac, yeah, everything that happens "after I unlock the phone after some time", is a suspect for the event loop issue
[12:31] <ogra_> ++
[12:32] <asac> Saviq: do you have a fix (even if incomplete) that you could use to validate this idea?
[12:32] <asac> e.g. repro, apply fix, unrepro
[12:32] <davmor2> Saviq: this is like 2 seconds
[12:32] <didrocks> Mir is in landing-005, FYI
[12:32] <Saviq> popey, davmor2, can you try while keeping the display on?
[12:32] <didrocks> I don't know what's the status of it, just that everything in it built
[12:33] <popey> ya
[12:33] <Saviq> i.e. instead of sending the text when screen is off, lock it, press power to wake it up
[12:33] <Saviq> send sms then
[12:33] <popey> ok
[12:33] <popey> that seems more reliable (on #250)
[12:34] <popey> however it still happens
[12:34] <popey> that sometimes you tap the notification and nothing happens
[12:34] <popey> even with the phone locked then unlocked, display on
[12:34] <davmor2> oh that is nasty I get no blue envelope in incoming now
[12:34] <bzoltan> didrocks: may i ask a silo for the line 37?
[12:35] <didrocks> bzoltan: mind pinging the whole team? On something else for now
[12:35] <popey> yes, i find this very unreliable on 250
[12:35] <bzoltan> sil2100: Mirv: may i ask a silo for the line 37?
[12:35] <Mirv> bzoltan: sure
[12:35] <Saviq> so that's post-5.2, pre-right-edge
[12:36] <popey> yes
[12:36] <Saviq> but since screen off or on don't matter, that'd be an issue different than event loop
[12:36] <davmor2> need to take wife to hospice to see mil back in a bit
[12:36] <Saviq> but not a regression
[12:36] <popey> +1
[12:36] <Saviq> popey, please file a bug, we'll look into it
[12:36] <popey> in what? unity?
[12:37] <asac> Saviq: can you do a quick assess? this feels important enough to get done for our arbitrary 14.04 milestone
[12:37] <asac> Saviq: e.g. impacts a key use case (messaging not working)
[12:37] <asac> even if its not a regression from last devel promotion, we kind of try to get a beta/stable promotion done here
[12:37] <Saviq> asac, yes, we will, a bug please :)
[12:37] <popey> Saviq: in unity?
[12:37] <Saviq> popey, yeah, u8
[12:37] <popey> kk
[12:37] <asac> Saviq: we will get you a bug, start looking anyhow :_)
[12:37] <asac> davmor2: popey: bug please
[12:37] <Mirv> bzoltan: landing-009 for your cool new staging branch
[12:37] <asac> lol
[12:38] <popey> on the way
[12:39] <bzoltan> Mirv: super :) thanks
[12:39] <didrocks> davmor2: where are you with the dogfooding before you leave? can popey finishes it up if needed?
[12:40] <didrocks> Mirv: sil2100: btw, based on that, please hold off any publication ^
[12:41] <didrocks> until we understand/know
[12:41] <popey> https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1307489
[12:42] <popey> ogra_: should location work again in #294 or are we waiting for something?
[12:42] <didrocks> I guess ogra_ told it should
[12:42] <ogra_> popey, the upstart job should properly fire it up
[12:42] <popey> osmtouch seems to think not
[12:43] <popey> Saviq: sorry, bug 1307489
[12:43] <popey> well the location service is running, but osmtouch never gets a lock
[12:43] <ogra_> didrocks, popey, no idea of the service actually works, i only made sure the upstart job doesnt crash on startup
[12:44] <popey> right.
[12:44] <ogra_> but it didnt change in a while
[12:44] <popey> it used to. i have had a blue blob on my house in that app before
[12:44] <ogra_> why should it not
[12:44] <asac> while people are digging; anyone would be brave and try an OTA update from last stable to this one?
[12:44] <asac> and see if it explodes?
[12:44] <asac> :)
[12:44] <popey> hahaha
[12:44] <popey> no
[12:44] <ogra_> popey, you are aware that getting a GPS fix can take half an hour, right ?
[12:44] <popey> ah true
[12:44] <asac> we wanted to push whatever image we have for 14.04 to the stable channel. i sense someone should see what appens really
[12:44]  * popey puts phone on the window-sill
[12:44] <asac> hehe
[12:44] <ogra_> go gardening
[12:44] <ogra_> keep the phone in pocket :)
[12:44] <popey> heh
[12:44] <asac> yeah
[12:45] <asac> ogra_: mind giving that a try? :)
[12:45] <asac> or are you investigating stuff?
[12:45] <popey> QObject::connect: No such slot core::GeoPositionInfoSource::updateTimeout()
[12:46] <ogra_> i'm waiting for QA signoff on line 36 of the landing sheet ... but its awful waether here, not really fond of gardening atm :P
[12:46] <popey> hmm
[12:46] <ogra_> that doesnt look so good
[12:46] <ogra_> where do you see it ?
[12:46] <asac> ogra_: we wont land anything until we know whats the image
[12:46] <asac> and if we rather need some small fix to land
[12:47] <ogra_> well, we wait for the Qt even fix too, no ?
[12:47] <asac> depends
[12:47] <ogra_> or did you want to do another special exception promotion
[12:47] <asac> is 36 the event fix?
[12:47] <asac> or media-hub?
[12:47] <didrocks> ogra_: read the email
[12:47] <ogra_> with the risk that this could become the release
[12:47] <asac> well,
[12:47] <asac> we can promote if its better than previous devel
[12:47] <ogra_> asac, 36 is drooping an unsupported package
[12:48] <ogra_> we need to get that in before release
[12:48] <asac> however, we want to get a real beta/stable at best
[12:48] <asac> ogra_: why?
[12:48] <asac> ogra_: we dont support touch images anyway
[12:48] <ogra_> (happy to land it later this week, but it needs to land to not keep cgroups-lite supported)
[12:48] <asac> or rather update them from t+1 soon
[12:48] <didrocks> ogra_: on the email, it's telling (as we did multiple times in meeting) that QA will assess if we promote or not with the Qt bug
[12:48] <didrocks> knowing that we already promoted with it
[12:48] <asac> ogra_: if its only on touch we can put it into universe?
[12:48] <didrocks> so I guess "risk that this could become the release" is already in
[12:49] <ogra_> asac, thats nicely said, but i'm sure foundations wouldnt be happy having to keep a package that was supposed to be gone
[12:49] <ogra_> for the next 5 years
[12:49] <ogra_> and it would make lxc on the phone totally unpredictable since nothing will use cgroups-lite officially anymore
[12:50] <ogra_> this landing has been tested for days by many people ... would be a shame to lose that work as well
[12:50] <asac> well, dont argue
[12:50] <asac> we will get to it after problem 1 is solved :)
[12:50] <asac> and look at all the pro and cons
[12:50] <ogra_> and the hack we currently use was only temporary to make the image testing go on while a fix is worked out ... it is not production stuff
[12:50] <asac> depends on many variables i guess
[12:51] <asac> the thing that has potential to uplevel our image the most is the evenloop bug
[12:51] <asac> but probably also biggest risk
[12:51] <ogra_> yes
[12:51] <asac> if that thing looks close, eveyrhting else taht might prevent the promotion of an image with that probably should stand back
[12:51] <asac> if it doesnt we can look at 2nd prio items
[12:51] <asac> like this and media-hub etc.
[12:52] <ogra_> well, its a simple dependency change ... but yeah, i can wait
[12:53] <boiko> hey, how do I request someone from QA to test landing-004?
[12:54] <asac> ogra_: can you try upgrading frrom stable to this image?
[12:54] <asac> i am sure knowning whether its broken is more important than many other things :)
[12:54] <didrocks> boiko: set QA needs sign off to yes
[12:54] <boiko> didrocks: already done
[12:54] <didrocks> boiko: so you should be good, now, you need to wait on QA doing it
[12:54] <didrocks> boiko: they are supposed to process the queue
[12:54] <boiko> didrocks: ok, thanks :)
[12:55] <ogra_> asac, but we already know they expose it both
[12:55] <didrocks> boiko: yw!
[12:55] <ogra_> how would such an upgrade prove anything new
[12:55] <asac> ogra_: sorry. i am talking about installing our image 101
[12:55] <asac> ogra_: 13.10
[12:55] <asac> using it and ten and upgrading straight to latest devel-proposed
[12:55] <asac> to see what happens to stable users if we push that out
[12:56] <ogra_> i can only do that on my test phone ... with the broken touchscreen ...
[12:57] <popey> asac: who would do that?
[12:57] <ogra_> but yeah, no prob installing 13.10 and testing an upgrade
[12:57] <popey> I mean, it's not something we even have UI for do we?
[12:58] <ogra_> nope
[12:58] <ogra_> stable would only go to next stable
[12:58] <ogra_> cant switch channels easily
[12:58] <ogra_> so the "upgrade" wuold essentially end up as a reinstall
[12:59] <ogra_> since you need to force a revision of 0 for switching the channel
[12:59] <asac> popey: how or who?
[12:59] <ogra_> how
[12:59] <ogra_> asac, he is right
[12:59] <asac> popey: we plan to push this build to stable, so someone needs to hack around and force the system to go to the other channel
[12:59] <asac> i guess
[12:59] <ogra_> we dont really have a way to do this
[12:59] <asac> thats the trick
[12:59] <asac>  :)
[12:59] <asac> hmm
[13:00] <asac> not even a config file hack?
[13:00] <asac> who would know?
[13:00] <ogra_> the only way to switch the channel with system-image is to force the revision to 0 ... which does a complete install
[13:00] <popey> right, so you're saying we should support oddball hacks that people do to work around the use case we don't have UI for ?
[13:00] <ogra_> no, he wants to asses what hapens if you upgrade within the stable channel
[13:00] <popey> ah okay.
[13:00] <popey> Good luck with that.
[13:01] <ogra_> but the design wont allow us
[13:01] <ogra_> thats indeed quite a flaw
[13:01] <ogra_> we need a test channel for such things
[13:01] <ogra_> but even that would generate different diffs ...
[13:01] <ogra_> so it wouldnt give you the exact same thing anyway
[13:02] <ogra_> asac, the point is though, that an image older than a month will force a full install anyway
[13:02] <ogra_> or even just 10 days
[13:02] <ogra_> i forgot what the exact time was we provide diffs for
[13:02] <asac> ogra_: right, but we have userdata
[13:02] <asac> that might then make things explode
[13:02] <ogra_> yeah
[13:02] <asac> ogra_: can you run 101
[13:02] <asac> use it
[13:03] <asac> and then use phabelt-flash i guess
[13:03] <asac> to upgreade
[13:03] <ogra_> uuh
[13:03] <asac> if thats equiv
[13:03] <ogra_> you are soo behind
[13:03] <popey> heh
[13:03] <asac> ubuntu-device-flash
[13:03] <ogra_> phablet-flash is dead and buried
[13:03] <asac> i know
[13:03] <ogra_> it smells already
[13:03] <asac> just dont agree that we didnt keep the command line name
[13:03] <asac> so i stick to it :)
[13:04] <ogra_> (and i think i have seen a circle of vultures hear imgbot t recently too)
[13:04] <asac> ogra_: but the point isthe same, use the stable image, change some settings etc. upgrade using our flashing tool
[13:04] <ogra_> err
[13:04] <ogra_> WHAT ?
[13:04] <ogra_> i didnt type that !
[13:04] <asac> really?
[13:04] <ogra_> (and i think i have seen a circle of vultures near it recently too)
[13:04] <ogra_> thats what i typed
[13:05] <ogra_> something expanded "imgbot" in there
[13:05] <asac> heh
[13:05] <ogra_> silly xchat
[13:05] <asac> heartbleed
[13:05] <ogra_> lol
[13:05] <asac> dont worry, everything is owned anyway
[13:05] <ogra_> yeah
[13:05] <ogra_> i'll ask the NSA for the logs
[13:05] <Saviq> didrocks, do you have write access to the silo branches?
[13:06] <didrocks> Saviq: no, it's all from webops now
[13:06] <didrocks> why?
[13:06] <Saviq> didrocks, I'm trying to strip the old lp:unity tags off of lp:unity8 again
[13:06] <ogra_> asac, your test wont really show issues though ... you would have to really use the device for a while with 13.10 to produce data, logs, db content etc  ... like for a week or so ... and then do that upgrade ...
[13:07] <Saviq> didrocks, but that's fine, will strip them after this lands and then make sure that no new landing branches have them
[13:07] <ogra_> usage data of a few munites wont really point out issues
[13:07] <asac> ogra_: so we should give up?
[13:07] <ogra_> *minutes
[13:07] <asac> even trying to catch the most basics
[13:07] <asac> ?
[13:07] <asac> i dont buy that
[13:07] <ogra_> asac, no, but you will only test if the defaults are properly updated
[13:07] <didrocks> Saviq: yeah, better to have that once there is no silo branch around
[13:07] <asac> you could take a pick
[13:07] <asac> do one call
[13:07] <Saviq> didrocks, yup
[13:07] <asac> send a sms
[13:07] <didrocks> Saviq: then, cleanswap everything :p
[13:07] <asac> etc.
[13:07] <asac> ionstall an app
[13:07] <ogra_> you wont see issues with data migration of live data
[13:07] <asac> etc.
[13:07] <asac> eveyrthing you can think about
[13:08] <asac> i think first i would like to know if anything works at all
[13:08] <asac> we can look closer then later
[13:08] <ogra_> well, still, i cant really interact with my test device ...
[13:08] <ogra_> but i can try a plain install and upgrade
[13:08] <didrocks> Saviq: FYI, bumping the priority of the notification issue, would be nice to know the cause before getting further though
[13:08] <ogra_> to see if data migradion of the defaults works
[13:08] <didrocks> Saviq: so that we can have a clear view of what this is about
[13:08] <Saviq> didrocks, we're looking into it
[13:09] <didrocks> thanks!
[13:09]  * ogra_ starts a clean 13.10 install
[13:15] <didrocks> asac: ok, I did promoted -> devel and don't stop any issue on a basic interaction
[13:16] <didrocks> however, it's shocking to see how 250 was faster than latest devel
[13:16] <didrocks> popey mentionned the same
[13:16] <asac> didrocks: wait
[13:16] <asac> didrocks: i was interested in stable -> devel
[13:16] <asac> e.g. our 13.10 image
[13:16] <popey> didrocks:  you noticed too?
[13:16] <didrocks> asac: yeah, and that's what ogra_ is doing
[13:16] <asac> using that to generate settings data
[13:16] <asac> ah cool
[13:17] <asac> sorry, got dragged into something else on server side too
[13:17] <didrocks> I'm doing promoted -> devel in between
[13:17] <didrocks> to ensure we don't have surprises here as well
[13:17] <didrocks> (40+ images in between)
[13:17] <didrocks> popey: yeah
[13:17] <didrocks> popey: you don't notice before your reflash to promoted…
[13:17] <didrocks> but then, it's night and day
[13:17] <popey> right
[13:18] <ogra_> asac, well, i cant really do anything but wipe, install upgrade and see if all services start ... my test device doesnt have a touchscreen
[13:18] <ogra_> didrocks, ^^
[13:19] <asac> thats only minimal assuring indeed
[13:21] <pmcgowan> popey, didrocks can you describe more about what is slower? which interactions
[13:22] <popey> pmcgowan: i can probably do a side by side comparison if I get some time in a bit
[13:22] <pmcgowan> popey, is it the dash mainly?
[13:22] <didrocks> pmcgowan: yeah, dash mainly
[13:22] <didrocks> harder to tell in apps
[13:23] <pmcgowan> ok, I "think" the guys are working on tuning, Saviq might know better
[13:24] <ogra_> webapps are tons faster  between devel and proposed
[13:24] <popey> +1
[13:24] <ogra_> that compensates for the slow dash :P
[13:24] <popey> and actually usable
[13:24] <ogra_> yeah
[13:24] <ogra_> popey,i have 15 new click packages here
[13:25] <ogra_> just to lazy to make up descriptions for all of them in the store yet :)
[13:27] <popey> hah
[13:27] <davmor2> didrocks: got no where really that was like test 5-6
[13:27] <didrocks> davmor2: ok, do you have any ETA when your deep dogfooding will be over?
[13:27] <davmor2> also I think I know how to trigger no indicator at all
[13:27] <ogra_> (and 12 updated clicks too for the new webapps framework)
[13:28] <didrocks> davmor2: not interesting in exploratory testing, just regressions or not :)
[13:28] <davmor2> didrocks: certainly before the meeting however jfunk is late back today
[13:28] <didrocks> hum
[13:28] <didrocks> so no decision promotion before the meeting?
[13:28] <davmor2> didrocks: might be not sure how long jfunk will be
[13:29] <didrocks> asac: I don't know how that will work, I'm afraid about stopping the line for everyday due to: 1. no dogfooding test results, 2. no jfunk around to take the decision on the Qt bug
[13:29] <didrocks> asac: as we clearly have no ETA for 2
[13:29] <didrocks> (not sure again why this decision had to be delayed on getting a promotable image. I argued on that for days…)
[13:30] <popey> ogra_: pro-tip, put the site name into google, it often comes back with a one line description of the site, that's what I used mostly ☻
[13:30] <ogra_> heh
[13:31] <ogra_> well, inside the packages i use a stereotypic "Webapp for foobar.de"
[13:43] <popey> ogra_: if you add detail to that description, when you upload to the store, it pulls that out, so you dont need to re-type it
[13:45] <didrocks> Mirv: do you have the bug handy about the clock flaky test?
[13:45] <t1mp> when arm64 packages are built for landing, is that done on actual arm64 hardware or some virtual machine?
[13:46] <t1mp> we have failures in building only on arm64 https://launchpadlibrarian.net/172791061/buildlog_ubuntu-trusty-arm64.ubuntu-ui-toolkit_0.1.46%2B14.04.20140414-0ubuntu1_FAILEDTOBUILD.txt.gz and I don't know how to reproduce it locally
[13:47] <didrocks> kgunn: hey, do you have any ETA for Mir being released?
[13:47] <ogra_> t1mp, ask infinity or cjwatson
[13:47] <kgunn> didrocks: for 0.1.8 i hope today...
[13:47] <didrocks> kgunn: ah, that would be excellent!
[13:47] <kgunn> didrocks: suffering too many things at one :P
[13:48] <didrocks> kgunn: anything I should worry on?
[13:48] <kgunn> didrocks: but i just need to re-test with the update...no worries, it should be good
[13:48] <didrocks> kgunn: remember that this is one of our last shot
[13:48] <cjwatson> t1mp: actual hardware
[13:48] <kgunn> didrocks: just a heads up, i do need a silo for the potential-fix for Qt5.2
[13:48] <t1mp> cjwatson: which devices are those?
[13:48] <didrocks> kgunn: hum, isn't that in the Mir landing?
[13:49] <t1mp> cjwatson: so I guess there is no way to reproduce it on an intel laptop?
[13:49] <cjwatson> t1mp: <redacted for commercial reasons>
[13:49] <kgunn> didrocks: nope...mir 0.1.8 is primarily a bug fix for the "unity8 crash on exit" that screws with ap testing
[13:50] <didrocks> kgunn: ok, so we can have the Qt 5.2 fixes without any Mir release? Like only an unity-mir fix?
[13:50] <didrocks> kgunn: I would prefer that one in priority then
[13:50] <cjwatson> t1mp: I think dannf should be able to give you an account on a test system
[13:50] <kgunn> didrocks: it just came in as available to test...we need to run it through some paces first
[13:50] <cjwatson> t1mp: there's an emulator available but it's stultifyingly slow
[13:51] <t1mp> zsombi_: ^ for the arm64 bug
[13:51] <didrocks> kgunn: and it's only unity-mir?
[13:52] <zsombi_> ok...
[13:53] <kgunn> didrocks: line 38 in the sheet
[13:54] <asac> Saviq: kgunn: the messaging issue ... can we relate that to the event bug?
[13:55] <kgunn> didrocks: ...and hang on...i think i need one more mp
[13:55] <kgunn> but if you'd like to secure a silo i'd be grateful
[13:55] <didrocks> kgunn: if you rebuild mir-devel on itself, you have an ABI breakage, so you need unity-mir rebuild, right?
[13:55] <kgunn> didrocks: yes...hence one more mp
[13:56] <didrocks> kgunn: I'm puzzled why you don't get that in the other silo as you are using -devel anyway
[13:56] <kgunn> didrocks: b/c that's split greeter...not kosher :)
[13:56] <didrocks> ah
[13:56] <kgunn> we need to keep it seperate
[13:56] <didrocks> so line 14 is with the split greeter
[13:56] <kgunn> didrocks: all is under control :)
[13:57] <didrocks> but you are going to land line 38 first without it
[13:57] <bfiller> elopio: can you or someone else from QA please test line 23 in sheet? It has fix for conference calling
[13:57] <davmor2> popey: add an account to settings→ account either twitter or FB and what happens to the app afterwards
[13:58] <cjwatson> zsombi_,t1mp: if it saves time, I already have such an account - tell me what I need to branch and I can test it
[13:58] <didrocks> kgunn: I thought line 9 was the split greeter?
[13:58] <didrocks> that's what written in the spreadsheet
[13:58] <Chipaca> didrocks: testing done. Now how do I hand it off to QA?
[13:59] <kgunn> didrocks: what's you're exact question ?
[13:59] <didrocks> kgunn: I'm not understanding what you are trying to do with that other silo
[13:59] <sil2100> Chipaca: usually QA will pick it up themselves, but we can ping om26er if he's free right now
[13:59] <didrocks> I thought that the Qt fix was in Mir 0.1.8
[13:59] <didrocks> that's what you told me last week
[13:59] <didrocks> and you couldn't cherry-pick it
[13:59] <Chipaca> sil2100: ta
[13:59] <didrocks> now, I see another request
[13:59] <sil2100> om26er: ping?
[13:59] <Chipaca> om26er: ping, if you're free :)
[13:59] <davmor2> popey: also I seem to be hitting your FB account login issue,  I'm wondering if you can only hit the this is a good client from one address so many times before it blocks maybe
[13:59] <didrocks> which has some -devel to -devel MP
[14:00] <popey> davmor2: its not blocked, its fine
[14:00] <didrocks> so mir 0.1.8 + other stuff I guess
[14:00] <kgunn> bingo
[14:00] <popey> davmor2: its just a notification popup thing that says "okay, you can post from this device" but the renderer doesnt like the html it seems
[14:00] <kgunn> didrocks: remember, devs are in control of their own poo-poo now, right...trust me, its under control...
[14:00] <kgunn> :)
[14:00] <om26er> Chipaca, hey I can test that later, right now I am testing music-hub and later something for ogra_
[14:00] <kgunn> you're welcome to question...but i'm having trouble ignoring irc pings to get it tested :)
[14:01] <Chipaca> om26er: ta
[14:01] <didrocks> kgunn: I'm happy to not ask you the same level of transparence that you (as upstreams) are asking to me
[14:01] <didrocks> but you have to welcome that it sounds fishy to say the least :p
[14:01] <didrocks> just tell me
[14:01] <didrocks> you are going to land that line
[14:01] <didrocks> then
[14:01] <didrocks> without the other one?
[14:02] <kgunn> didrocks: ok, from the top...we have 1 silo with mir0.1.8 fix for "unity8 crash on exit" screws with AP...nothing to do with Qt
[14:02] <didrocks> yeah
[14:02] <didrocks> agreed
[14:02] <kgunn> we have another silo not landing/just test for split greeter
[14:02] <mhr3> sil2100, can i get silo for line #8?
[14:02] <didrocks> right
[14:02] <bfiller> om26er: I have one as well that needs testing :) anyone else from QA who can help here?
[14:03] <sil2100> mhr3: looking, hoh, something old it seems?
[14:03] <mhr3> yea, very old
[14:03] <kgunn> i just added another silo for test of mir-devel which contains the Qt 5.2 render loop/blocking problem...again, just test not for landing
[14:03] <kgunn> (see the comment block)
[14:03] <kgunn> didrocks: does that all make sense now ?
[14:03] <didrocks> kgunn: ok, so you are going to land the 1st one only in the end?
[14:04] <sil2100> mhr3: so, tell me, in case of a revert, if we for instance revert unity-scope-mediascanner - will the new music-app work fine then still?
[14:06] <t1mp> cjwatson: ok, thanks. we're still trying to understand what can cause the failure.
[14:07] <kgunn> didrocks: first one lands first....just a matter of testing (line 14/silo5)
[14:08] <kgunn> didrocks: and that silo is unrelated with the Qt5.2 bug of blocking
[14:08] <didrocks> kgunn: ack, I need the unity-mir MP in to assign it
[14:09] <didrocks> kgunn: I don't think we should land line 14/silo5 without the Qt fix though
[14:09] <didrocks> kgunn: we just have one shot for landing
[14:09] <didrocks> and we told for multiple days that the next Mir is going to fix the Qt issue
[14:09] <didrocks> asac: wdyt? ^
[14:10] <sil2100> mhr3: hmm?
[14:10] <mhr3> sil2100, yea, new music-app is already in the image
[14:10] <mhr3> for a few days actually
[14:11] <asac> kgunn: why would you land something unrelated to our main issues?
[14:11] <asac> kgunn: is it worth it?
[14:11] <asac> whats in there?
[14:11] <didrocks> description says:
[14:11] <didrocks> Mir v0.1.8 + cherry pick bug FIX (for critical but non-block bug) for https://bugs.launchpad.net/mir/+bug/1256360
[14:11] <asac> that sounds like a cherry pick for our event bug?
[14:12] <didrocks> not sure what's in 0.1.8, I assumed there were the Qt bug from multiple days
[14:12] <didrocks> as told in the landing email as well
[14:12] <didrocks> but seems not
[14:12] <asac> dont we have 0.1.8 already>?
[14:12] <didrocks>  mir | 0.1.7+14.04.20140318-0ubuntu1  | trusty | source
[14:12] <didrocks> asac: ^
[14:12] <asac> does it reak abi/api?
[14:12] <asac> can it be backed out?
[14:12] <didrocks> yeah
[14:12] <didrocks> it breaks
[14:12] <asac> ok so not
[14:12] <asac> ok, lets focus on promotion of this one
[14:13] <didrocks> I thought we were…
[14:13] <asac> after that happened let scollect all the stakeholders that have stuff they want to land and ensure that they all discuss amongst each other what to do
[14:15] <sil2100> mhr3: awesome, assigning then
[14:15] <sil2100> Just remember that publishing might take soem time due to many reasons right now
[14:18] <didrocks> cyphermox: Mirv: sil2100: remember: no publication until we know if we can promote or not. And especially, nothing risky
[14:18] <Saviq> asac, not likely - see bug, turning the screen of or not doesn't matter for the behaviour
[14:18] <asac> Saviq: ack
[14:19] <sil2100> didrocks: right! I remember that ;)
[14:20] <didrocks> cyphermox: Mirv: sil2100: going for a run, will be back for the meeting
[14:23] <zsombi_> cjwatson: would you mind to take lp:~zsombi/ubuntu-ui-toolkit/dynamic-tabs-test-failure
[14:25] <sil2100> didrocks: ok, have fun!
[14:31] <cjwatson> zsombi_: looking
[14:39] <zsombi_> cjwatson we had a failure on some tabs tests in tst_tabs.qml
[14:41] <davmor2> popey: can you login to the gmail webapp?
[14:43] <popey> davmor2: yes
[14:44] <davmor2> popey: yes I can now I think I had too many apps open maybe I'll dig into that more after
[14:46] <sergiusens> sil2100: Mirv hello! Can I get a slot for l39?
[14:49] <sil2100> sergiusens: let me take a look
[14:51] <sergiusens> ty
[14:51] <sil2100> sergiusens: assigning!
[14:58] <psivaa> sil2100: didrocks: the dialer app failure is reproducible with and w-o apport. have run many times.
[15:03] <cjwatson> zsombi_: reproduced on am1.  let me know what you'd like me to try
[15:04] <zsombi_> cjwatson: any logs?
[15:05] <sil2100> psivaa: ok, so that's not it then, hmmm
[15:05] <cjwatson> zsombi_: http://paste.ubuntu.com/7250160/
[15:06] <zsombi_> cjwatson: excellent! why arm behaves differently there?
[15:07] <cjwatson> zsombi_: I have no idea
[15:07] <cjwatson> zsombi_: These things usually become clear after debugging rather than before :)
[15:08] <zsombi_> cjwatson: it's not that easy... you cannot really debug it :
[15:08] <cjwatson> (also, this is arm64, not arm, I suggest distinguishing them)
[15:09] <cjwatson> zsombi_: surely somebody can, it seems unlikely that we're shipping critical software that nobody can debug :)
[15:10] <zsombi_> cjwatson it only happens on arm64
[15:10] <cjwatson> zsombi_: hm, this doesn't seem to be quite the same failure as on the buildd
[15:11] <cjwatson> The buildd says "FAIL!  : components::TabsAPI::test_z_insertTab() Uncaught exception: Cannot read property '__protected' of null" which suggests a null dereference somewhere
[15:12] <cjwatson> is there a way to run this one test given a build tree?
[15:13]  * cjwatson finds it
[15:13] <Saviq> popey, didrocks, davmor2, asac: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1307489/comments/3
[15:13] <Saviq> and the previous comment
[15:14] <Saviq> https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1307489/comments/2
[15:16] <zsombi_> cjwatson: it is the same, I've added a null-check in the script and also set a warning print in case the element was null. The problem is that it cannot be null!
[15:16] <cjwatson> ah ok
[15:16] <zsombi_> cjwatson: as the tab instance was already added to the model, and the only thing doen is reindexing. and the item at the given index seems to be null, which cannot ever be
[15:18] <zsombi_> cjwatson: on the other hand, now we have a clear failure there!
[15:22] <om26er_> ogra_, ping, regarding line 36 aka silo 14 seems there is no lander name there? and no one tested it
[15:23] <cjwatson> zsombi_: It seems weird that this is emitting warnings about tabs added by other test functions; doesn't this point to a test isolation problem?
[15:23] <om26er_> sorry discard the "and no one tested it" part
[15:23] <ogra_> om26er_, i, tested it (after popey tested it for a night and stgraber tested it before)
[15:23] <om26er_> ogra_, it does not have the agreed orange color, probably something is missing, I am not sure
[15:23] <seb128> popey, hey, just as fyi, the system settings update from today should have working click updates, if you want to test that again in the next image (or just update the deb manually on your device)
[15:23] <popey> seb128: awesome, will do.
[15:23] <seb128> popey, thanks
[15:24] <ogra_> om26er_, well, then thats my fault, i need to find what switcheds to flick for you to get it orange ... one sec
[15:24] <om26er_> maybe the name of the lander
[15:25] <ogra_> om26er_, yeah, not sure who deleted it, there was definitely my name in originally
[15:26] <ogra_> om26er_, set it again ... did anything change for you ?
[15:26] <om26er_> ogra_, I think it will take a few more minutes, when the auto-didrocks runs
[15:26] <ogra_> ah
[15:26] <om26er_> well I guess I can just go ahead, will save time for both of us ;)
[15:27]  * ogra_ offers some chateaulafite to the auto-didrocks
[15:27] <om26er_> ogra_, so mako or flow or does it not matter ?
[15:27] <ogra_> mako would be preferred
[15:32] <ogra_> sil2100, did i do something wrong ? line 36 doesnt seem to want to turn orange
[15:32] <sil2100> ogra_: let me see
[15:33] <ogra_> oh, i might indeed not have clicked "build" since that was a direct PPA upload
[15:33] <Mirv> didrocks: the clock AP bug #1307458
[15:33] <ogra_> status still says "ready to build"
[15:33] <sil2100> ogra_: yeah ;)
[15:33] <sil2100> ogra_: you're right - you need to press build with 'watch_only'
[15:34] <ogra_> is it worth still doing that after the package has build ?
[15:36] <sil2100> ogra_: yes
[15:36] <ogra_> done then
[15:36] <sil2100> ogra_: it will just check, see the package being built and finish
[15:36] <ogra_> ok
[15:38] <zsombi_> cjwatson: the warning you see there is from the same test. it comes several times as the tabs are added as children to the holder Tabs component, and each child change is redoing the indexes few times...
[15:40] <didrocks> Mirv: thanks!
[15:40] <didrocks> psivaa: thanks!
[15:42] <didrocks> davmor2: so, where are you with the dogfooding?
[15:43] <cjwatson> zsombi_: But e.g. it complains about "Invalid Tab at index 5 Inserted External tab", and the tab by that name is added by an entirely different test (test_z_insertExternalTab rather than test_z_insertTab).  Shouldn't those two different test functions be isolated?
[15:43] <davmor2> didrocks: just finished got delyed due to meeting gonna catch up with jfunk now before the meeting
[15:43] <didrocks> davmor2: no new blockers found?
[15:43] <sil2100> ogra_: hah! You made a typo in the sources list in the landing ;)
[15:43] <sil2100> ogra_: lxc-android-conifg
[15:43] <sil2100> I'll fix that, reconfigure and press the build watch-only button
[15:43] <davmor2> didrocks: https://docs.google.com/a/canonical.com/spreadsheets/d/1mWLpKK18mPU1Z1qJ-rgpSDQ_AbvT6DWVChu42urj6vY/edit#gid=0 looks good to me :)  couple of new bugs but only minor mostly cosmetic
[15:44] <zsombi_> cjwatson: that's what I'm talking about! :) the Tab i sthere, but fo rsome reason it reports that it isn't!
[15:44] <didrocks> davmor2: yeah, I fetch and looked through it
[15:44] <ogra_> sil2100, bah, sigh
[15:44] <ogra_> fixed
[15:44] <zsombi_> cjwatson: we can isolate those only by doing each test with a separate test document
[15:44] <davmor2> didrocks: the blockers are basically the blocker as it stands :)
[15:44] <ogra_> sil2100, can we just consider red another form of very dark orange ?
[15:44] <ogra_> :P
[15:45] <zsombi_> cjwatson: the tests are executed on the same component
[15:45] <didrocks> davmor2: it can have an s, it's there for a long time :p
[15:45] <sil2100> ogra_: can you make sure sergiusens and the MMS guys are aware of rebuilding lxc-android-config ? :)
[15:45] <ogra_> sil2100, that landing got cancelled on friday
[15:46] <zsombi_> cjwatson: what I'm affraid of is that there is a move before the reindex() is called, and that doesn't complete while the reindexing is done...
[15:46] <ogra_> unless sergiusens tries a separate landing now that i'm not aware of
[15:46] <sil2100> ogra_: like, completely cancelled? As the silo is still assigned for them...
[15:47] <ogra_> well parts were split out (like the download manager)
[15:47] <ogra_> better talk to sergio if it is still needed
[15:49] <sil2100> sergiusens: hello! Do you still need the MMS silo 013?
[15:49] <ogra_> yay
[15:49] <ogra_> orange !
[15:49] <sil2100> o/
[15:49] <cjwatson> zsombi_: I would be happy to try inserting instrumentation to see if that's the case, if you give me some suggestions
[15:49] <didrocks> popey: do you think the clock apps guys will be able to look at the flaky clock AP test?
[15:49] <zsombi_> cjwatson: I'll add more logs, will ping you when I'm ready!
[15:50] <om26er_> Chipaca, hey! trying to understand, do we only have 1 test case for push server ?
[15:50] <cjwatson> zsombi_: OK.  If you need to move on urgently then of course it would be possible to XFAIL this on just that one architecture; but IME this sort of thing often acts as a canary for code that fails less reproducibly elsewhere so it's worth at least the effort to understand it
[15:51] <zsombi_> cjwatson: I feel we have again a small timing problem. The move aint seems to complete while we do the reindexing, that's the problem.
[15:51] <Chipaca> om26er_: you mean for push client?
[15:52] <om26er_> Chipaca, sorry, yes its the client
[15:52] <cjwatson> zsombi_: maybe inserting artificial delays would widen the window and make it more reproducible elsewhere
[15:52] <Chipaca> om26er_: for now yes; we're fleshing that out
[15:53] <Chipaca> om26er_: i can show you the spreadhseet with what we're looking at adding
[15:53] <om26er_> Chipaca, so right now only the updates notification are using push ?
[15:53] <om26er_> trying to figure out the impact here
[15:53] <Chipaca> om26er_: yes, only update notifications
[15:54] <Chipaca> om26er_: https://docs.google.com/a/canonical.com/spreadsheets/d/1yq212uXJYT_Xm-s7RZYoKfMU7CSGZ9C87SPIS4NGNwk/edit#gid=0 fwiw
[15:54] <Chipaca> om26er_: (am working with rhuddie on getting those into the right format and etc)
[15:55] <om26er_> Chipaca, cool, that's great
[15:58] <zsombi_> cjwatson: the problem is that introducing delay may be a bit of overkill...
[16:05] <zsombi_> cjwatson: I've updated the branch, pls pull
[16:06] <cjwatson> zsombi_: I obviously don't mean in production, just for testing
[16:06] <cjwatson> zsombi_: no changes, did you push?
[16:06] <zsombi_> cjwatson: ah, sorry :) now it's in
[16:10] <ogra_> damned
[16:10] <ogra_> didrocks, asac, so ggogle kicked me out from the HO telling me "too many people"
[16:14] <cjwatson> zsombi_: that makes it pass ..
[16:14] <zsombi_> cjwatson: aha :D I felt it...
[16:14] <cjwatson> zsombi_: http://paste.ubuntu.com/7250464/
[16:14] <zsombi_> t1mp: we have again timing problems :/
[16:14] <zsombi_> t1mp: ^^
[16:16] <om26er> ogra_, the lxc-config change seems to work fine, rebooted alot, though not sure what else do to try to to break it.
[16:17] <om26er> ogra_, is there a MR ?
[16:17] <ogra_> om26er, thats enough, the change is in the upstart job of the android container, as long as it still comes up on boot we're good
[16:17] <ogra_> no, there is no MR
[16:17] <ogra_> https://launchpadlibrarian.net/172071020/cgmanager.debdiff
[16:18] <ogra_> there is a debdiff (different changelog entry since it was against a different variant of that package)
[16:18] <ogra_> om26er, as long as it still boots all is fine (it didnt the last time we applied the exact same change)
[16:19] <zsombi_> cjwatson: ok, so the model element move completion is the problem here...
[16:20] <om26er> ogra_, great, gave a QA +1 :)
[16:23] <zsombi_> cjwatson: I'll get back to it tomorrow... I'll need someone to help me out with arm64, can anybody else help me out tomorrow starting 8 AM UTC+3?
[16:24]  * ogra_ hugs om26er 
[16:24] <didrocks> ogra_: how much did you pay? :p
[16:24]  * om26er hugs ogra_ back
[16:25] <ogra_> didrocks, just a hug (and a drik of omars choice in malta)
[16:25] <didrocks> ;)
[16:27] <cjwatson> zsombi_: One of the release team in London should be able to help by then (try #ubuntu-release).  I'll be on a train, but I expect I'll be around from a couple of hours after that
[16:39] <t1mp> zsombi_: what do we do about it?
[16:40] <t1mp> zsombi_: how come? the Tab existed before its parent was changed, so only a pointer needs to be updated?
[16:40] <zsombi_> t1mp: dunno... try to add some timeout after the move(tab.__protected.index, tabIndex, 1) and try it again... I'll fade out now, I have no better idea right now
[16:41] <zsombi_> t1mp: not really... the move() places the Tab to a different index, and that means the move will happen few times
[16:42] <t1mp> huh? phablet-click-test-setup is failing for me http://pastebin.ubuntu.com/7250563/
[16:42] <t1mp> the files to download are not found
[16:45] <cjwatson> That looks like some strange unofficial PPA
[16:45] <cjwatson> Quite why it's going for the primary archive I'm not sure, probably just because pull-lp-source isn't smart enough
[16:52] <ogra_> didrocks, so if i understood that correct, i'll land lxc-android-config now (after promoting) and immediately kick an image, right ?
[16:52] <didrocks> ogra_: yep!
[16:52] <ogra_> great
[16:52] <didrocks> thanks ogra_ :)
[16:52] <davmor2> kgunn: just checking you got my message from the hangout that the dialer app is the same
[16:52] <ogra_> do we have enough image bui8ld people around for the other landings that are queued ?
[16:53] <ogra_> so that we dont start getting stuff piled up in the archive
[16:53] <robru> bfiller_afk, in line 40, one of those URLs is a branch, not an MP. please fix and then I can assign it
[16:54] <asac> ogra_: promtoed?
[16:54]  * asac wonders if the trainbot would announce that
[16:54] <robru> kgunn, line 38 got silo 3, please build
[16:54] <Chipaca> om26er: ping
[16:54] <om26er> Chipaca, pong
[16:54] <kgunn> robru: thanks...i
[16:54] <kgunn> am waiting on 1 mp...
[16:54] <robru> kgunn, you're welcome
[16:55] <om26er> Chipaca, I am testing the client, I downgraded to a previous image just now so that it could show me updates notification
[16:55] <ogra_> asac, not automatically ...
[16:55] <Chipaca> om26er: hi there. I don't know if you're looking at push, or needing anything from me?
[16:55] <robru> kgunn, ok no worries, I can reconfigure if needed
[16:55] <ogra_> (promotion scripts are running)
[16:55] <Chipaca> om26er: um... oh dear. No, it doesn't work that way.
[16:55] <robru> ToyKeeper, need QA ack on silos 4, 11, and 12. no rush ;-) thanks
[16:55] <om26er> Chipaca, well If I am already on the latest image how will it tell there is an update ?
[16:56] <Chipaca> om26er: well, somebody tells the server there's something newer :)
[16:56] <Chipaca> om26er: downgrading won't put a message on the server to let you know about anything :)
[16:56] <robru> ogra_, you ready for me to publish silo 14?
[16:57] <ogra_> robru, sure
[16:57] <robru> ogra_, done ;-)
[16:57] <om26er> Chipaca, how do I do that then ?
[16:57] <ogra_> rsalveti, hmm, what about generic_x86 ... should i promote that along ?
[16:57] <rsalveti> ogra_: please
[16:57] <ogra_> (we didnt have it in 250)
[16:57] <ogra_> k
[16:57] <rsalveti> ogra_: so we can have at least one promoted image
[16:57] <Chipaca> om26er: if you're running the client, you can point it at your own server and send yourself a message, or ask us to do so
[16:57] <rsalveti> useful for testing
[16:59] <om26er> Chipaca, can you please send me a message then ?
[16:59] <om26er> I would need to login to UbuntuOne ?
[17:00] <Chipaca> om26er: you don't need to log in to ubuntu one, no
[17:00] <ogra_> rsalveti, argh ...
[17:00] <Chipaca> om26er: the guy with access to send messages is either afk or eod. Argh!
[17:00] <ogra_> generic is completely out of sync wrt versioning
[17:00] <rsalveti> ogra_: generic_x86?
[17:01] <ogra_> rsalveti, yeah
[17:01] <rsalveti> ogra_: it's fine, current image is still broken anyway
[17:01] <ogra_> stgraber, ^^^
[17:01] <rsalveti> we need to get a working one first and then ask stgraber to sync the ids
[17:01] <ogra_> can you bring that in sync ?
[17:02] <stgraber> oh yeah, never got around to doing that...
[17:02] <stgraber> will do it now
[17:02] <om26er> Chipaca, should we wait for tomorrow ? or do you want that in today ?
[17:02] <Chipaca> om26er: let's wait for tomorrow, then
[17:02] <om26er> Chipaca, ok :)
[17:02] <Chipaca> om26er: what time can i find you around?
[17:03] <imgbot> didrocks, asac: ogra told me to tell you guys that image 294 got successfully promoted
[17:03] <ogra_> :P
[17:03] <didrocks> ogra_: ahah! ;)
[17:03] <ogra_> semi automatic :P
[17:03] <didrocks> for how long that feature was there? :p
[17:03] <didrocks> ahah
[17:03] <didrocks> ogra_: \o/
[17:03] <om26er> Chipaca, 09:00 UTC till +12hours
[17:03] <rsalveti> \o/
[17:03] <Chipaca> om26er: perfect, thanks!
[17:04] <didrocks> Chipaca: om26er: think about running unity8 AP tests as part of push client dogfooding
[17:04] <didrocks> Chipaca: om26er: if it's not in the testing plan (for the notification issue we saw)
[17:04] <Chipaca> didrocks: i'll be adding that, yes
[17:04] <didrocks> thanks!
[17:04] <Chipaca> didrocks: with a script that tries to trigger it :)
[17:05] <didrocks> I like the "tries" ;)
[17:05]  * Chipaca used examples from unity-notifications to trigger
[17:05] <Chipaca> :)
[17:05] <om26er> how does push affect unity8 ?
[17:05] <asac> ogra_: nice one!
[17:05] <asac> :)
[17:05] <Chipaca> also, I'll be adding a way to inject stuff
[17:05] <stgraber> ogra_, rsalveti: done
[17:05] <Chipaca> so we don't get stuck like this again
[17:05] <asac> ogra_: rickspencer also might want a priv /msg :)
[17:05] <asac> about promotions
[17:05] <om26er> considering autopilot tests are pretty isolated in themselves
[17:05] <ogra_> stgraber, thanks !
[17:05] <Chipaca> om26er: by not filtering notifications by id
[17:05] <rsalveti> stgraber: thanks!
[17:05] <Chipaca> om26er: <brown paper bag/>
[17:05] <ogra_> asac, hah, i have to figure out how to do that with the bot :)
[17:06] <didrocks> asac: apparently, he already knows
[17:06] <didrocks> from g+ :p
[17:08] <bregma> huzzah, landing-008 has passed its tests and needs someone to hit publish....
[17:08] <robru> ogra_, so lxc-android-config is in UNAPPROVED. Does it ship on desktop? I thought it was part of the phone FFe
[17:08] <om26er> bfiller_afk, I'll be testing the dialer-app silo after a call I have to attend.
[17:10] <ogra_> robru, it should be auto accepted after a moment
[17:10] <robru> ok
[17:10] <cjwatson> it was auto-accepted
[17:10] <cjwatson> 18:01 -queuebot:#ubuntu-release- Unapproved: accepted lxc-android-config [sync] (trusty-proposed) [0.161]
[17:11] <ogra_> ah, cool
[17:11]  * ogra_ didnt watch it 
[17:12]  * didrocks sees for long on the CI Train spreadsheet last devel image == last promoted image
[17:13] <robru> didrocks, yay!
[17:13] <Chipaca> om26er: actually, if you're still there, the guy just came back :)
[17:14] <Chipaca> om26er: (otherwise, tomorrow, no worries)
[17:14] <didrocks> robru: good luck for today! hopes everything will continue to work as for us today!
[17:14] <ogra_> didrocks, well, i could still find the promotion command for 250 in the bash history of the cdimage user
[17:14] <ogra_> once we exceeed that i'll start getting worries about our promotion speed :)
[17:14] <ogra_> *worried
[17:14] <didrocks> ogra_: heh :)
[17:14] <didrocks> ogra_: did you edit the HISTSIZE?
[17:14] <ogra_> lol, no
[17:15] <didrocks> ok, so all good! :)
[17:15] <om26er> Chipaca, I am here though I am in a call, but if he sends a notification i'll note ;)
[17:15] <ogra_> yeah
[17:15] <didrocks> (tbh, I did on my desktop and really… it was a good decision :p)
[17:15] <Chipaca> om26er: note the screen needs to be on and unlocked for you to see it, for now
[17:15] <ogra_> my gnome-terminals have 10000 lines backlog ... usually enough
[17:16] <ogra_> (until the terminal crashes indeed)
[17:16] <didrocks> heh
[17:16] <om26er> Chipaca, its unlocked
[17:16]  * Chipaca crosses his appendages
[17:18] <Chipaca> om26er: you should've received it by now :-/
[17:19] <om26er> Chipaca, no, didn't see, I have had my eyes on the screen
[17:19] <Chipaca> om26er: ok, we need to figure out why not. Whenever you can.
[17:20] <om26er> Chipaca, sure, I will ping
[17:20] <om26er> after the call
[17:20] <Chipaca> sure
[17:23] <kgunn> robru: line14/silo5 ready to land... it needs qa sign off (note: this isn't addressing bug 1292306, but does address bug 1256360)
[17:23] <robru> ToyKeeper, need QA signoff ^
[17:25] <robru> ogra_, your next lxc landing is in silo 6
[17:26] <ogra_> cool, thanks !
[17:26] <robru> you're welcome!
[17:29] <asac> hmm. ... we didnt even talk about https://launchpad.net/bugs/1256360 in the meeting, right?
[17:29] <asac> where is that prioritiy wise compared to the other 3 that needed QA sign off?
[17:31] <asac> i guess lets add this to the list of jfunk to prioritize on his own?
[17:32] <ogra_> asac, well, it produces a .crash file on shutdown of unity8 as i understand ... thats never good ... because apport will kick in to process that file on boot
[17:32] <asac> ogra_: maybe, but why wasn't this brought up?
[17:32] <ogra_> sureöy worth to try to get it fixed
[17:32] <ogra_> no idea
[17:33] <asac> we have multiple things we felt are important :) ... your landing (ready), then 3 that waited for QA; we should ensure that others that wanted to get QA attention are happy with this getting fast pathed
[17:34] <asac> so we have 23, 29, 35 as candidates for QA cycles
[17:34] <asac> now we also have 14 i guess?
[17:49] <imgbot> [17:50] <ogra_> lxc-android-config ^^^
[17:54] <ogra_> ARGH
[17:54] <ogra_> the image build failed !!!
[17:54] <robru> noooooooooooo
[17:54] <robru> revert everything!
[17:54] <ogra_> didrocks, asac ^^^
[17:55] <asac> woot?
[17:55] <ogra_> asac, bah, seems xnox changed the seeds
[17:55] <ogra_> and uploaded a meta change
[17:55] <robru> curses!!
[17:55] <ogra_> (ubuntu-touch is uninstallable atm ... til meta is built i guess)
[17:57] <asac> slangasek: ^^
[17:57] <slangasek> asac: can someone provide a one-line summary of what actually broke?
[17:58] <asac> ogra_: ^^
[17:58] <asac> slangasek: ogra will deal with it; you can get info from him; or he can say we shouldnt care
[17:58] <ogra_> slangasek, http://paste.ubuntu.com/7250907/
[17:59] <ogra_> slangasek, i hit build while the seeds were changed and meta wasnt in the archive yet since i didnt expect any direct uploads for touch
[17:59] <ogra_> (at least not without approval)
[18:00] <ogra_> i assume all will be fine once -meta was built
[18:01] <rsalveti> yeah, I think the problem is just xnox not giving a heads up that he changed the seeds
[18:01] <om26er> bfiller, hey! so it seems ToyKeeper is going to be checking the dialer-app silo later in the day
[18:01] <slangasek> ogra_: ok; so this was just a race, colliding with a normal core-dev upload of something that touches the touch image but doesn't go through landings?
[18:01] <rsalveti> and he's also not in this channel
[18:01] <om26er> Chipaca, Hi! I am here, can we do the testing now ?
[18:01] <slangasek> ETOOMANYCHANNELS
[18:01] <ogra_> rsalveti, well, i seemingly mistook his upload
[18:01] <bfiller> om26er: ok thanks
[18:01] <om26er> Chipaca, well I just saw that message for update manager
[18:02] <slangasek> the ubuntu-meta package is not normally siloed, and the change was not related to the touch images
[18:02] <ogra_> slangasek, right, i was wrong about that
[18:02] <Chipaca> om26er: wow, that took a while
[18:02] <rsalveti> oh, then what is the issue? :-)
[18:02] <ogra_> seems to be some dependency change from a seeded package, not the seed itself
[18:02] <slangasek> ok
[18:02] <ogra_> http://paste.ubuntu.com/7250937/
[18:02] <Chipaca> om26er: were you disconnected from the network or something?
[18:02] <ogra_> thats the issue
[18:03] <ogra_> system-settings perhaps ?
[18:03]  * ogra_ checks what was uploaded
[18:03] <om26er> Chipaca, no, the wifi has been connected all the time and internet was working fine
[18:03] <rsalveti> ogra_: dist-upgrade worked fine here
[18:03] <om26er> Chipaca, try a second notification maybe ?
[18:03] <asac> something trapped in proposed?
[18:03] <Chipaca> om26er: didn't you touch that one?
[18:03] <Chipaca> om26er: i can't send them myself :)
[18:03] <ToyKeeper> boiko: Silo 004 is schedule for testing later today, as soon as I can borrow a third phone to test the multiple-call features.
[18:04] <slangasek> ogra_: right; so given that we're building exclusively in trusty, not in trusty-proposed, this certainly should not have happened...
[18:04] <boiko> ToyKeeper: nice! thanks!
[18:04] <ogra_> slangasek, we build with -updated enabled though
[18:04] <rsalveti> ogra_: hm, after dist-upgrade (got latest lxc-android-config), the device can't boot anymore
[18:04] <slangasek> ogra_: is there any indication in the britney output of the cause?
[18:04] <ogra_> *updates
[18:04] <om26er> Chipaca, yeah, sorry I didn't get the time to tap on it
[18:04] <ogra_> is there anything in it already ?
[18:04] <rsalveti> and I don't have adb =\
[18:04] <slangasek> ogra_: updates a) should be empty right now, b) is also meant to be inconsistent
[18:04] <ogra_> rsalveti, 0.160 needs the corresponding initrd
[18:05] <rsalveti> ogra_: oh, ok
[18:05] <Chipaca> om26er: no worries. But now I'm afraid the guy that can send them by hand is eod
[18:05] <rsalveti> let me rebuild the image
[18:05] <ogra_> slangasek, well, we had planned to use it for touch specific stuff ... pre-SRUing things if needed
[18:05] <ogra_> that was actually worked out with cjwatson
[18:05] <ogra_> but if there is not anything in -updates we dont need to care
[18:05] <rsalveti> ogra_: should we then respin android?
[18:06] <ogra_> rsalveti, that was in your last respin
[18:06] <rsalveti> ogra_: ok, let me wait the build to finish to give it a try, as I though I had the latest here
[18:06] <ogra_> rsalveti, oh, you are not using a proper image, right ?
[18:06] <ogra_> rsalveti, you might need to manually purge cgroups-lite
[18:06] <rsalveti> a custom one based on latest
[18:06] <ogra_> (or cgroup-lite)
[18:06] <ogra_> (i can never remember isf there is an s)
[18:07] <slangasek> ogra_: yes, it's fine to /put/ stuff in -updates, I'm saying I believe it's /currently/ empty and I don't believe -updates is a likely source of the current problem
[18:07] <ogra_> no, it isnt
[18:08]  * ogra_ doesnt get why it complains about "held" packages though 
[18:08] <ogra_> during an image build ...
[18:09] <slangasek> because that's a generic apt message
[18:10] <ogra_> i wish it was more verbose though :(
[18:11] <robru> ToyKeeper, hi, sorry for the amount of silos awaiting you today, let me know if you need any help with anything.
[18:11] <asac> ToyKeeper: check with jfunk... he is the man having the priorities and what to do
[18:11] <ToyKeeper> robru: FWIW, I normally start about this time of day...  didn't see your earlier messages until just now.
[18:11] <asac> ToyKeeper: there is no need to rush things; one by one, in right order; jfunk manages that order
[18:12] <slangasek> ogra_: http://people.canonical.com/~ubuntu-archive/testing/trusty_probs.html points to a problem with ubuntu-sso-client, which /happens/ to also be the package referenced in the ubuntu-meta upload; don't know yet why this is uninstallable, looking
[18:13] <ogra_> slangasek, ah, thanks a lot, yeah, that looks like it
[18:14] <slangasek> ogra_: when you see any sort of installability error in an image build, please check that page first
[18:14] <ogra_> will do
[18:15] <bfiller> robru: can we get a silo for line 40 please?
[18:17] <robru> ToyKeeper, ahhh, i wasn't aware of your starting time, thanks for the heads up
[18:18] <robru> bfiller, just need you to fix that one URL which is a branch (needs to be a merge)
[18:18] <ogra_> asac, so no images until thats fixed i guess ...
[18:18] <bfiller> checking
[18:18] <robru> bfiller, it's the second one listed
[18:18] <slangasek> ogra_, asac: ok, so what happened was ubuntuone-client-data needed promoted to main, it was accidentally double-promoted which causes launchpad to lose its mind and delete instead of promoting (longstanding LP bug, you may be familiar with it).  The package has been recovered, so an image build triggered now should succeed
[18:19] <ogra_> lets try one then :)
[18:20] <ogra_> great how iso.qa.ubuntu.com doesnt catch that the build failed
[18:20] <ogra_> i wonder if it will say (re-building) til we have a new image
[18:20] <bfiller> robru: one sec, got another one
[18:22] <rsalveti> ogra_: yeah, even with latest initrd, still doesn't boot :-(
[18:22] <ogra_> weird
[18:22] <ogra_> did it install cgmanager ?
[18:22] <rsalveti> just did a dist-upgrade, with then installed latest lxc-android-config
[18:22] <asac> slangasek: rock on. thanks
[18:22] <ogra_> well, that should have pulled it in
[18:23] <asac> ogra_: ?
[18:23] <ogra_> asac, build running
[18:23] <asac> kk
[18:23] <asac> ogra_: u think all is fine?
[18:23] <ogra_> (bot should announce soon (i hope))
[18:23] <asac> ogra_: thats for your silo shot, right?
[18:23] <ogra_> asac, we'll see
[18:23] <ogra_> yep
[18:23] <rsalveti> ogra_: will wait next image to see if it'll boot or not :-)
[18:24] <bfiller> robru: all set now
[18:24] <ogra_> rsalveti, well, if you only got lxc-android-config you should check that one :)
[18:24] <rsalveti> will flash latest and do another dist-upgrade to confirm
[18:25] <ogra_> rsalveti, oh, dist-upgrade on a system-image ?
[18:25] <rsalveti> ogra_: yup
[18:25] <ogra_> that wont work indeed
[18:25] <rsalveti> as that was what caused it
[18:25] <rsalveti> ogra_: why?
[18:25] <ogra_> lxc-abdroid-config cant unpack
[18:25] <ogra_> as usual
[18:25] <rsalveti> I did an umount of the udev rule
[18:26] <rsalveti> which allowed me to install it successfully
[18:26] <ogra_> hmm
[18:26] <robru> bfiller, thanks
[18:26] <rsalveti> flashing 294 and will give it another try
[18:26] <ogra_> rsalveti, it might leave the overrides for cgmanager and cgproxy in place
[18:27] <ogra_> they are conffiles, might not be removed on upgrade
[18:27] <robru> bfiller, ok you got silo 14
[18:27] <bfiller> robru: cheers
[18:28] <robru> you're welcome
[18:28] <xnox> ogra_: system-image update makes sure that conf-files are gone...
[18:28] <xnox> ogra_: we are not using dpkg to upgrade.
[18:28] <rsalveti> ogra_: right, that's what I thought
[18:29] <rsalveti> xnox: we know, it's just that I did a dist-upgrade but then couldn't boot anymore
[18:29] <rsalveti> I know it's not supported, was just concerned that there could be a real issue
[18:30] <rsalveti> ogra_: how did we test this change then?
[18:30] <ogra_> xnox, rsalveti does
[18:30] <ogra_> :P
[18:30] <ogra_> rsalveti, http://paste.ubuntu.com/7219206/
[18:30] <rsalveti>  - adb shell rm /mnt/etc/init/cgroup-lite.conf /mnt/etc/init/cgmanager.override /mnt/etc/init/cgproxy.override
[18:30] <rsalveti> right
[18:30] <ogra_> yep
[18:31] <ogra_> so i guess your dist-upgrade left them around
[18:31] <rsalveti> probably
[18:31] <rsalveti> then fine :-)
[18:31] <ogra_> well, kind of
[18:31] <ogra_> i'll add a proper maintainer script snippet for the next time
[18:32] <ogra_> since there are some crazy people using dist-upgrade :P
[18:32] <rsalveti> :-)
[18:32] <ogra_> :)
[18:34] <kgunn> ToyKeeper: om26er ...just double checking 1 of you if giving me some qa love on line 14...
[18:34] <ToyKeeper> kgunn: That's the first on my list.
[18:34] <kgunn> as if i can land it now, it'll make my qt5.2-mir bug easier
[18:34] <kgunn> ToyKeeper: thanks!
[18:34] <kgunn> was just making sure
[18:53] <asac> robru: busy?
[18:53] <asac> :)
[18:53] <asac> trying to find someone who could try reproducing a unity8 crash rick has been seeing on latest image
[18:53] <robru> asac, always! what's up?
[18:53] <asac> https://bugs.launchpad.net/unity8/+bug/1307634
[18:54] <asac> robru: if you are deep into supporting landings dont worry :)
[18:54] <robru> asac, I'm just waiting for an SRU to build actually, so I have some time to test taht
[18:54] <asac> robru: yeah, think old image, pin stuff to launcher
[18:54] <asac> and then see
[18:54] <asac> otherwise ask rick directly
[18:54] <asac> if he has more ideas
[18:54] <asac> or what his state before was
[18:55] <asac> rickspencer3 in #ubuntu-touch :)
[18:55] <ogra_> i doubt iit will cause the unity crash
[18:55] <asac> most likely not
[18:55] <asac> but still
[18:55] <ogra_> i have seen launcher entries not work before when the app underneath was upgraded
[18:55] <ogra_> and i think i would have noticed unity crashing then
[18:56] <robru> asac, do we know how old his original image was?
[18:56] <ogra_> 250 most likely
[18:56] <ogra_> he usually only uses devel
[18:56] <ogra_> not -proposed
[18:56] <asac> robru: he is upgrading all the time afaik
[18:56] <asac> ask him
[18:57] <robru> ahh
[19:00]  * ogra_ sees the -changes ML and sighs
[19:00] <ogra_> that wont be a small changelog for this image
[19:15] <rsalveti> ogra_: nops, my fault, but just rebuilds
[19:15] <rsalveti> it'll be scary still ;-)
[19:16] <ogra_> rsalveti, yeah, i dont mean your stuff ... but lxc ... cgmanager ... lots of low level stuff
[19:16] <rsalveti> right
[19:16] <ogra_> scaring me  ...
[19:16] <rsalveti> :-)
[19:19] <asac> hmm
[19:19] <asac> was "[ubuntu/trusty-proposed] click-update-manager 0.1+14.04.20140306-0ubuntu2 (Accepted)" discused on the call?
[19:21] <ogra_> asac, yes, together with all the other no-change rebuilds rsalveti is doing for GLES on x86
[19:22] <asac> really?
[19:22] <asac> i must have missed that part
[19:22] <ogra_> ricardo mentioned that he is doing that, yes
[19:22] <asac> anyway, /me closes eyes
[19:22] <ogra_> right, nothing to worry about
[19:22] <ogra_> just no-change rebuilds to make x86 pick up the GLES symbols
[19:22] <asac> well, if something happens the price could be pretty high though, so lets cross fingerse
[19:23] <rsalveti> I'm on top of this
[19:24]  * ogra_ crosses fingerse
[19:25] <asac> rsalveti: sure. thanks
[19:29] <bfiller> robru: need a silo for line 42 when you have a moment
[19:32] <rsalveti> asac: ogra_: we also need to remember folks that the stable update will not happen for maguro (not sure about grouper)
[19:32] <ToyKeeper> Right, can't talk to the network when the GUI isn't running.  /me stabs NetworkManager
[19:33] <asac> rsalveti: right. isnt that a matter of remembering that when we promote?
[19:33] <asac> rsalveti: are we currently promoting maguro to devel?
[19:33] <robru> ToyKeeper, how is that a problem? it's not like computers can do anything even slightly useful without a gui ;-)
[19:33] <asac> if so we should stop that now :)
[19:33] <ogra_> asac, rsalveti, grouper is still in the promotion list ... i probably should take it out for the release
[19:33] <asac> yes, kill grouper as well
[19:33] <ogra_> asac, nope, not since 188
[19:33] <rsalveti> right, but we need to do 2 things
[19:34] <rsalveti> one is not promoting them, and the other is remembering as part of release notes
[19:34] <ogra_> yeah, i'll rip out grouper from the next promotion
[19:34] <robru> bfiller, ok, you got silo 18
[19:36] <ToyKeeper> kgunn: Should this just be a 'apt-get dist-upgrade' with silo 005 enabled?
[19:37] <asac> rsalveti: can you remind me of release notes tomorrow again? :)
[19:37] <rsalveti> sure
[19:37]  * asac will try to remember as well
[19:37] <bfiller> robru: thanks
[19:37] <asac> have to talk to didrocks
[19:37] <ogra_> do we actually do an official release and all ?
[19:37] <asac> what is an official release?
[19:37] <asac> if we punt it to stable channel i guess its a release
[19:38] <ogra_> well, our notes added to the official ubuntu notes etc
[19:38] <asac> are we doing that? we dont know yet:)
[19:38] <asac> yeah, i think we will add something
[19:38] <asac> i guess we can't really avoid doing that
[19:38] <asac> nor should we i assume :P
[19:38] <cyphermox> ToyKeeper: actually, you can talk to NM via the nmcli command
[19:39] <ToyKeeper> cyphermox: I've tried that, roughly every year or two since 2006, and have never seen it actually work.
[19:39] <imgbot> [19:39] <imgbot> [19:40] <ogra_> there we go
[19:40] <asac> ToyKeeper: nmcli is dumping info, not setting info afair
[19:40] <asac> ToyKeeper: so nmcli nm; nmcli c; nmcli d
[19:40] <asac> work
[19:40] <ToyKeeper> Getting rid of NM is one of the first things I do on any new install, though I did get it to work somewhat consistently for a few months in 2011.
[19:41] <asac> nmcli d | pastebinit
[19:41] <asac> http://paste.ubuntu.com/7251460/
[19:41] <cyphermox> ToyKeeper: up to you I guess.
[19:45] <asac> ToyKeeper: what are you using? ifupdown?
[19:47] <ToyKeeper> Depends on the box.  ifupdown is nice on systems which physically stay in one place.
[19:47] <ToyKeeper> Wicd has been pretty reliable for portable use.
[19:48] <ToyKeeper> wifiroamd was really nice for a few years, but can be inconvenient when visiting random new access points.
[19:49] <ToyKeeper> Hmm, did this dist-upgrade fail because of the silo I added, or because of the new image landing?
[19:49] <ToyKeeper> dpkg: error processing archive /var/cache/apt/archives/lxc-android-config_0.161_all.deb (--unpack):
[19:49] <ToyKeeper>  unable to make backup link of `./lib/udev/rules.d/70-android.rules' before installing new version: Invalid cross-device link
[19:50] <ogra_> you cant upgrade lxc-android-config
[19:50]  * ToyKeeper tries from the new base image
[19:50] <ogra_> yeah
[19:50] <ogra_> (well, there iis a way from recover to upgrade it, but dpkg wont allow you on a running image by desing)
[19:50] <ogra_> *design
[19:52]  * ogra_ OTAs to 295 too
[19:52] <ogra_> bah !
[19:53] <ogra_> and again ... swiping up in the updater while it downloads makes it vanish
[19:53] <ogra_> :(
[19:55] <popey> can someone confirm bug 1307683
[19:55] <popey> i know jono saw it, dunno if anyone else did
[19:57] <ToyKeeper> Sorry, I break my system so much that I rarely get to OTA update...  usually need a fresh flash to clean up my testing messes.
[19:58]  * ogra_ files bug 1307687
[19:58] <ogra_> ToyKeeper, well, i know that popey and davmor2 regulary do OTA too ... one of them will likely be able to confirm
[20:00] <popey> ooh, i have seen that
[20:00] <popey> also happens if you rotate
[20:01] <ogra_> popey, oh, really ? i often rotate accidentially
[20:01] <ogra_> enver had it during rotation
[20:01] <popey> yeah, i press "install" and then put the phone down, the action of putting it down knocks it to rotate
[20:01] <ogra_> right
[20:02] <ogra_> i wish we had landed the new splash screen :(
[20:02] <ogra_> this first boot after upgrade always takes so long
[20:03] <popey> yeah, especially when you have a truckload of clicks
[20:03] <ogra_> yeah
[20:05] <ToyKeeper> That reminds me...  is there already a bug for "can't disable auto-rotate"?
[20:06] <ToyKeeper> It's really annoying when trying to read while laying down.
[20:06] <ogra_> i think it is a "feature" that you cant
[20:06] <ogra_> at leats i was told so
[20:06] <ogra_> :P
[20:06] <ogra_> (well, that apps cant)
[20:07]  * ogra_ would really like to use an ebook reader on the phone ... but with that policy ... 
[20:10] <rsalveti> ToyKeeper: something that needs to be added as a system config, in system-setting and then change unity8 I believe
[20:10] <rsalveti> shouldn't be that hard, and I agree it's really useful
[20:10] <ogra_> right, first we need working rotation at all :)
[20:10] <rsalveti> right
[20:10] <rsalveti> we're getting there
[20:10] <ogra_> the one we have is actually brooken by design
[20:10] <ToyKeeper> I'd put it in an indicator, or some other easy-to-access place, because I generally want to enable it only once in a while, for short tasks.
[20:11]  * ogra_ likes if it can be handled per app actually 
[20:11] <ogra_> so i dont need to tweak the system default all the time
[20:11] <ToyKeeper> Yeah, lots of Android apps have a setting for it.
[20:15] <ToyKeeper> I think the #1 thing I use my Android phone for is reading books...  and the main use case I've found for a larger tablet is reading comics/manga.  Neither works well yet in Touch.
[20:15]  * ogra_ only has book reading at #2 ... 
[20:15] <ogra_> news is my #1
[20:26] <ToyKeeper> The gallery app can be kludged to work as a manga reader, aside from the auto-rotation issue, if I make a script override the mtime on each individual page image to force correct sorting and grouping.
[20:28] <ToyKeeper> (otherwise, the pages end up in pseudo-random order)
[20:53] <ToyKeeper> kgunn: Still around?  The Mir silo appears to work correctly, but the test plan has some issues...
[20:53] <ToyKeeper> (looks like nobody has actually run its manual test plan in a while)
[21:02]  * ToyKeeper biab, hopefully soon
[21:06] <kgunn> ToyKeeper: if you mean the copy/paste...that regression has been around
[21:06] <kgunn> https://bugs.launchpad.net/webbrowser-app/+bug/1303896
[21:06] <kgunn> i filed a bug a while back
[21:08] <ToyKeeper> kgunn: The test plan specifies ?Install packages from build silo per the Release team's process?, but doesn?t link to any details. ?This would resolve the ?which packages? issue I ran into (a bunch are included which shouldn't be part of manual testing).
[21:08] <ToyKeeper> kgunn: It also specifies ?note: cross check known unity8 bugs for any oddity?, but no one is actually going to go through the entire list of unity8 bugs to manually test them.
[21:09] <ToyKeeper> kgunn: Test plan includes ?Browser copy/paste? test, but the browser's long-press does nothing. ?I suspect nobody has run this test in a while? ?The notes app and message app can fill the role though.
[21:09] <ToyKeeper> kgunn: Outdated test: ?running as phablet user on the device stop unity8? ? ?stop: Unknown job: unity8?
[21:09] <ToyKeeper> kgunn: Manual test plan includes AP tests, but landing proposal does not link to any results.
[21:10] <kgunn> ToyKeeper: there's an edit button on that wiki ;)
[21:10] <ToyKeeper> It looks like nobody has actually done these tests in a while, but it should be up to date and tested before asking QA to sign off.
[21:10] <kgunn> ToyKeeper: i ran all these tests today
[21:11] <kgunn> granted i don't read the sheet verbatim
[21:11] <kgunn> b/c i wrote them
[21:11] <kgunn> ToyKeeper: consider, if i hadnt had these test instructions, the browser copy/paste bug would still be hiding
[21:12] <kgunn> ToyKeeper: updating some of the cruft....
[21:12] <ToyKeeper> Just saying...  as far as I can tell, the silo's code is good...  but the test plan isn't really up to par.
[21:14] <ToyKeeper> I'll approve the silo, but "traincon 0" landing QA is pretty strict about getting all the i's dotted and t's crossed.
[21:15] <ToyKeeper> (and pretty soon we'll be requiring a link to AP test results before approving silos)
[21:17] <ToyKeeper> Anyway, it's signed off, and I'll bbiab...  need something done during business hours.
[21:19] <sergiusens> robru: hey, can you take action on silo 16?
[21:19] <robru> sergiusens, just a sec
[21:19] <sergiusens> ty
[21:19] <kgunn> ToyKeeper: update...take a look and see if they're to your liking
[21:19] <kgunn> https://wiki.ubuntu.com/Process/Merges/TestPlans/Mir
[21:20] <robru> sergiusens, ok, published
[21:20] <robru> cyphermox, need a packaging ack when you get a sec: https://ci-train.ubuntu.com/job/landing-005-2-publish/
[21:20] <sergiusens> ty
[21:20] <robru> yw
[21:20] <robru> ;-)
[21:21] <kgunn> ToyKeeper: ...and thank you
[21:44] <asac> how are things looking?
[21:46] <kgunn> robru: can you hook me up with some package acking on line14/silo5 ?....and then a reconfigure on silo3 ?
[22:05] <robru> kgunn, need a core dev for that, i usually go with cyphermox but he didn't respond to my last ping
[22:15] <robru> kgunn, humm, asked a few more people, no responses yet
[22:16] <cyphermox> gonna review now
[22:16] <kgunn> thanks guys
[22:32] <cyphermox> robru: look okay I guess
[22:32] <robru> cyphermox, thanks
[23:14] <robru> kgunn, got you silo 8
[23:30] <robru> kgunn, small hiccup with silo 5 stuck in UNAPPROVED, but that's cleared up, now the whole silo is happily in -proposed.