[01:05] <fginther> robru, looks like it merged about an hour ago. The build machines are still under load
[01:05] <robru> fginther, ok, thanks
[04:12] <plars>  balloons have you noticed that calendar seems to just fail on maguro for the most part? Not saying that makes any sense, just an observation
[04:13] <plars> balloons: I mean, it does fail on mako too, but not nearly as much. On maguro it's really hard to make it pass though.  maybe something timing sensitive?
[06:43] <didrocks> Mirv: hey, can you try the camera_app AP tests? (as we have those crashers) to see if you can reproduce with latest image
[06:43] <didrocks> and then latest image + camera-app in distro?
[06:43] <didrocks> that will help to have first hints for the meeting
[06:43] <didrocks> (now that you published libunity, thanks again! ;))
[06:48] <Mirv> didrocks: ok, I ran them once today before publishing the new camera-app, but I'll try some complete reflash + rety.
[06:48] <didrocks> Mirv: great, thanks!
[06:50] <vila> didrocks: so, the DNS has been migrated
[06:50] <didrocks> vila: great news! Let's cross fingers now :)
[06:50] <vila> * retoaded announces that he has switched all DHCP services over to the new DNS/DHCP server(s). Networking will need to be restarted on just about everything on the 10.97.2.0/24 network for the system to pick up their new DHCP leases and DNS servers unless you want to wait for the 24 hour DHCP renewal to take care of it.
[06:50] <didrocks> vila: next topic was those autopilot machines for which the nodes are going down randomly
[06:51] <vila> ^ that was yesterday evening
[06:51] <vila> hehe
[06:51] <didrocks> (again today, the nvidia machine)
[06:51] <didrocks> retoaded: I guess I have the next topic (we already discussed that) for you ^
[06:51] <didrocks> something to monitor those machines
[06:51] <didrocks> reboot (electrically) if we can't ssh to them for 10 minutes
[06:51] <didrocks> and restart the jenkins node if down
[06:51] <didrocks> otherwise, rocking on the DHCP! :)
[06:52] <vila> didrocks: http://10.97.2.10:8080/job/webapps-autopilot-next-daily/306/label=quantal/testReport/webapps.tests.test_hud/HudTests/test_webappicon_firefox_/
[06:53] <vila> this is a selenium failure I fixed for sst, the way webapps-tests defines browser launch is way too optimistic, not sure who I should talk to about that
[06:53] <didrocks> rsalveti: great work! you should go to bed now :)
[06:53] <didrocks> vila: I think this is dbarth's team
[06:53] <didrocks> (vvruiz should be the one in charge of those tests AFAIK)
[06:54] <vila> vrruiz_: ping
[06:54] <vrruiz_> vila: pong
[06:54] <vila> vrruiz_:  http://10.97.2.10:8080/job/webapps-autopilot-next-daily/306/label=quantal/testReport/webapps.tests.test_hud/HudTests/test_webappicon_firefox_/
[06:55] <vila> vrruiz_: this is a spurious selenium failure
[06:56]  * vila searches relevant revision in sst
[06:57] <vila> vrruiz_: http://bazaar.launchpad.net/~canonical-isd-qa/selenium-simple-test/trunk/revision/425
[06:58] <vila> vrruiz_: in a nutshell, building a selenium driver can (and will) fail at times, you have to retry
[06:59] <vrruiz_> Hmm
[06:59] <vila> vrruiz_: main point of interest in this huge revision is in src/sst/browsers.py (but src/sst/cases.py is also relevant)
[07:00] <vila> vrruiz_: I realize you can't easily reuse that code but the feature you need is there :-/
[07:00] <vila> vrruiz_: mostly I wanted you to be aware that the failure in the url above won't magically disappear
[07:00] <vrruiz_> vila: One question
[07:00] <vila> until *you* do something about it
[07:00] <vila> sure
[07:01] <vrruiz_> vila: Do you know which Launchpad project/branch is that job using?
[07:02] <vila> vrruiz_: lp:webapps-tests ?
[07:02] <vila> vrruiz_: at least that's where I found the overoptimistic line
[07:03] <vila> vrruiz_: http://bazaar.launchpad.net/~vrruiz/webapps-tests/trunk/view/head:/autopilot/webapps/emulators/browser.py#L18
[07:03] <vila> vrruiz_: i.e. just building a driver without catching the exception and retrying as in src/sst/cases.py roughly (but sst uses a modified driver too)
[07:04] <vrruiz_> Ah, I see
[07:04] <vila> vrruiz_: oh, indeed, the trunk for that is yours ;)
[07:05] <vila> vrruiz_: I didn't dig from there so may be you can just use sst and be done
[07:06] <vrruiz_> Someone should package sst and put it in universe :)
[07:06] <vrruiz_> (or main ;)
[07:06] <vila> vrruiz_: it is packaged but not put in universe (my packaging fu is weak :-/)
[07:06] <vrruiz_> Yeah, elopio told me there is a PPA
[07:07] <vila> https://launchpad.net/~vila/+archive/selenium/
[07:07] <vila> vrruiz_: and (basic) instructions on how to update it in sst: doc/packaging.rst
[07:08] <vila> vrruiz_: and (basic) instructions on how to update it in sst: docs/packaging.rst
[07:09] <vrruiz_> Thanks, I will take a look
[07:09] <vila> vrruiz_: ping the qa team about that maybe, elopio and cgoldberg may want to address that now (I pushed for that but didn't go further than the ppa)
[07:10] <vrruiz_> Yup
[07:20] <didrocks> Mirv: I tried here and I don't have any failure, is it the same for you?
[07:20] <didrocks> (camera-app)
[07:27] <vila> didrocks: http://10.97.2.10:8080/job/gallery-app-saucy-i386-ci/352/console rings a bell ?
[07:27] <didrocks> vila: I would say no more loop device available on the machine
[07:28] <didrocks> which makes pbuilder going crazy and can't unmount others
[07:28] <vila> wow, lucky it rang a bell, would never have suspected a lack of device leading to unmount failing 8-)
[07:29] <didrocks> vila: it's a crazy chain of cause/consequence when I looked at it ;)
[07:29] <vila> didrocks: /var/cache/pbuilder/build also contains stuff as old as March 2013
[07:29] <vila> didrocks: on kinnara that is
[07:29]  * ogra_ doesnt understand the camera-app issues
[07:30] <vila> fginther: can use your help ^
[07:30] <didrocks> ogra_: me neither, I asked Mirv to look at it (be he doesn't seem around)
[07:30] <didrocks> ogra_: I tried locally with image 73, all good
[07:30] <didrocks> (multiple times)
[07:30] <Mirv> didrocks: hi
[07:30] <didrocks> hey Mirv!
[07:30] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/20130930.changes
[07:30] <Mirv> didrocks: yep, no failures, have tried twice with both older and newer camera-app
[07:30] <ogra_> it wasnt updated either
[07:30] <Mirv> fresh -b flashing
[07:31] <didrocks> Mirv: upgrade here, but same :/
[07:31] <fginther> vila, woah
[07:31] <didrocks> ogra_: yeah, nothing that I can spot on
[07:31] <vila> fginther: errk, you're here ! OMG, shouldn't you be sleeping ???
[07:31] <ogra_> hmm, pulse was updated
[07:31] <lool> lots of landed over night  :-)
[07:31] <ogra_> lool, lots of broke over night :(
[07:31] <fginther> vila, yes
[07:31] <didrocks> ogra_: well, we do have that one locally as well…
[07:32] <vila> fginther: http://10.97.2.10:8080/job/gallery-app-saucy-i386-ci/352/console can't we just kill it ? I suspect it will never get out of that loop
[07:32] <vila> fginther: but I'm still hesitant to kill jobs without someone confirming ;)
[07:33] <vila> fginther: http://10.97.2.10:8080/computer/kinnara/ seems healthy otherwise (I've just a couple of other jobs and they progress)
[07:33] <didrocks> ogra_: can you update as well and tell us?
[07:33] <didrocks> ogra_: if we are 3 with all tests passing…
[07:33] <fginther> vila, yes, it's in a bad place, the job will be timed out after two hours, but no reason to wait that long here
[07:34] <vila> fginther: ha great, where can I see that timeout ?
[07:34] <ogra_> didrocks, takes a while, i only have 2MBit here ... gimme 30min
[07:34] <vila> fginther: no, stop, go to bed, I don't want to retain you here ;)
[07:35] <didrocks> ogra_: still 300 MBit here (well, less as I'm connected through wifi to my router, but I won't complain :p)
[07:35] <ogra_> didrocks, there is a .crash file in the tests
[07:35] <ogra_> did you check /var/crash ?
[07:35] <fginther> vila, alight, I go back to sleep now :-)
[07:36] <vila> fginther: job killed, will monitor kinnara a bit, have nice dreams ;)
[07:36] <didrocks> ogra_: yeah, I don't have any crash here
[07:36] <didrocks> ogra_: but let's give that to upstream
[07:36] <didrocks> ogra_: image 74? do you know why?
[07:36] <didrocks> with no packaging changes…
[07:36] <ogra_> why what ?
[07:37] <didrocks> why an image 74?
[07:37] <didrocks> 71, 72, 73 I can understand
[07:37] <ogra_> dunno, i didnt build it
[07:37] <didrocks> but why this 74? (just appeared)
[07:37] <ogra_> lool, yours ? ^^^
[07:37] <didrocks> ogra_: this is not a bug, right? http://people.canonical.com/~ogra/touch-image-stats/20131001.2.changes
[07:37] <didrocks> it's really like, there is nothing…
[07:38] <ogra_> didrocks, yeah, there are only 2h between the two builds
[07:38] <didrocks> ok, /me sed -i s/74/75/ on the spreadsheet
[07:39] <didrocks> annoying we don't know who do builds
[07:39] <didrocks> 2 or 3 for system-image ok
[07:39] <didrocks> but we shouldn't do more :p
[07:39] <ogra_> heh, we should do a lot more imho :)
[07:39]  * ogra_ would like hourly builds 
[07:39] <ogra_> automated ones
[07:40] <didrocks> ogra_: well, it's harder to track, I spend my time updating the spreadsheet with build numbers
[07:40] <didrocks> so if we do that, we need more automation for all the tracking
[07:40] <ogra_> but that would mean that the build *and* the full tests would have to finish in under 1h
[07:40] <ogra_> oh, indeed
[07:40] <ogra_> the spreadsheet doesnt scale
[07:41] <ogra_> the point is, if you could automate all this at such a fine grained manner, you will be ablet to have one image per change automatically
[07:41] <ogra_> that means you will spot any regression immediately and will know exactly where it come from
[07:41] <ogra_> *comes
[07:49] <ogra_> didrocks, i would replace the spreadsheet with an LP form where people put in everything for one changeset to create a ticket and the "lander" has a button called "do testbuild" that runs the whole process of building, publishing, image creation and a full testsuite to show you the results ... if they are good, the system publishes them with one click from you
[07:50] <didrocks> argh, sil2100 won't be able to connect :/
[07:50] <didrocks> ogra_: yeah, we are more or less inline on that
[07:51] <didrocks> having feature landing
[07:51] <didrocks> instead of trunk landing
[07:51] <didrocks> anyway, let's see with what we have ;)
[07:51] <didrocks> Mirv: ok, so as sil2100 isn't around, do you mind taking the Mir request?
[07:52] <didrocks> Mirv: landing #52
[08:04] <lool> nope, I didn't build that image
[08:04] <ogra_> weird
[08:05] <lool> did someone launch in the build in the morning?
[08:05] <ogra_> apparently
[08:05] <lool> Cause Steve L still had one running not too long ago, but he finished testing ~1h ago, however if someone had launched another build, it probably started just while Steve's finished
[08:05] <ogra_> i see rsalveti spun 72
[08:06] <ogra_> oh why did steve run a build ?
[08:06] <lool> Steve did 73 and 74
[08:06] <lool> he wanted to test upgrades with system-image
[08:06] <ogra_> ah
[08:06] <ogra_> well, then we have identified them all
[08:06] <lool> it's what I suggested yesterday evening actually, except it took the whole night to complete landing and testing of this
[08:07] <ogra_> yeah
[08:07] <lool> (this timezone thing is awesome0
[08:07] <ogra_> i went to bed then it FTBFS the first time
[08:07] <ogra_> lool, does it work for you ?
[08:07] <ogra_> didrocks claims it doesnt
[08:07] <ogra_> (i'm still flashing here, maguro sucks)
[08:07] <lool> what doesn't work?
[08:07] <ogra_> TZ selection
[08:07] <lool> haha
[08:08] <ogra_> oh
[08:08] <lool> I just meant that it was great for US folks to be in another TZ to finish the work while we sleep
[08:08] <ogra_> yeah, got it now
[08:08] <lool> but I haven't tested the touch TZ support  :-)
[08:08] <ogra_> to much timezines in my head today
[08:08] <ogra_> *zones
[08:08] <lool> so what do we know about the camera-app crashes?
[08:08] <ogra_> exactly nothing
[08:08] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/20130930.changes
[08:09] <ogra_> thats the change set after which it started
[08:09] <didrocks> lool: I sent an email to olivier, ugo and bill
[08:09] <didrocks> discussing right now on ubuntu-touch
[08:11] <ogra_> didrocks, hmm are you sure we're not seeing an UI issue wrt timezone selection ? i cant even pick it here
[08:11] <ogra_> seb128, ^^^
[08:11] <ogra_> is that supposed to work ?
[08:11] <seb128> ogra_, if you type in the text entry you should get locations
[08:11] <didrocks> I get location
[08:11] <didrocks> I click on one
[08:11] <ogra_> seb128, i do, but tapping a location does nothinng
[08:11] <didrocks> and nothing
[08:11] <Mirv> didrocks: ok, there seems to be a lot to test, maybe sil2100 can then take some of the AP:s if he arrives and I've still tests to run
[08:11] <seb128> didrocks, ogra_: btw, whoever landed that content-hub update without updating setting probably regressed background selection again :/
[08:12] <didrocks> Mirv: right, but this is prio #1 for us, so can you start on those? maybe then sil2100 can pick up when he arrives
[08:12] <didrocks> seb128: it's ken I guess
[08:12] <seb128> didrocks, ogra_: that's likely https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1227520/comments/44
[08:12] <didrocks> seb128: he didn't ask
[08:12] <didrocks> nothing written
[08:12] <didrocks> so please check with him
[08:12] <Mirv> didrocks: yep
[08:12] <seb128> didrocks, no, ken and I agreed yesterday that I would do the organize the landings with you today
[08:12] <didrocks> seb128: someone published the stack without any requests
[08:13] <seb128> didrocks, he said he would land the content-hub commit in trunk and a gallery-app rebuild, but those shouldn't have been uploaded
[08:13] <seb128> didrocks, could be robru?
[08:13] <didrocks> maybe he miscommunicated with robru and he Robert landed it?
[08:13] <seb128> I'm pretty confident Ken didn't do it
[08:13] <seb128> we had a 15 min discussion on how to land settings content-hub and gallery-app synced
[08:14] <didrocks> yeah, but what I told is that he maybe discussed about it with robru
[08:14] <ogra_> seb128, well, i know that apparmor is broken, but is the UI supposed to work ? this zero feedback is weird
[08:14] <didrocks> and Robert misunderstood
[08:14] <seb128> ogra_, it's supposed to show as selected the timezone, try on your desktop
[08:15] <ogra_> heh, my desktop runs precise :)
[08:15] <ogra_> i belive you ;)
[08:17] <seb128> ogra_, https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1232114
[08:17] <seb128> ogra_, that's a bug about the lack of feedback/current behaviour
[08:18] <ogra_> yeah
[08:20] <ogra_> oh, wait !
[08:20] <ogra_> it sets the timezone right
[08:20] <seb128> so?
[08:20]  * ogra_ sees "Europe/Berlin UTC+0"
[08:20] <seb128> haha
[08:20] <seb128> \o/
[08:21] <ogra_> and nothing in any logs :(
[08:21] <seb128> ogra_, it should show Berlin in orange in the list
[08:21] <seb128> in the UI
[08:21] <ogra_> well, i used my hometown
[08:21] <ogra_> not berlin
[08:22] <ogra_> and it shows it highlighted in orange now
[08:22] <seb128> ogra_, it should show as orange all the entries matching your tz
[08:22] <ogra_> that doesnt fix the UTC offset though
[08:22] <ogra_> it does
[08:22] <seb128> ?
[08:22] <seb128> what offset?
[08:22] <ogra_> but my clock is still wrong indeed
[08:22] <ogra_> UTC+0
[08:23] <seb128> was there any time change?
[08:23] <ogra_> unless berlin moved to london recently, thats wrong :)
[08:23] <seb128> we had bugs with clock in the past where the new time would only be picked on refresh
[08:23] <ogra_> no i freshly flashed
[08:23] <seb128> e.g the new minute
[08:23] <ogra_> with a complete re-bootstrapping
[08:23] <seb128> that's not what I meant
[08:24] <ogra_> i flashed freshly, and then went to the timezone selection
[08:24] <seb128> I meant, did you wait a minute, in case the indicator is just too stupid to refresh the time during the minute (where the UI is not supposed to changed)
[08:24] <ogra_> the TZ selector says UTC+0
[08:24] <ogra_> i doubt it will adjust anything
[08:24] <seb128> what does "time" says in adb?
[08:24] <ogra_> root@ubuntu-phablet:/# date
[08:24] <ogra_> Tue Oct  1 08:24:45 UTC 2013
[08:25] <seb128> shrug
[08:25] <ogra_> (assuming you meant date)
[08:25] <seb128> yes
[08:25] <seb128> is /etc/timezone having the right content?
[08:25] <lool> so I'm going to revert to 73 and test an upgrade to 74
[08:25] <Laney> pitti posted a comment in the bug saying there were apparmor problems still
[08:25] <ogra_> root@ubuntu-phablet:/# cat /etc/timezone
[08:25] <ogra_> cat: /etc/timezone: No such file or directory
[08:25] <ogra_> aha
[08:25] <seb128> :-(
[08:25] <seb128> Laney, yeah, I mentioned that before
 didrocks, ogra_: that's likely https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1227520/comments/44
[08:26] <Laney> oh ok
[08:26] <ogra_> root@ubuntu-phablet:/# ls /etc/writable/
[08:26] <ogra_> root@ubuntu-phablet:/#
[08:26] <Laney> doh
[08:26] <ogra_> :(
[08:27] <seb128> let me update here/try
[08:27] <Laney> is it right in the image?
[08:27] <Laney> http://people.canonical.com/~ubuntu-archive/livefs-build-logs/saucy/ubuntu-touch/latest/livecd-20131001.2-armhf.out says good things
[08:28] <ogra_> Laney, it does good things ...
[08:29]  * ogra_ checks livecd-rootfs code
[08:29] <seb128> ok, let's move that to -touch with pitti
[08:29] <seb128> on other news, robru's landing regressed the background selection
[08:29] <seb128> we need to land
[08:29] <seb128> - a rebuild of gallery-arpp
[08:29] <seb128> - one commit to ubuntu-system-settings
[08:30] <seb128> - the new ubuntu-system-settings to saucy then
[08:31] <ogra_> Laney, i suspect the code doesnt cd into the right place when linking and moving
[08:48] <Mirv> psivaa: ok so if you have time to also run mir testing, I tried to do mir testing instructions (comments welcome) at http://pastebin.ubuntu.com/6178812/
[08:48] <Mirv> after, those running the actual tests
[08:48] <psivaa> Mirv: ack, will do
[08:48] <Mirv> ogra_: does that pastebin look correct to you? ^
[08:48] <Mirv> psivaa: thanks!
[08:48] <psivaa> Mirv: yw
[08:49] <ogra_> Mirv, touch .display-mir needs to happen in /home/phablet
[08:50] <ogra_> beyond that, looks ok to me ... make sure to test unity8 last, else the tests behave weird
[08:53] <Mirv> ogra_: thanks
[09:03] <Mirv> psivaa: hmm, first things first, can you check with top if you also get 100% CPU usage of unity8 under mir?
[09:04] <psivaa> Mirv: just doing a fresh flashing, ill check once that's done :)
[09:05] <Mirv> psivaa: yeah, there's quite a log to flash/install/etc. I just noted that myself.
[09:07] <Mirv> hmm now after another reboot it calmed down, weird
[09:09] <Mirv> didrocks: autopilot does not seem to work for me under mir. nothing happens, the autopilot process is there but doesn't do anything.
[09:10] <didrocks> psivaa: same for you? ^
[09:10] <Mirv> I've tried -n unity8, camera_app etc, multiple reboots
[09:10] <ogra_> didrocks, so with 74 i cant get the camera-app to start at all on maguro ... just FYI
[09:10] <psivaa> didrocks: just flashing.. not yet finished :)
[09:10] <didrocks> ogra_: hum, we can on mako here
[09:10] <seb128> so, how do I get a gallery-app update to land?
[09:10] <seb128> that seems to be enough to make the background selection works again
[09:11] <seb128> (it needs to be rebuilt with the new content-hub)
[09:11] <didrocks> Mirv: ok, but there is no regression visible?
[09:11] <ogra_> didrocks, with a fresh --no-backup flash ?
[09:11] <didrocks> Mirv: if you play with it?
[09:11] <didrocks> ogra_: yeah
[09:11] <ogra_> weird
[09:11] <didrocks> ogra_: but on majo
[09:11] <didrocks> mako*
[09:11] <ogra_> right
[09:11] <didrocks> same for lool
[09:11] <didrocks> ogra_: can you try again (after waiting the session to start, like 1 min)
[09:12] <ogra_> yeah, let me reboot
[09:12] <didrocks> it seems to be linked to usermetrics
[09:12] <didrocks> seb128:  you need to check with bfiller, he told me to not release apps without his green flag
[09:13] <didrocks> seb128: and I see no landing ask from him on this
[09:13] <didrocks> (it seems they don't have an always releasable trunk)
[09:13] <seb128> didrocks, what about doing a direct "no change rebuild" of gallery-app to saucy?
[09:13] <didrocks> seb128: once you get his ack, I'll get that in priority
[09:13] <didrocks> seb128: fine with me if that's really enough and you backport the changelog upstream
[09:13] <ogra_> didrocks, nope ... reboot and 1min wait before doing anything didnt change it
[09:13] <didrocks> urgh
[09:13] <seb128> didrocks, let me double check, I get the gallery-app from the daily-ppa, but ken told me a rebuild was the key there
[09:14] <ogra_> i get a white screen
[09:14] <ogra_> thats all
[09:14] <seb128> didrocks, coming back to you about that in a bit
[09:14] <didrocks> ogra_: let me reflash
[09:14] <didrocks> seb128: thanks!
[09:14] <seb128> didrocks, yw ;-)
[09:15] <Mirv> didrocks: I don't have a reference to compare, but it seems to work, yeah. no flickering for example.
[09:16] <didrocks> Mirv: let's wait for psivaa's result, and please email with those results kgunn
[09:16] <Mirv> didrocks: but I'm seeing this 100% CPU usage of the unity8 process (not always, but for example on this boot)
[09:16] <didrocks> yeah, when the screen is blank
[09:16] <didrocks> this is a known thing
[09:16] <Mirv> ok
[09:17] <didrocks> expected to still exist
[09:17] <Mirv> didrocks: also otherwise
[09:17] <Mirv> image visible, idling on eg Applications screen, 100% CPU
[09:17] <didrocks> interesting
[09:17] <didrocks> Mirv: can you detail those in the email?
[09:17] <didrocks> (please CC me and olli)
[09:18] <Mirv> didrocks: ok. after psivaa has some additions to the report.
[09:18] <didrocks> yep
[09:19] <ogra_> tested with Mir, doesnt work either
[09:19] <ogra_> (though i get a black screen now ... )
[09:19] <didrocks> ogra_: AP or camera app?
[09:19] <ogra_> the app
[09:19] <ogra_> i wanted to check wallpaper settings
[09:19] <ogra_> not even the cam
[09:19] <ogra_> :)
[09:20] <didrocks> ahah
[09:24] <seb128> ogra_, wallpaper settings are not working again (thanks to robru's landing of content-hub)
[09:24] <ogra_> seb128, yeah, i wanted to verifyx that ... but am not able to take a picture :)
[09:25] <seb128> ogra_, just copy stuff to ~/Images over mtp
[09:25] <seb128> that's what I do
[09:25] <seb128> ups
[09:25] <ogra_> well, i usually take a closeup pic of something :)
[09:25] <seb128> ~/Pictures I mean
[09:26] <ogra_> that way you test both, camera and wallpaper settings at the same time :)
[09:26] <seb128> right
[09:27] <ogra_> and its funny trying to find structures to make nice wallpapers from
[09:27] <vila> ogra_: verifyx, nice one, you fix stuff as you verify it works, you just rock ;)
[09:27] <ogra_> :D
[09:39] <psivaa> Mirv: 1. i do not get 100% CPU for unity8 under Mir on maguro
[09:39] <psivaa> Mirv: 2. unity8 AP test does not pregress.. like you said above
[09:40] <psivaa> Mirv: the screen was blank when that happened and there was no response to the power button press
[09:51] <psivaa> Mirv: the same thing even after rebooting (removing the battery etc) for other AP tests
[09:51] <psivaa> didrocks: Mirv: i see _usr_lib_arm-linux-gnueabihf_hud_hud-service.32011.crash and _usr_bin_maliit-server.32011.crash on reboots
[09:52] <didrocks> psivaa: ok, anyway, as long as we don't have AP tests running
[09:52] <didrocks> let's not go further
[09:52] <didrocks> we can publish Mir, it's not enabled by default
[09:52] <didrocks> Mirv: mind doing (that + email?)
[09:53] <psivaa> didrocks: ack
[09:53] <didrocks> psivaa: sounds reasonable to you?
[09:53] <didrocks> ok ;)
[09:55] <ogra_> didrocks, the mediaplayer breakage was expected btw (just seeing your mail)
[09:56] <ogra_> didrocks, the tests were supposed to be off though
[09:56] <psivaa> didrocks: Mirv: just to make sure, i disabled Mir (by deleting .display-mir) and then run AP tests and that's working fine
[09:57] <didrocks> ogra_: no, it's another issue
[09:57] <didrocks> ogra_: like the app can't start
[09:57] <ogra_> oh
[09:57] <didrocks> (see, crashing in setup())
[09:58] <didrocks> ogra_: normally, just 2 tests are disabled
[09:58] <didrocks> not all :)
[09:58] <didrocks> psivaa: \o/
[09:58] <didrocks> psivaa: thanks for confirming
[09:58] <ogra_> well, everything that uses the scene selector and thumbnails afaik
[09:58] <didrocks> psivaa: can you install Mir on your desktop and reboot as well?
[09:58] <didrocks> psivaa: so that we are all sured
[09:58] <didrocks> ogra_: right, so 2 ;)
[09:58] <didrocks> ogra_: but it's crashing in setup(), when trying to launch the app
[09:58] <psivaa> didrocks: ack, will do
[09:58] <didrocks> I bet it's the same issue than camera-app
[09:58] <didrocks> psivaa: thanks!
[09:59] <psivaa> didrocks: yw
[10:02] <seb128> didrocks, https://launchpad.net/ubuntu/+source/gallery-app/0.0.67+13.10.20130924.1-0ubuntu2 and https://code.launchpad.net/~seb128/gallery-app/backport-saucy-upload/+merge/188539
[10:02] <didrocks> seb128: rocking!
[10:03] <seb128> ;-)
[10:04] <seb128> ogra_, ^ that should give us back working background selector
[10:04] <ogra_> awesome !
[10:04] <ogra_> now if i could take a pic to use as background that would be even more awesome *g*
[10:05] <Laney> use one of the lovely stock wallpapers we ship
[10:06] <Mirv> psivaa: ok, thanks for the report and the fact that you have maguro, maybe the 100% CPU happens only on mako
[10:06] <seb128> Laney, can't do that, the picker only picks from the gallery ... we should probably add those to the gallery by default though
[10:06] <Laney> if you copy them then they appear in the gallery
[10:06] <psivaa> Mirv: yea possibly
[10:06] <seb128> right
[10:06] <seb128> but it would be nice to have some content in the gallery by default ;-)
[10:07] <Laney> yes
[10:07] <Laney> I don't think the wallpapers are even installed yet though
[10:07] <Mirv> didrocks: doh, the new tick just started, I'm uncertain whether cancelling is ok when prepare job is already running?
[10:07] <Mirv> it won't pick up any new changes though, as there are none
[10:08] <Mirv> seb128: I agree, like on desktop the wallpapers package
[10:09] <didrocks> Mirv: is it wait on stack?
[10:09] <Mirv> didrocks: no the mir is the first one to build so it's doing that
[10:09] <didrocks> ah ok
[10:09] <didrocks> Mirv: if there is no new content, just install it on your desktop quickly and ensuring it's booting
[10:09] <didrocks> no need for further changes
[10:09] <Mirv> but it's just a rebuild so I guess I can wait a bit and then publish the rebuild
[10:09] <Mirv> didrocks: ok
[10:10] <Mirv> didrocks: with publishing mir do you mean just mir or also unity-system-compositor, or also unity-mir from unity8 stack?
[10:10] <didrocks> Mirv: there is no ABI break, right?
[10:11] <Mirv> didrocks: no
[10:11] <didrocks> so mir + unity-mir (the 2 you tested, right?)
[10:12] <Mirv> didrocks: right, that's what I thought, the ones tested exactly and nothing else
[10:12] <didrocks> perfect then
[10:12] <didrocks> no need for u-s-c
[10:12] <Mirv> just checking since I haven't done that many mir releases
[10:12] <didrocks> yeah ;)
[10:25] <didrocks> Mirv: did you send an email/point me to a bug for Mir not working with AP tests?
[10:27] <psivaa> didrocks: Mirv: so on desktop, just installed Mir (did not manually enable though) and it works fine
[10:27] <didrocks> phew!
[10:28] <didrocks> thanks psivaa ;)
[10:28] <Mirv> didrocks: writing ATM
[10:28] <Mirv> didrocks: do you want a bug filed?
[10:28] <didrocks> Mirv: probably yeah
[10:28] <didrocks> with the version of the packages that were tested
[10:28] <Mirv> psivaa: thanks! I also upgraded, but I'm now waiting for the rebuild to finish.
[10:28] <psivaa> Mirv: ack
[10:35] <didrocks> Mirv: great email
[10:35] <Mirv> didrocks: thanks
[11:02] <Mirv> didrocks: hrm, the i386 build seems quite stuck https://launchpad.net/~ubuntu-unity/+archive/daily-build/+build/5065483
[11:03] <didrocks> Mirv: maybe kill it and relaunch the build right away?
[11:03]  * didrocks tries
[11:03] <didrocks> Mirv: ok, retried
[11:04] <didrocks> Mirv: if you are faster than cu2d to notice it, there is no need to do anything then ;)
[11:04] <Mirv> didrocks: ok, thanks.
[11:04] <didrocks> let's cross fingers
[11:06] <Mirv> cool, cu2d refreshed, it didn't notice anything ("still building")
[11:06] <didrocks> heh ;)
[11:28] <didrocks> Mirv: successfully built!
[11:29] <Mirv> didrocks: yes, just publishing
[11:31] <Mirv> didrocks: unity-mir would tell about packaging changes if the publish job would be at that state, can you ack debian/control at http://bazaar.launchpad.net/~mir-team/unity-mir/trunk/revision/94?
[11:31] <didrocks> Mirv: sounds good
[11:34] <Mirv> didrocks: for future runs https://code.launchpad.net/~timo-jyrinki/cupstream2distro-config/libunity-mir1_depends_on_libupstart-app-launch1/+merge/188560
[11:34] <didrocks> Mirv: approved
[11:37] <Mirv> and deployed, and both mir + unity8 published before that
[11:41] <didrocks> sweet
[11:42]  * didrocks goes for some exercise now
[12:56] <fginther> morning
[13:51] <didrocks> Mirv: still around?
[14:10] <plars> bfiller: I saw some keyboard stuff landed again, but the autopilot tests still don't seem to work. Are those pieces going to go back in at some point?
[14:13] <bfiller> plars: they are back in
[14:13] <bfiller> plars: what failures are you getting?
[14:15] <plars> bfiller: dbus introspection problems it seems, I am stoping maliit-server and restarting with 'sudo -iu phablet bash -ic "initctl set-env QT_TESTABILITY=1 && start maliit-server"'
[14:15] <plars> bfiller: one sec, will pastebin
[14:15] <plars> http://paste.ubuntu.com/6179730/
[14:15] <sergiusens> doanac, plars how did I install utah again?
[14:16] <plars> sergiusens: on your host system I hope?
[14:16] <sergiusens> plars, yeah, doanac gave me something to test and complains about missing utah
[14:16] <plars> sergiusens: ppa:utah/stable - then install utah and utah-client
[14:19] <sergiusens> ty
[14:37] <fginther> bfiller, anything looking better today? Looks like gallery-app is still hitting one or two failures per MP
[14:38] <ogra_> fginther, ignore image 71-74
[14:38] <ogra_> they all have broken filesystem setups
[14:39] <fginther> ogra_, ack
[15:02] <plars> ogra_: could that have something to do with the other odd failures we started seeing like camera and url-dispatcher crashes?
[15:02] <ogra_> yes
[15:02] <ogra_> it is causing them
[15:06] <lool> plars: pretty likel
[15:06] <lool> likely
[15:07] <fginther> ogra_, should I just roll back to saucy channel for now?
[15:07] <ogra_> yeah
[15:07] <fginther> ogra_, thanks
[15:07] <ogra_> or wait for next image
[15:08] <fginther> ogra_, if these are causing odd failures, I'd prefer to roll back instead of waiting
[15:16] <bfiller> fginther: things looking a lot better today. thank you for all of your help. I'll keep you posted if there are specific MR's that we want to selectively re-trigger
[15:17] <bfiller> plars: looked at your pastebin. you have to start maliit-server with "maliit-server -testability" - looks like this iniitctrl command doesn't set it correctly
[15:18] <thostr_> do we already have an image 75?
[15:18] <bfiller> plars: veebers should be able to tell you about using initctrl and whether that is expected to work or not
[15:19] <lool> thostr_: no
[15:27] <plars> bfiller: ok, when I checked before I thought we decided that it was correct, but I don't think it was veebers I talked to
[15:28] <plars> bfiller: I'll try to sync up with him when his daytime rolls around
[15:28] <bfiller> plars: I've only ever tried it with the -testability flag and it works with that
[15:28] <plars> bfiller: you just launched it by hand, without upstart?
[15:29] <bfiller> plars: correct
[15:29] <bfiller> plars: or I guess you can modify the upstart job to add the -testability flag to the exec
[15:29] <bfiller> that should work as well for testing
[15:29] <plars> bfiller: heh, it doesn't seem to like that at all
[15:30] <plars> bfiller: http://paste.ubuntu.com/6180010/
[15:34] <bfiller> plars: I see that too but that makes it work
[15:34] <bfiller> weird
[15:36] <plars> strange, I'll give it a try though
[15:38] <Mirv> didrocks: starting to be, for the weekly. I guess mir was resolved, it was stuck in unapproved queue?
[15:39] <didrocks> Mirv: yeah, it's done now!
[15:49] <fginther> didrocks, https://code.launchpad.net/~ken-vandine/ubuntu-system-settings/revert_reverted/+merge/188371 building now (about 50% done)
[15:50] <sil2100> Oh my
[15:50] <sergiusens> doanac, lets discuss after image updates
[15:50] <doanac> sergiusens: k
[15:51] <didrocks> great ;)
[15:54] <Mirv> sil2100: you has internet? :)
[15:55] <sil2100> Mirv: yes!
[15:55] <sil2100> Mirv: although I seem to be having lags
[15:58] <psivaa> plars: balloons: dpm_ : regarding the calendar app test failures on maguro.. i see "x_pad = 0.15" is a little thin for maguro in test_monthview.py
[15:59] <psivaa> i experimented it with x_pad = 0.35 and the appear to fix the failures..
[15:59] <balloons> psivaa, ohh excellent. thank you
[15:59] <plars> psivaa: awesome!
[16:00] <plars> psivaa: did you propose a merge for it?
[16:00] <psivaa> balloons: plars: not yet, i could do it rightaway
[16:00] <didrocks> Mirv: sil2100: https://plus.google.com/hangouts/_/e4e5ae9e0927194b088489edf431527da8f0e4bd
[16:00] <balloons> psivaa, go for it.. I assume it doesn't break mako
[16:00] <balloons> but I will check ofc
[16:01] <plars> psivaa: do you happen to know if it... right mako, was just going to ask but baloons beat me to it :)
[16:01] <psivaa> balloons: plars: i have not tested with mako though.. i dont have one
[16:02] <didrocks> ogra_: coming as well?
[16:02] <didrocks> robru: ^
[16:13] <lool> thostr_: upstart-app-launch >> I see this is all in trunk now, but will it work without Mir?
[16:13] <lool> thostr_: I think this is unity-mir API?
[16:15] <thostr_> lool: it's supposed to, otherwise we have a problem
[16:15] <thostr_> lool: let me recheck
[16:15] <cjwatson> I've certainly used it in the past without mir
[16:15] <cjwatson> Maybe it doesn't do all the things it will with mir
[16:18] <thostr_> lool: yes, latest upstart-app-launch should be fine
[16:18] <thostr_> yes, it doesn't do everything without mir
[16:25] <psivaa> plars: balloons: https://code.launchpad.net/~psivaa/ubuntu-calendar-app/fix-maguro-smoke/+merge/188646 is the MP :)
[16:26] <lool> thostr_: it shouldn't regress on SF though, IIUC; will test this tomorrow morning so that we can land it just after tonight's image is confirmed good
[16:26] <lool> (tonight's image isn't built yet)
[16:28] <thostr_> lool: ok
[16:48] <elopio> ping didrocks. So, image 75 will be out today or tomorrow?
[16:48] <didrocks> elopio: tomorrow (for promotion)
[16:49] <didrocks> elopio: it will start building in then next 3 hours
[16:49] <elopio> great. Thanks.
[16:49] <didrocks> yw ;)
[16:50] <ogra_> *twiddle*
[16:52]  * ogra_ waits for an android to come out of britney ...
[16:52] <ogra_> *twiddle*
[16:56] <didrocks> ;)
[16:56] <didrocks>  I want to see a blinking ogra_
[16:57] <ogra_> sorry, <blink> tag not supported
[16:57] <ogra_> :)
[16:59] <didrocks> ;)
[17:13] <robru> ogra_, so what is the deal with the image upgrades? phablet-flash can only find image 70 and then if i try to update from system settings, it can't find any updates.
[17:29] <fginther> Any CI team member want to help review: https://code.launchpad.net/~fginther/pbuilderjenkins/retry-apt-and-bzr/+merge/188664
[17:29] <fginther> vila, ^?
[17:31] <ogra_> robru, are you on the right channel ? we didnt release anything after 70, sounds liek you use stable
[17:38] <josepht> fginther: reviewed
[17:39] <fginther> josepht, clever
[17:39]  * fginther wishes he was clever
[17:52] <ogra_> image build running
[18:26] <ogra_> build 75 done
[18:34] <plars> ogra_ bot? :)
[18:34] <ogra_> heh
[18:34] <ogra_> no
[18:34] <ogra_> :)
[18:47] <fginther> plars, you still have the job for doing an image test with mir, right?
[18:50] <plars> fginther: there's no job, because it never worked. I'm talking to olli about it now. The change to make it work is supposed to land today, and I'll retry then
[18:51] <fginther> plars, ah, thanks. I had thought your results were from the job already, didn't think about just doing it manually.
[18:52] <fginther> plars, doanac, is there anything available for diffing the results of two image tests? (just curious before someone builds a new one)
[18:53] <plars> fginther: not at the moment
[18:53] <doanac> fginther: sorry. we really need to carve out time for that in the next cycle
[18:54] <fginther> plars, doanac thanks
[19:08] <vila> fginther: approved, nice and simple ! Cool
[19:09] <thomi> fginther: is CI/AL set up for lp:python-ubuntu-platform-api? If not, are you able to configure that for me pleae?
[19:09] <thomi> *please
[19:10] <fginther> thomi, looks like it's already there
[19:10] <thomi> fginther: awesome,t hanks
[19:10] <fginther> vila, thanks
[19:15] <lool> ogra_: updated the landing pipeline for newimage
[19:16] <lool> robru: this is what you'd expect on the "stable" channel; the devel-proposed channel would have image 75
[19:20] <lool> Added landing slot for music-app powerd lock
[19:34] <pmcgowan> lool, any chance we can land the toolkit? want to use the url handler in apps
[19:37] <ogra_> lool, thanks
[19:38] <sil2100> ogra_: is 75 released?
[19:38] <ogra_> sil2100, no, but build
[19:39] <ogra_> omg, gallery-app looks really bad
[19:39] <sil2100> Oh, so there were some problems?
[19:39] <ogra_> sil2100, beyond the ones durign the day ? no
[19:40] <ogra_> there were no plans to release 75 today, thats planned for tomorrow
[19:41] <sil2100> I thought 76 was for tomorrow, but I might have missed something
[19:41] <sil2100> Ok, thanks!
[19:41] <robru> ogra_, lool: ok, thanks guys. trying again
[19:42] <ogra_> sil2100, 75 is just for getting back to a good state
[19:43] <ogra_> plars, mako doesnt really look so well on the dashboard
[19:43] <plars> ogra_: checking
[19:43] <ogra_> maguro looks really good
[19:43] <lool> popey_: you around tonight?
[19:44] <lool> popey_: assuming 75 does well in testing, would you be good to release it?
[19:44] <ogra_> (for the state the tests are at)
[19:44] <plars> ogra_: both mako and maguro failed on mediaplayer it seems, mako failed on gallery too for some reason, let me check it out
[19:44] <ogra_> plars, mauro only had one fail on mediaplayer ... for mako nearly everythign failed
[19:44] <ogra_> *maguro
[19:45]  * ogra_ vanishes back into the night 
[19:45] <plars> ogra_: doesn't appear to be universal though, webbrowser passed
[19:45] <ogra_> yeah
[19:45] <plars> ogra_: I'll keep an eye on it, don't worry
[19:45] <ogra_> thx
[19:45] <ogra_> i'll driop by later again
[19:46] <popey_> lool: i can't
[19:46] <popey_> ooh
[19:47] <popey> ogra_: mako looks good too. only one unity crash
[19:48] <lool> popey: you can't?
[19:49] <popey> lool: well, I have no knowledge of the process, and probably no access to the systems
[19:49] <lool> the URL thing, is this the DBus interface to tell a running app about an URL to load?
[19:49] <lool> pmcgowan: ^
[19:49] <lool> pmcgowan: I've added it to plan in any case, but would like to know whether it relates to the "tell running app to load another URL" thing
[19:49] <lool> popey: Oh sorry, I was asking for your approval, not for you to press the button
[19:49] <lool> popey: my bad, wasn't clear
[19:50] <popey> ah okay, that makes more sense
[19:50] <popey> but yeah, 75 is good here
[19:50] <pmcgowan> lool, yes it has the API for that
[19:50] <pmcgowan> lool, did the qtubuntu change get in already?
[19:51] <lool> pmcgowan: no, no qtubuntu update for 8 days or so
[19:51] <lool> in trunk
[19:51] <lool> pmcgowan: I don't know who's on the qtubuntu side in fact
[19:51] <lool> I've lost track  :-)
[19:51] <lool> pmcgowan: is this loicm?
[19:52] <lool> Gerry is on the unity-mir side
[19:52] <lool> but it's not complete
[19:54] <vila> lool: doh ! just realized loicm is not another nick for you but another Loic ;-D
[20:02] <pmcgowan> lool, I thought he finished the qtubuntu stuff some days ago, unless I am confusing it with something else
[20:08]  * thomi hugs doanac for his termsize script :)
[20:09] <doanac> thomi: gotta get your money's worth out of that giant screen!
[20:09] <thomi> hell yes
[20:09] <pmcgowan> lool, this was merged over a week ago so it must already been in https://code.launchpad.net/~aacid/qtubuntu/qtubunturl/+merge/181752
[20:10] <thomi> doanac: am I missing something ? I seem to get 100% failures on all autopilot tests, with all AP packages from the image
[20:10] <thomi> is there some step I'm forgetting? I ran phablet-click-test-setup, and then phablet-test-run
[20:10] <doanac> thomi: are you try click packages or just normal apps?
[20:11] <thomi> doanac: I'm trying everything in ~/autopilot
[20:11] <thomi> like, unity8 for example
[20:12] <doanac> thomi: hmm. unity8 worked fine for me (although it was broke). maybe you need to run the aa-click-hook to enable dbus probing?
[20:12] <doanac> i don't think that's your issue, but might help
[20:12] <thomi> doanac: ok, thanks - just wanted to make sure I wasn't missing something
[20:19] <sil2100> lool: hm, I just switched to ubuntu-system - how can I make things read/writable? .writable-image doesn't seem to work
[20:23] <sil2100> popey: ^? ;)
[20:23] <sil2100> I'm used to using cdimage-touch
[20:25] <robru> sil2100, it's .writable_image
[20:25] <sil2100> robru: then the wiki needs updating
[20:25] <robru> sil2100, yeah, I noticed that too...
[20:25] <sil2100> robru:  adb shell touch /userdata/.writable-image is written there...
[20:27] <popey> then reboot
[20:30] <robru> sil2100, i tried to update it earlier but for some reason i can't login to the wiki... openid just loads forever & ever and never completes the login
[20:38] <sil2100> robru: I updated it
[20:39] <robru> sil2100, great, thx
[20:40] <robru> sil2100, ungh, using terminal on the n7 for the first time (usually just use adb shell). how do I scroll?? finger scrolling is scrolling up to previous inputs. i can't see how to scroll back to read old output
[20:42] <robru> sil2100, or, better question: how do I get autopilot tests to run from an adb shell? they just complain about not being able to connect to X that way
[20:47] <sil2100> robru: use ssh for that
[20:47] <sil2100> robru: just when using adb shell start ssh, connect and run autopilot - but remember you have to manually unlock the phone before running a test
[20:49] <robru> sil2100, buh, what's the default username/pw for the device?
[20:51] <sil2100> robru: phablet/phablet
[20:52] <robru> sil2100, huh, i thought i tried that, of course it works now...
[20:52] <robru> must have fat-fingered it pretty good
[20:52] <lool> pmcgowan: Right, I was asking about something else; the merge proposal you quote is the one allowing apps to open URLs using the url-dispatcher as the backend, and that's all in
[20:52] <sil2100> ;)
[20:53] <lool> pmcgowan: the ongoing work is about telling an app that would be able to open URLs to load a new URL if it's already running (rather than killing it to pass it on the cmdline)
[20:53] <pmcgowan> lool, right, and I think the toolkit has something added for the signal callback into QML
[20:53] <lool> sil2100: touch /userdata/.writable_path + reboot, or mount -o remount,rw /
[20:54] <sil2100> lool: all working already, but thanks
[21:00] <lool> pmcgowan: so the change in ubuntu-ui-toolkit is definitely the second type: support for org.freedesktop.Application; at least that's in r768
[21:00] <lool> by loicm
[21:25] <lool> Cool, music playback works with screen off and USB cable unplugged here  :-)
[21:26] <pmcgowan> lool, the behavior on the video lens is when you have a carousel with only 1 entry, it seems to jump around
[21:26] <pmcgowan> but not playing
[21:28] <lool> pmcgowan: exactly, but didn't manage to get it playing
[21:28] <lool> pmcgowan: if it works, great; after reboot I had 2 out of 3 videos picked up and indeed it worked as usual
[21:28] <pmcgowan> lool, 76 for sure!
[21:29] <lool> :-)
[21:29] <lool> pmcgowan: well in doubt I guess we should report this
[21:30] <lool> filing this against unity8
[21:30] <pmcgowan> I think its not that though
[21:30] <pmcgowan> video scope
[21:32] <lool> pmcgowan: is the carrousel in video scope?
[21:32] <pmcgowan> lool, I am guessing but I just have one vid
[21:32] <lool> pmcgowan: what's the name of the video scope?
[21:33] <lool> there's unity-scope-video-remote, but not sure
[21:33] <lool> seems only for remote videos
[21:33] <pmcgowan> lool, I cant find it either
[21:33] <lool> pmcgowan: the carousel is definitely in unity8
[21:33] <lool> Dash/Video/VideosCarousel.qml
[21:33] <lool> https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1233859
[21:33] <pmcgowan> ok lets log there
[21:33] <ubot5`> Ubuntu bug 1233859 in unity8 (Ubuntu) "Video carrousel doesn't activate mediaplayer for one video" [Undecided,New]
[21:33] <pmcgowan> oh
[21:33] <lool> Saviq: ^
[21:34] <pmcgowan> lool, oh I get it now, with 2 they work
[21:35] <lool> pmcgowan: yeah, that's what I was seeing in the sync call with rickspencer earlier today
[21:36] <lool> ah crap, I broke the displaystatechange thing in unity
[21:37] <Saviq> lool, pmcgowan https://bugs.launchpad.net/unity8/+bug/1226288
[21:37] <ubot5`> Ubuntu bug 1226288 in Unity 8 "Carousel should only be used when there's enough items" [Medium,Triaged]
[21:38] <pmcgowan> Saviq, indeed
[21:42] <lool> Saviq: thanks
[21:59] <thomi> doanac: still around?
[22:01] <doanac> thomi: yes
[22:01] <thomi> doanac: so I'm trying to run the ubuntuuitoolkit autopilot test suite...
[22:01] <thomi> doanac: I get the tests using the phablet-click-test-setup script...
[22:02] <thomi> doanac: but when I try and run the tests, it looks to me like the qml file(s) it launches and the desktop file it references are not present
[22:02] <thomi> doanac: so it seems I need to install some other package
[22:02] <thomi> and I was hoping you'd know what that was
[22:03] <doanac> thomi: let me check. plars just added support to for that in our daily smoke testing this afternoon
[22:03] <thomi> awesome, sorry, I'm not really sure who I should be pinging about thi
[22:03] <thomi> s
[22:03] <doanac> thomi: he sets up that test by installing the package. ie "apt-get install ubuntu-ui-toolkit-autopilot"
[22:04] <doanac> so the the click-setup might be missing a dependency
[22:05] <thomi> huh, ok, thanks :)
[22:05] <thomi> doanac: who maintains that script? They probably want to fix that :)
[22:05] <doanac> thomi: that would be sergiusens ^^^
[22:06]  * doanac thinks all roads lead back to sergiusens
[22:08] <sergiusens> hmm
[22:08]  * sergiusens looks
[22:09] <sergiusens> doanac, thomi ok, two weeks ago I said phablet-click-test-setup could potentially be used for testing ui-toolkit and unity8, but that required first getting the click stuff working
[22:09] <sergiusens> doanac, thomi not really missing a dependency, just not installing the extras from the binary package
[22:09]  * doanac bbiab
[22:10] <thomi> sergiusens: the confusion is that that script downloads the tests
[22:10] <thomi> sergiusens: I think it should either fully support ubuntuuitoolkit, or not at all
[22:10] <thomi> downloading the tests, but not the test dependencies is confusing.. to me, anyway
[22:10] <sergiusens> thomi, ah, well it doesn't I just download it so the emulators can be used from there
[22:10] <thomi> ahhhh
[22:10] <thomi> gotchya
[22:11] <sergiusens> thomi, same for unity8
[22:11] <sergiusens> thomi, with a bit more work, it could be made to work with everything
[22:11] <thomi> sergiusens: so I still need to install unity8-autopilot with apt-get before running those test suites?
[22:12] <sergiusens> thomi, yup, that's what I was just telling veebers on #ubuntu-unity
[22:12] <thomi> oh, cool
[22:12] <sergiusens> thomi, the click from phablet-click-test-setup probably needs to be removed once we support unit8 and the toolkit too :-)
[22:29] <thomi> yeah
[23:05] <kgunn> fginther: ...ping
[23:27] <robru> kgunn, ping ;-)
[23:29] <robru> kgunn, so, didrocks told me to poke you and ask for help testing mir on the device... I have the updated python-ubuntu-platform-api built in PPA and need help testing it before i can push it to distro
[23:32] <kgunn> robru: you can find us on #ubuntu-unity having loads of fun