[01:22] I wonder if someone from the CI team could comment on this bug? https://bugs.launchpad.net/autopilot/+bug/1210596 specifically, is this still a problem, or not? [01:22] Ubuntu bug 1210596 in Autopilot "Touch broken on nexus4" [Undecided,Incomplete] [01:29] ok, back [01:29] sorry for the delay [02:07] rsalveti: aha, I was wrong there are some places that do adb reboot [02:08] plars: cool [02:08] but noticed sometimes reboot takes quite a bit [02:08] at least I fixed the adb respawn when shutting down [02:08] rsalveti: well, I've had issues when rebooting with adb shell reboot today - at least with mir enabled [02:09] adb shell reboot; adb wait-for-device should work as expected [02:09] hm, right [02:11] thomi: this new unlock change that you and lool discussed earlier doesn't seem to be working for me [02:11] "Starting Unity with testability" is as far as I get, and it just stops there [02:11] plars: on a mako? [02:11] thomi: yes [02:11] * thomi reads the code [02:11] thomi: haven't tried on maguro yet [02:12] plars: it won't work on a maguro [02:12] ok [02:12] it should work tomorrow though [02:12] thomi: what's up with maguro? [02:12] plars: bug in ubuntu-platform-api [02:12] fixed already, just need to get it in the image [02:12] plars: where can I see that unlock code? I'm sure I had it open... [02:15] thomi: look at lool's branch here: https://code.launchpad.net/~lool/ubuntu-test-cases/powerd-lock/+merge/189191 [02:15] what am I searching for? that's a massive diff [02:16] thomi: it's against the wrong branch, just look at the latest change [02:16] oh, nvm, found it [02:16] plars: ahh, I think I see the problem [02:16] or, maybe not [02:16] hmmm [02:16] thomi: if you have something you want me to try locally, I can do so easily [02:17] plars: if the 'start' command is failing, it usually means one of two things: [02:18] 1) The screen is blanked [02:18] 2) There's a stale /tmp/mir_socket file lying around. [02:18] In either case, upstart will endlessly try and restart unity [02:18] and block forever [02:18] :( [02:18] so I'd make sure unity8 isn't running [02:18] then rm /tmp/mir_socket [02:19] the make sure you have a wakelock with powerd (make sure 'powerd-cli active' is runing somewhere) [02:19] then start unity8 [02:19] it's all a bit fragile at the moment :-( [02:19] thomi: sounds like [02:20] thomi: seems like unlocking has been a struggle for a long time - any chance of it ever being sane? [02:20] I had a hangout call with kgunn about it this morning [02:20] so I'd say "yes", but not for 1.0 [02:23] well, rebooting seems to work a little happier now at least [02:23] thomi: there was definitely a stray /tmp/mir_socket lingering around, let me see what I can do about that [02:24] that'll be the problem [02:24] err [02:24] this isn't good [02:24] when I reboot, I lose the device [02:24] rsalveti: is this related to what you described earlier? [02:24] rsalveti: I don't see it in adb devices anymore [02:25] plars: after the device is fully booted again? [02:25] if so, it might be the issue with adb x mtp [02:25] rsalveti: doesn't look like it, the screen is just black, and device is unresponsive [02:26] plars: right, so it's still rebooting [02:26] plars: that's the issue I noticed today [02:26] rsalveti: had to hard poweroff the device [02:26] ok [02:26] just takes forever? [02:26] plars: yeah, tried on maguro a few minutes ago and it took more than 2 minutes to reboot [02:26] wow [02:26] something is wrong in our shutdown logic [03:13] thomi: ok, so I still can't get the unity8 tests working at all, but at least I can get other tests working *I think* [03:14] plars: what happens with the unity8 tests? [03:14] thomi: I never see anything on the screen at all [03:14] thomi: and they all fail [03:14] plars: got a test log I can peek at? [03:14] even just for one test - I'm curious to see the failure condition [03:15] thomi: http://pastebin.ubuntu.com/6188183/ [03:15] hmmmm [03:15] ProcessSearchError: Process exited with exit code: -6 [03:15] what's signal 6? [03:16] SIGABT [03:16] also, this: terminate called after throwing an instance of 'boost::exception_detail::clone_impl >' [03:16] what(): display factory cannot create fb display [03:16] thomi: the error message appears there too [03:16] heh, beat me to it [03:17] ahhh [03:17] plars: can you try running this manually on the phone? 'unity8 -testability -fullscreen' - I bet it'll fail. Veebers, didn't we remove -fullscreen earlier today? [03:17] thomi: hmm, I wrote the code [03:17] that may be the problem - mir interprets '-fullscreen' as '-f ullscreen' [03:18] thomi: ugh, yeah let me push and propose :-\ [03:18] it got lost in the flurry [03:18] because, you know... programming [03:19] phablet@ubuntu-phablet:~$ unity8 -testability -fullscreen [03:19] __pthread_gettid -2 [03:19] terminate called after throwing an instance of 'boost::exception_detail::clone_impl >' [03:19] what(): Could not unblank display [03:19] Aborted (core dumped) [03:20] thomi: ^ [03:20] plars: now try without -fullscreen :) [03:20] plars: try it without the'-fullscreen' [03:20] heh [03:20] ugh thomi you're too fast [03:20] thomi: oh wait, let me do the powerd thing.. [03:21] thomi: ok, with powerd-cli active it seemed to do a bit more [03:21] ahh [03:21] thomi: yeah, with powerd-cli active running in the background, it worked [03:22] with -fullscreen'? [03:22] thomi: yes [03:22] huh, I guess that already got fixed in the image [03:23] plars: so it still doesn't work for the tests though? [03:24] thomi: well, let me try something [03:24] thomi: the unity8 tests are special [03:24] yes they are :) [03:25] heh [03:25] thomi: remind me why we removed -fullscreen earlier? (submitting a bug to attach) [03:25] veebers: it's not needed on the phone, and it caused problems with mir this morning. They may have patched mir by now though [03:26] thomi: thanks [03:29] thomi: are you alright approving it? https://code.launchpad.net/~veebers/unity8/remove_fullscreen_argument/+merge/189207 [03:30] veebers: that's only on the device, right? [03:30] thomi: yep, otherwise width|height are set to a value [03:35] approved. I have to step out for a bit, but I'll be back again [03:38] thomi: cheers [04:01] * thomi is back === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha [08:09] plars: heya [08:10] plars: so reading through the backlog, it seems the issues you were seeing were around boot time / shutdown on one side, and sometimes mir_socket; the powerd-cli active thing is the equivalent of the dbus code I've added, except it's actually easier to do the dbus thing in python than spawning and stopping a subprocess cleanly IMO [08:10] (hey alL!) [08:11] psivaa: hey [08:11] psivaa: did you dive a bit in failing tests on 80? [08:11] lool: yes just started a couple of them and watching them [08:12] ok [08:12] psivaa: ok, unity8 is probably the longest but most interesting on es [08:12] *one [08:13] the other ones are relatively isolated and seem to be in apps themselves, not 100% sure though [08:13] psivaa: how's the Mir stuff looking this morning? [08:13] lool: ok, ill try unity8 in one device [08:13] we lost dbus.log from utah [08:13] :/ [08:13] lool: i am just starting to do the Mir stuff [08:14] psivaa: ok [08:14] psivaa: (how many devices do you have? :-) [08:14] ogra_: ? [08:15] lool: locally only one maguro [08:15] hmm that's not much [08:15] psivaa: so you're testing Mir on maguro? [08:15] must not be going well [08:15] lool: yes, until yesterday the results were not that good on that [08:15] psivaa: ah but you're running remote tests? [08:15] lool: yea [08:15] lool, http://reports.qa.ubuntu.com/smokeng/saucy/touch_ro/4539/unity8-autopilot/ image 79 ... and the same test on image #80 http://reports.qa.ubuntu.com/smokeng/saucy/touch_ro/4541/unity8-autopilot/ [08:16] lool, with a dbus change from xnox inbetween, i guess that changed the logging behavior somehow alongside [08:17] ogra_: but I see dbus.log there [08:17] lool, in the second link ? [08:17] ah [08:17] :) [08:18] indeed, always empty [08:18] hmmm [08:18] root@ubuntu-phablet:/# ls /home/phablet/.cache/upstart/dbus.log [08:18] ls: cannot access /home/phablet/.cache/upstart/dbus.log: No such file or directory [08:18] freshly flashed, first boot [08:19] Poked xnox [08:19] i assume just adding a "console log" to the upstart job might help [08:19] i did already 30min ago [08:19] ogra_: did it work? [08:21] havent tried that [08:21] one sec [08:21] image isnt writable yet and i want to check some things before doing so [08:21] ok [08:23] sil2100, Mirv: how are things for you guys this morning? [08:24] lool: morning! I'm updating my device and will test indicators [08:24] yay, the dbus fix helps a good bunch [08:25] stopwatched my boot takes 25sec from vibration to unity now [08:25] ogra_, what sort of issues does it fix? segfaults? [08:25] on mako [08:25] lool: busy, but ok.. [08:25] seb128, boot delays [08:25] ogra_, is the dbus-daemon zombie going away with it? [08:25] seb128, i'll check after the landing meeting, need to set up bootchart etc [08:26] ok [08:26] settings in, some qtbase work, ui-toolkit testing (just one commit), now testing unity8 [08:26] but from the gut feeling it does [08:26] boots a lot faster [08:26] (excelpt for the first boot where apparmor hogs the device) [08:26] * ogra_ gets coffee [08:28] ogra_: console log is the default. [08:31] lool, Mirv: I'll be back in a moment and join the meeting, need to reboot my modem as it's beeping loudly [08:31] sil2100, vila: Joining [08:31] ok [08:31] brb [08:31] lool: omw [08:31] lool: I'll do more testing but I'd need packaging acks http://pastebin.ubuntu.com/6191237/ (indicator-network) http://pastebin.ubuntu.com/6191239/ (unity-notifications) http://pastebin.ubuntu.com/6191241/ (unity8) [08:31] xnox, well, it would be nice to get the logs back .... the fix helps a lot with boot speed btw ! === sil2100_ is now known as sil2100 [08:40] psivaa: add daily-build PPA and apt-get install unity8-autopilot unity8-fake-env unity8 unity8-private qtdeclarative5-unity-notifications-plugin indicator-network [08:40] Mirv: sure, will do [08:40] Mirv: what version of autopilot that you are using? .. just to confirm [08:41] psivaa: it's the new one, I just checked [08:41] 1.3.1+13.10.20131003.1-0ubuntu1 [08:41] Mirv: ack [08:41] ie. I flashed image 80 [08:55] Mirv: forgot to ask, what's status on toolkit update? you had reported some bugs to SDK team, and then they went to fix them, did they come back with fixes in trunk? [08:56] lool: balloons was looking at it, apparently path changes that need to be fixed in the apps but is still ongoing, branches linked at https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1234544 [08:57] Ubuntu bug 1234544 in Ubuntu UI Toolkit "Several apps have failing tests with 20131003 ui-toolkit" [Critical,In progress] [08:57] Mirv: were there other regressions in the toolkit outside of this? [08:58] lool: not known, that caused so many errors it was hard to say [08:58] ok [08:58] lool: can you look at the packaging acks at :31 ^ [08:58] Mirv: so you'd need another round of testing with these fixes in place to find out [08:58] lool: plus http://pastebin.ubuntu.com/6191421/, so that I've everything ready ack wise when I've done testing [08:59] lool: yes [08:59] Mirv: looking at packaging acks [09:00] Mirv: ok for packaging changes [09:00] Mirv: oh sorry just first one [09:01] Mirv: indicator-network is +1 [09:01] Mirv: what do we need to rebuld for unity-notifications change in Provides? [09:01] ah unity8 [09:02] that, yes [09:03] Mirv: ok for unity8 and unity-notifications [09:03] Mirv: might want to keep an eye on new indicator though [09:03] + * Added an indicator which is displayed in the search bar whenever a [09:03] + search is in progress. Added accompanying test in tst_PageHeader. [09:05] Saviq: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1235000 [09:05] Ubuntu bug 1235000 in unity8 (Ubuntu) "Unity8 wont start on Mir when screen is blanked" [Undecided,New] [09:05] right [09:11] lool, https://bugs.launchpad.net/mir/+bug/1216237 [09:11] Ubuntu bug 1216237 in mir (Ubuntu) "Mir silently overwrites and reuses /tmp/mir_socket, rendering the previous server useless" [Medium,Fix released] [09:15] * lool & [09:15] lool: as for indicators, I'm not sure if we should release indicator-network today, as it requires the new unity8 to be released with it [09:18] sil2100: no, that's the item above yours that I'm handling, don't worry about indicator-network :) [09:18] Ah! ;) [09:31] lool, can you link me the doc? I'll put a ~table of suites to add their "owners" to under mir === vrruiz_ is now known as rvr [09:54] lool, http://studio.sketchpad.cc/uRlqdixl3G? [10:01] plars, hey can you please point me as to how to run click autopilot suites? [10:01] plars, I saw some "click-setup-autopilot-something-fancy-stuff" [10:02] but can't find it now [10:06] phablet-click-test-setup isn't it? [10:07] cjwatson, thanks! [10:17] Mirv: lool: i've run unity8 tests locally with clean 80, 3 times and all the times they passed without failures. Not sure what's causing the 2 failures in the lab.. [10:17] looking though [10:23] psivaa: Ok, it might also be the unity8 update in the PPA fixing it? [10:23] psivaa: but if they pass for you, it's good [10:24] lool: i have not done the update yet though.. [10:24] Saviq: thanks, I was about to satrt a google doc spreadsheet actually [10:24] lool, whatever you prefer [10:25] Saviq: I'd like to collect results with image numbers, testers, failures etc. (a bit like report.qa. but manually since that's what we have) [10:25] psivaa: ok, don't spend more time on this, it passes locally for you, that's good [10:25] psivaa: move to the update and/or mir stuff :-) [10:26] lool, just let us know where to push our results [10:26] lool: yep doing that :) [10:26] Mirv: are you done with indicator-network testing? otherwise I thought we could try with the NM changes [10:26] * lool is not as efficient as didrocks on thinking this through [10:28] lool: yes, the i-n + unity8 + unity-notifications is now published. but now for a late lunch. [10:29] the new password prompt was quite neat looking [10:30] Saviq: https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0ApRxJIi-SaMddEdtdWtMaXNkMzYtN2puZ2YxdU9MekE#gid=0 [10:30] Saviq: just shared read/write now [10:30] Saviq: I've moved most inprogress tests [10:30] psivaa: ^ [10:31] psivaa: spreadsheet to track Mir results https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0ApRxJIi-SaMddEdtdWtMaXNkMzYtN2puZ2YxdU9MekE#gid=0 [10:31] Mirv: good lunch [10:31] * lool lunches too [10:32] lool: ack, will use that [10:42] psivaa, if you haven't really started calculator yet... I'm running it [10:43] psivaa, sorry - should've added to the spread already, but got calendar and calculator confused... [10:43] Saviq: ok, i've just started to run.. let that finish and then ill go to webbrowser [11:12] sil2100: regarding your unity7 remark, it always has failing tests so the question is that are there more, and whether they can be manually marked as false alarms (as before) [11:14] sil2100: I already released libunity and unity-scope-home yesterday, and on my own machine the tests were fine. so, you can also compare to for example this check run http://localhost:8080/job/autopilot-saucy-daily_release/2311/ <- that's the result, on reality on my own machine I got only 20 FAILs and they were false alarms as well (actual functionality worked) [11:16] sil2100: ok forget the last remark, obviously I only tested those components I was about to release, so you can't assume that run as a whole was ok. but anyway, you know the drill, manual work.. [11:28] Mirv: I know, I was running some AP tests already on unity7, and it looks fine - mostly false positives [11:30] balloons: just to confirm, are you dealing with all the core app smoke failures with bug #1234544? [11:30] bug 1234544 in Ubuntu UI Toolkit "Several apps have failing tests with 20131003 ui-toolkit" [Critical,In progress] https://launchpad.net/bugs/1234544 [11:37] psivaa: hey. I'm struggling running autopilot with mir on the galaxy nexus and was told you see the same [11:38] any solution yet? [11:38] like: there seems no input at all, screen blanks during tests and cannot be woken up again after that [11:38] mzanetti i had packages from unity daily ppa and Saviq said that's not intended [11:39] hmm... I just did a clean flash [11:39] installed the autopilot package and ran tests... [11:40] mzanetti, ah no input? [11:40] mzanetti, I *think* I read something about that about the galaxy [11:40] lool, you aware of what that was ↑? no input during autopilot on maguro? [11:41] (works fine with SF) [11:45] sil2100: ok, sounds good, hopefully that holds. [12:02] mzanetti: Saviq: re no input on maguro - known issue, fixed, waiting to be landed in the image [12:02] it's a defect in python-upa [12:02] thomi, released yet? [12:02] already in the landing pipeline SS [12:02] thomi, ok, so no [12:02] Saviq: it's in trunk, I haven't checked since I finished work [12:03] mzanetti, you can build python-upa out of lp:python-upa to fix your input [12:03] psivaa, ↑ you'll want that too [12:03] actually /me builds [12:03] * thomi -> EOW [12:06] aaand it rebooted :/ [12:07] Saviq: ohh ok, thanks. that may explain my first run of webbrowser test failures (34/35 failed) thanks [12:07] Saviq: yes, that's fixed with python-platform-api update I think [12:08] Saviq: the maguro thing was that autopilot/python-platform-api/platform-api are using an unsupported android property; it happens to work on mako, but not on maguro; another property works though [12:08] psivaa, will have a fixed package in 5 [12:08] lool, yup, got it [12:08] Saviq: if you update python-platform-api, it shoudl work though [12:08] lool, not released yet [12:08] Saviq: thanks [12:09] Saviq: it's being tested, it's in ubuntu-unity/daily-build PPA [12:09] Saviq: see landing spreadsheet === alan_g is now known as alan_g|lunch [12:10] lool, right, I don't trust the daily-build ppa ;P [12:10] lool, if it's not released - it's not there! [12:10] Saviq: forgot device in Mir tests; would you add the ones you know? [12:10] I'm assuming mostly mako [12:10] psivaa: ^ [12:10] Saviq: haha [12:10] Saviq: it's in flight [12:10] Saviq: this is just to unblock you and to give you status [12:11] Saviq: if it's not in a *PROMOTED IMAGE* it doesn't exist ;-) [12:11] (we have even harder rules ;-) [12:11] lool, yup :) [12:21] lool, ogra_ can we add upstart into the landing plan? https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1234898 [12:21] Ubuntu bug 1234898 in upstart (Ubuntu) "upstart-local-bridge not handling all events sent to it" [Undecided,In progress] [12:22] lool, ogra_ it's a fix for the upstart-local-bridge which is not used by anyone yet, so should be low impact [12:22] psivaa, here's the fixed package http://people.canonical.com/~msawicz/papi/ [12:22] sergiusens: Yes [12:22] sergiusens: please upload ASAP [12:22] sergiusens, yeah [12:22] Saviq: thanks, will update [12:22] lool, ogra_ well we need jodh to do that :-) [12:23] sergiusens, pinged him in -touch [12:26] I've pinged him in -release [12:26] gah, I'm so late in testing and in sending emails out [12:26] wow, I thought this was an off the radar fix :-) [12:26] I've had an issue with my laptop's saucy, wasted one hour [12:26] * ogra_ still fights with ureadahead today [12:26] system-image breaks it :( [12:27] ogra_: how so? [12:27] lool, ureadahead uses /var/lib/ureadahead/debugfs for reading ... to make uredahead work i need to make /var/lib/ureadahead writable so it can store its pack files there ... [12:28] making it writable mounts rw fs over the existing /var/lib/ureadahead and the debugfs mount is hidden [12:29] ogra_: talk to stgraber about best way to handle this I guess [12:29] ogra_: it's not urgent I guess [12:29] i can easily work around it by adding a pre-start script to the ureadahead upstart job that remounts /var/lib/ureadahead/debugfs before firing up, but waiting on stgraber, probably system-image stuff can work around this [12:30] lool, well, i'd like to have a sane boot by reklease ... its one of many small issues [12:30] ogra_: can you also track the status of the powerd changes? [12:30] ogra_: these are in the spreadsheet for many days now [12:30] (not as big as the hud dieing all the time and delaying the boot by 20sec indeed) [12:30] lool, yeah, will land it today ... but probably not for 81 [12:31] ogra_: can you test the dbus binaries that got uploaded on touch? [12:31] ogra_: I've added a row for you on this one [12:32] lool, i tested it before the upload happened :) but will verify it also works with the package [12:33] ogra_: thanks [12:33] Mirv: ok, I actually checked all the failing tests - 99% of them are either false positives (so test environment issues), others are AP issues - I'll report those to bregma and release ;) [12:34] Saviq: mzanetti: no luck yet even with the upa package above (1.1+13.10.20131001.1-0ubuntu2~sbuild1) on maguro. [12:34] psivaa, do you see stuff happening on screen at all? [12:34] sil2100: \o/ [12:35] Saviq: that i see, webbrowser is opening but the tests at some stage are failing [12:35] psivaa, but I mean do the test interact with the browser at all? [12:36] psivaa, or does it just launch it and sit there [12:36] sil2100, we track all the failures in the Unity7 builds and already have bugs open on the non-environmental ones [12:37] without that bran it gets launched and sits there. but not waiting for the usual autopilot 10 secs timeout but closing down faster [12:37] Saviq: webbrowser launches, opens the localhost web and then it does not do anything more [12:37] s/localhost web/web page/ [12:38] bregma: awesome [12:38] it would be more awesome if there were no bugs, but we're doing our best [12:39] bregma: since I also noticed that there seems to be something wrong with for instance self.assertVisibleWindowStack(), as the visible window stack seems to be OK, but the call still fails as if it was not ;) [12:40] bregma: not sure if that's even because of unity, or maybe an autopilot issue itself [12:41] psivaa, sounds like your input issue isn't solved indeed [12:41] psivaa, can you try with the version from daily-build ppa then? [12:42] Saviq: ack, will do. thanks. [12:43] * psivaa -> reboot === alan_g|lunch is now known as alan_g [12:58] lool, btw, for the "unity8 is launching slow" - it's most probably hud-service crashing - and unity8 is blocking on that service with a timeout [12:59] trying to overwrite '/usr/share/icons/ubuntu-mobile/apps/144/gallery-app.png', which is also in package ubuntu-mobile-icons 13.04+13.10.20130925-0ubuntu1 [12:59] Saviq: great discovery [12:59] Saviq: indeed, hud seems quite unhappy [12:59] Saviq: they recently added some debug to see what was going on [13:00] Saviq: generating the crash file will also slow down the device [13:00] lool, yup [13:00] Saviq: did you find a crash file for hud and an existing bug report? [13:00] Saviq: could you raise it with ted/whoever worked on this last? [13:00] sergiusens: heya [13:00] sergiusens: we're reading up to switch to Mir [13:00] lool, yeah [13:00] sergiusens: not this image, but soon [13:00] lool, it's always the same crash [13:01] lool, have made apport ignore it for now.. [13:01] sergiusens: would you know how to patch the image build to touch .display-mir (or .display_mir I never remember which, I touch both :-) [13:01] lool, Saviq, http://people.canonical.com/~ogra/ubuntu-touch/bootchart-maguro-hud-dbus-hang.png ... watch the dbus zombie ... vs http://people.canonical.com/~ogra/ubuntu-touch/bootchart-maguro-SF.png [13:01] sergiusens: that way, people could opt out of it and they keep what they had [13:01] lool, .display-mir [13:01] seems the HUD gets dbus in a weird state [13:01] when it crashes [13:01] sergiusens: if you could prepare that change in a bzr branch, that would be cool [13:01] sergiusens: especially since I might be enabling this over the WE [13:02] ogra_, /me no grok those charts ;) [13:02] lool, it's 3 locations currently; we are ramping up a phablet-config tool with doanac and cwayne, i thought I'd just add a switch there to --enable disabel mir [13:03] Saviq, it shows that with SF todays image boots in ~30sec ... but with Mir hud-service crashes and tears down dbus with it ... which results in a 50sec boot [13:03] ogra_, ught [13:04] Saviq, mhr3_, pete-woods and ted are on it since yesterday [13:04] good [13:04] (probably longer) [13:06] sergiusens: yes, that's useful; we still need a way to enforce the default, and that ought to be in the image [13:07] home/phablet was perhaps a poor choice, but it's all hooked up with this now, so I'd rather we use this rather than doing code changes somewhere else [13:09] morning [13:09] lool, we talked about it, on ro it was sort of the only choice at the time; location readable and writable by users and system; and to be honest, it was supposed to last a week tops ;-) so creating another writable location for this seems a bit too much [13:09] lool, that said, we can transform it into a property now :-) [13:10] :-) [13:11] fginther: good mooooornnnnniiiiiiiing! [13:12] lool: can you scheudle landing ask line 93 so that we finally get thumbnailing working? [13:13] Saviq: i'll enter my maguro results at the bottom of the page if that's ok [13:14] psivaa, well... if you don't get input... kind of beats the purpose [13:15] Saviq: that's true.. the output is the same, even with upa from the daily ppa: 1.1+13.10.20131004-0ubuntu1 [13:15] lool, [13:16] ↑↑ [13:16] thostr_1: ubuntu-ui-toolkit is not going in soon [13:16] thostr_1: it's pending fixes [13:16] lool: are we running ubuntu-keyboard tests now automatically on the image testings? [13:16] thostr_1: so it would kind of pollute the view (much like the open URL stuff staged already, blocked on ui-toolkit) [13:16] thostr_1: also, Mir going in pretty soon [13:16] lool: since those are failing badly for the new ubuntu-keyboard right now [13:16] thostr_1: so this will be likely be next week [13:16]