[01:22] <thomi> 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:29] <plars> ok, back
[01:29] <plars> sorry for the delay
[02:07] <plars> rsalveti: aha, I was wrong there are some places that do adb reboot
[02:08] <rsalveti> plars: cool
[02:08] <rsalveti> but noticed sometimes reboot takes quite a bit
[02:08] <rsalveti> at least I fixed the adb respawn when shutting down
[02:08] <plars> rsalveti: well, I've had issues when rebooting with adb shell reboot today - at least with mir enabled
[02:09] <rsalveti> adb shell reboot; adb wait-for-device should work as expected
[02:09] <rsalveti> hm, right
[02:11] <plars> thomi: this new unlock change that you and lool discussed earlier doesn't seem to be working for me
[02:11] <plars> "Starting Unity with testability" is as far as I get, and it just stops there
[02:11] <thomi> plars: on a mako?
[02:11] <plars> thomi: yes
[02:11]  * thomi reads the code
[02:11] <plars> thomi: haven't tried on maguro yet
[02:12] <thomi> plars: it won't work on a maguro
[02:12] <plars> ok
[02:12] <thomi> it should work tomorrow though
[02:12] <plars> thomi: what's up with maguro?
[02:12] <thomi> plars: bug in ubuntu-platform-api
[02:12] <thomi> fixed already, just need to get it in the image
[02:12] <thomi> plars: where can I see that unlock code? I'm sure I had it open...
[02:15] <plars> thomi: look at lool's branch here: https://code.launchpad.net/~lool/ubuntu-test-cases/powerd-lock/+merge/189191
[02:15] <thomi> what am I searching for? that's a massive diff
[02:16] <plars> thomi: it's against the wrong branch, just look at the latest change
[02:16] <thomi> oh, nvm, found it
[02:16] <thomi> plars: ahh, I think I see the problem
[02:16] <thomi> or, maybe not
[02:16] <thomi> hmmm
[02:16] <plars> thomi: if you have something you want me to try locally, I can do so easily
[02:17] <thomi> plars: if the 'start' command is failing, it usually means one of two things:
[02:18] <thomi> 1) The screen is blanked
[02:18] <thomi> 2) There's a stale /tmp/mir_socket file lying around.
[02:18] <thomi> In either case, upstart will endlessly try and restart unity
[02:18] <thomi> and block forever
[02:18] <thomi> :(
[02:18] <thomi> so I'd make sure unity8 isn't running
[02:18] <thomi> then rm /tmp/mir_socket
[02:19] <thomi> the make sure you have a wakelock with powerd (make sure 'powerd-cli active' is runing somewhere)
[02:19] <thomi> then start unity8
[02:19] <thomi> it's all a bit fragile at the moment :-(
[02:19] <plars> thomi: sounds like
[02:20] <plars> thomi: seems like unlocking has been a struggle for a long time - any chance of it ever being sane?
[02:20] <thomi> I had a hangout call with kgunn about it this morning
[02:20] <thomi> so I'd say "yes", but not for 1.0
[02:23] <plars> well, rebooting seems to work a little happier now at least
[02:23] <plars> thomi: there was definitely a stray /tmp/mir_socket lingering around, let me see what I can do about that
[02:24] <thomi> that'll be the problem
[02:24] <plars> err
[02:24] <plars> this isn't good
[02:24] <plars> when I reboot, I lose the device
[02:24] <plars> rsalveti: is this related to what you described earlier?
[02:24] <plars> rsalveti: I don't see it in adb devices anymore
[02:25] <rsalveti> plars: after the device is fully booted again?
[02:25] <rsalveti> if so, it might be the issue with adb x mtp
[02:25] <plars> rsalveti: doesn't look like it, the screen is just black, and device is unresponsive
[02:26] <rsalveti> plars: right, so it's still rebooting
[02:26] <rsalveti> plars: that's the issue I noticed today
[02:26] <plars> rsalveti: had to hard poweroff the device
[02:26] <plars> ok
[02:26] <plars> just takes forever?
[02:26] <rsalveti> plars: yeah, tried on maguro a few minutes ago and it took more than 2 minutes to reboot
[02:26] <plars> wow
[02:26] <rsalveti> something is wrong in our shutdown logic
[03:13] <plars> 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] <thomi> plars: what happens with the unity8 tests?
[03:14] <plars> thomi: I never see anything on the screen at all
[03:14] <plars> thomi: and they all fail
[03:14] <thomi> plars: got a test log I can peek at?
[03:14] <thomi> even just for one test - I'm curious to see the failure condition
[03:15] <plars> thomi: http://pastebin.ubuntu.com/6188183/
[03:15] <thomi> hmmmm
[03:15] <thomi> ProcessSearchError: Process exited with exit code: -6
[03:15] <thomi> what's signal 6?
[03:16] <thomi> SIGABT
[03:16] <thomi> also, this: terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >'
[03:16] <thomi> what(): display factory cannot create fb display
[03:16] <veebers> thomi: the error message appears there too
[03:16] <veebers> heh, beat me to it
[03:17] <thomi> ahhh
[03:17] <thomi> 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] <veebers> thomi: hmm, I wrote the code
[03:17] <thomi> that may be the problem - mir interprets '-fullscreen' as '-f ullscreen'
[03:18] <veebers> thomi: ugh, yeah let me push and propose :-\
[03:18] <veebers> it got lost in the flurry
[03:18] <thomi> because, you know... programming
[03:19] <plars> phablet@ubuntu-phablet:~$ unity8 -testability -fullscreen
[03:19] <plars> __pthread_gettid -2
[03:19] <plars> terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >'
[03:19] <plars>   what():  Could not unblank display
[03:19] <plars> Aborted (core dumped)
[03:20] <plars> thomi: ^
[03:20] <thomi> plars: now try without -fullscreen :)
[03:20] <veebers> plars: try it without the'-fullscreen'
[03:20] <thomi> heh
[03:20] <veebers> ugh thomi you're too fast
[03:20] <plars> thomi: oh wait, let me do the powerd thing..
[03:21] <plars> thomi: ok, with powerd-cli active it seemed to do a bit more
[03:21] <thomi> ahh
[03:21] <plars> thomi: yeah, with powerd-cli active running in the background, it worked
[03:22] <thomi> with -fullscreen'?
[03:22] <plars> thomi: yes
[03:22] <thomi> huh, I guess that already got fixed in the image
[03:23] <thomi> plars: so it still doesn't work for the tests though?
[03:24] <plars> thomi: well, let me try something
[03:24] <plars> thomi: the unity8 tests are special
[03:24] <thomi> yes they are :)
[03:25] <plars> heh
[03:25] <veebers> thomi: remind me why we removed -fullscreen earlier? (submitting a bug to attach)
[03:25] <thomi> 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] <veebers> thomi: thanks
[03:29] <veebers> thomi: are you alright approving it? https://code.launchpad.net/~veebers/unity8/remove_fullscreen_argument/+merge/189207
[03:30] <thomi> veebers: that's only on the device, right?
[03:30] <veebers> thomi: yep, otherwise width|height are set to a value
[03:35] <thomi> approved. I have to step out for a bit, but I'll be back again
[03:38] <veebers> thomi: cheers
[04:01]  * thomi is back
[08:09] <lool> plars: heya
[08:10] <lool> 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] <lool> (hey alL!)
[08:11] <lool> psivaa: hey
[08:11] <lool> psivaa: did you dive a bit in failing tests on 80?
[08:11] <psivaa> lool: yes just started a couple of them and watching them
[08:12] <lool> ok
[08:12] <lool> psivaa: ok, unity8 is probably the longest but most interesting on es
[08:12] <lool> *one
[08:13] <lool> the other ones are relatively isolated and seem to be in apps themselves, not 100% sure though
[08:13] <lool> psivaa: how's the Mir stuff looking this morning?
[08:13] <psivaa> lool: ok, ill try unity8 in one device
[08:13] <ogra_> we lost dbus.log from utah
[08:13] <ogra_> :/
[08:13] <psivaa> lool: i am just starting to do the Mir stuff
[08:14] <lool> psivaa: ok
[08:14] <lool> psivaa: (how many devices do you have? :-)
[08:14] <lool> ogra_: ?
[08:15] <psivaa> lool: locally only one maguro
[08:15] <lool> hmm that's not much
[08:15] <lool> psivaa: so you're testing Mir on maguro?
[08:15] <lool> must not be going well
[08:15] <psivaa> lool: yes, until yesterday the results were not that good on that
[08:15] <lool> psivaa: ah but you're running remote tests?
[08:15] <psivaa> lool: yea
[08:15] <ogra_> 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] <ogra_> lool, with a dbus change from xnox inbetween, i guess that changed the logging behavior somehow alongside
[08:17] <lool> ogra_: but I see dbus.log there
[08:17] <ogra_> lool, in the second link ?
[08:17] <lool> ah
[08:17] <ogra_> :)
[08:18] <lool> indeed, always empty
[08:18] <lool> hmmm
[08:18] <ogra_> root@ubuntu-phablet:/# ls /home/phablet/.cache/upstart/dbus.log
[08:18] <ogra_> ls: cannot access /home/phablet/.cache/upstart/dbus.log: No such file or directory
[08:18] <ogra_> freshly flashed, first boot
[08:19] <lool> Poked xnox
[08:19] <ogra_> i assume just adding a "console log" to the upstart job might help
[08:19] <ogra_> i did already 30min ago
[08:19] <lool> ogra_: did it work?
[08:21] <ogra_> havent tried that
[08:21] <ogra_> one sec
[08:21] <ogra_> image isnt writable yet and i want to check some things before doing so
[08:21] <lool> ok
[08:23] <lool> sil2100, Mirv: how are things for you guys this morning?
[08:24] <sil2100> lool: morning! I'm updating my device and will test indicators
[08:24] <ogra_> yay, the dbus fix helps a good bunch
[08:25] <ogra_> stopwatched my boot takes 25sec from vibration to unity now
[08:25] <seb128> ogra_, what sort of issues does it fix? segfaults?
[08:25] <ogra_> on mako
[08:25] <Mirv> lool: busy, but ok..
[08:25] <ogra_> seb128, boot delays
[08:25] <seb128> ogra_, is the dbus-daemon zombie going away with it?
[08:25] <ogra_> seb128, i'll check after the landing meeting, need to set up bootchart etc
[08:26] <seb128> ok
[08:26] <Mirv> settings in, some qtbase work, ui-toolkit testing (just one commit), now testing unity8
[08:26] <ogra_> but from the gut feeling it does
[08:26] <ogra_> boots a lot faster
[08:26] <ogra_> (excelpt for the first boot where apparmor hogs the device)
[08:26]  * ogra_ gets coffee
[08:28] <xnox> ogra_: console log is the default.
[08:31] <sil2100> 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] <lool> sil2100, vila: Joining
[08:31] <lool> ok
[08:31] <sil2100> brb
[08:31] <vila> lool: omw
[08:31] <Mirv> 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] <ogra_> xnox, well, it would be nice to get the logs back .... the fix helps a lot with boot speed btw !
[08:40] <Mirv> 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] <psivaa> Mirv: sure, will do
[08:40] <psivaa> Mirv: what version of autopilot that you are using? .. just to confirm
[08:41] <Mirv> psivaa: it's the new one, I just checked
[08:41] <Mirv> 1.3.1+13.10.20131003.1-0ubuntu1
[08:41] <psivaa> Mirv: ack
[08:41] <Mirv> ie. I flashed image 80
[08:55] <lool> 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] <Mirv> 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] <lool> Mirv: were there other regressions in the toolkit outside of this?
[08:58] <Mirv> lool: not known, that caused so many errors it was hard to say
[08:58] <lool> ok
[08:58] <Mirv> lool: can you look at the packaging acks at :31 ^
[08:58] <lool> Mirv: so you'd need another round of testing with these fixes in place to find out
[08:58] <Mirv> lool: plus http://pastebin.ubuntu.com/6191421/, so that I've everything ready ack wise when I've done testing
[08:59] <Mirv> lool: yes
[08:59] <lool> Mirv: looking at packaging acks
[09:00] <lool> Mirv: ok for packaging changes
[09:00] <lool> Mirv: oh sorry just first one
[09:01] <lool> Mirv: indicator-network is +1
[09:01] <lool> Mirv: what do we need to rebuld for unity-notifications change in Provides?
[09:01] <lool> ah unity8
[09:02] <Mirv> that, yes
[09:03] <lool> Mirv: ok for unity8 and unity-notifications
[09:03] <lool> Mirv: might want to keep an eye on new indicator though
[09:03] <lool> +  * Added an indicator which is displayed in the search bar whenever a
[09:03] <lool> +    search is in progress. Added accompanying test in tst_PageHeader.
[09:05] <lool> Saviq: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1235000
[09:05] <Mirv> right
[09:11] <Saviq> lool, https://bugs.launchpad.net/mir/+bug/1216237
[09:15]  * lool &
[09:15] <sil2100> 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] <Mirv> sil2100: no, that's the item above yours that I'm handling, don't worry about indicator-network :)
[09:18] <sil2100> Ah! ;)
[09:31] <Saviq> lool, can you link me the doc? I'll put a ~table of suites to add their "owners" to under mir
[09:54] <Saviq> lool, http://studio.sketchpad.cc/uRlqdixl3G?
[10:01] <Saviq> plars, hey can you please point me as to how to run click autopilot suites?
[10:01] <Saviq> plars, I saw some "click-setup-autopilot-something-fancy-stuff"
[10:02] <Saviq> but can't find it now
[10:06] <cjwatson> phablet-click-test-setup isn't it?
[10:07] <Saviq> cjwatson, thanks!
[10:17] <psivaa> 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] <psivaa> looking though
[10:23] <lool> psivaa: Ok, it might also be the unity8 update in the PPA fixing it?
[10:23] <lool> psivaa: but if they pass for you, it's good
[10:24] <psivaa> lool: i have not done the update yet though..
[10:24] <lool> Saviq: thanks, I was about to satrt a google doc spreadsheet actually
[10:24] <Saviq> lool, whatever you prefer
[10:25] <lool> 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] <lool> psivaa: ok, don't spend more time on this, it passes locally for you, that's good
[10:25] <lool> psivaa: move to the update and/or mir stuff  :-)
[10:26] <Saviq> lool, just let us know where to push our results
[10:26] <psivaa> lool: yep doing that :)
[10:26] <lool> 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] <Mirv> lool: yes, the i-n + unity8 + unity-notifications is now published. but now for a late lunch.
[10:29] <Mirv> the new password prompt was quite neat looking
[10:30] <lool> Saviq: https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0ApRxJIi-SaMddEdtdWtMaXNkMzYtN2puZ2YxdU9MekE#gid=0
[10:30] <lool> Saviq: just shared read/write now
[10:30] <lool> Saviq: I've moved most inprogress tests
[10:30] <lool> psivaa: ^
[10:31] <lool> psivaa: spreadsheet to track Mir results https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0ApRxJIi-SaMddEdtdWtMaXNkMzYtN2puZ2YxdU9MekE#gid=0
[10:31] <lool> Mirv: good lunch
[10:31]  * lool lunches too
[10:32] <psivaa> lool: ack, will use that
[10:42] <Saviq> psivaa, if you haven't really started calculator yet... I'm running it
[10:43] <Saviq> psivaa, sorry - should've added to the spread already, but got calendar and calculator confused...
[10:43] <psivaa> Saviq: ok, i've just started to run.. let that finish and then ill go to webbrowser
[11:12] <Mirv> 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] <Mirv> 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] <Mirv> 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] <sil2100> Mirv: I know, I was running some AP tests already on unity7, and it looks fine - mostly false positives
[11:30] <psivaa> balloons: just to confirm, are you dealing with all the core app smoke failures with bug #1234544?
[11:37] <mzanetti> psivaa: hey. I'm struggling running autopilot with mir on the galaxy nexus and was told you see the same
[11:38] <mzanetti> any solution yet?
[11:38] <mzanetti> like: there seems no input at all, screen blanks during tests and cannot be woken up again after that
[11:38] <psivaa>  mzanetti i had packages from unity daily ppa and Saviq said that's not intended
[11:39] <mzanetti> hmm... I just did a clean flash
[11:39] <mzanetti> installed the autopilot package and ran tests...
[11:40] <Saviq> mzanetti, ah no input?
[11:40] <Saviq> mzanetti, I *think* I read something about that about the galaxy
[11:40] <Saviq> lool, you aware of what that was ↑? no input during autopilot on maguro?
[11:41] <mzanetti> (works fine with SF)
[11:45] <Mirv> sil2100: ok, sounds good, hopefully that holds.
[12:02] <thomi> mzanetti: Saviq: re no input on maguro - known issue, fixed, waiting to be landed in the image
[12:02] <thomi> it's a defect in python-upa
[12:02] <Saviq> thomi, released yet?
[12:02] <thomi> already in the landing pipeline SS
[12:02] <Saviq> thomi, ok, so no
[12:02] <thomi> Saviq: it's in trunk, I haven't checked since I finished work
[12:03] <Saviq> mzanetti, you can build python-upa out of lp:python-upa to fix your input
[12:03] <Saviq> psivaa, ↑ you'll want that too
[12:03] <Saviq> actually /me builds
[12:03]  * thomi -> EOW
[12:06] <Saviq> aaand it rebooted :/
[12:07] <psivaa> Saviq: ohh ok, thanks. that may explain my first run of webbrowser test failures (34/35 failed) thanks
[12:07] <lool> Saviq: yes, that's fixed with python-platform-api update I think
[12:08] <lool> 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] <Saviq> psivaa, will have a fixed package in 5
[12:08] <Saviq> lool, yup, got it
[12:08] <lool> Saviq: if you update python-platform-api, it shoudl work though
[12:08] <Saviq> lool, not released yet
[12:08] <psivaa> Saviq: thanks
[12:09] <lool> Saviq: it's being tested, it's in ubuntu-unity/daily-build PPA
[12:09] <lool> Saviq: see landing spreadsheet
[12:10] <Saviq> lool, right, I don't trust the daily-build ppa ;P
[12:10] <Saviq> lool, if it's not released - it's not there!
[12:10] <lool> Saviq: forgot device in Mir tests; would you add the ones you know?
[12:10] <lool> I'm assuming mostly mako
[12:10] <lool> psivaa: ^
[12:10] <lool> Saviq: haha
[12:10] <lool> Saviq: it's in flight
[12:10] <lool> Saviq: this is just to unblock you and to give you status
[12:11] <lool> Saviq: if it's not in a *PROMOTED IMAGE* it doesn't exist  ;-)
[12:11] <lool> (we have even harder rules  ;-)
[12:11] <Saviq> lool, yup :)
[12:21] <sergiusens> lool, ogra_ can we add upstart into the landing plan? https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1234898
[12:22] <sergiusens> 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] <Saviq> psivaa, here's the fixed package http://people.canonical.com/~msawicz/papi/
[12:22] <lool> sergiusens: Yes
[12:22] <lool> sergiusens: please upload ASAP
[12:22] <ogra_> sergiusens, yeah
[12:22] <psivaa> Saviq: thanks, will update
[12:22] <sergiusens> lool, ogra_ well we need jodh to do that :-)
[12:23] <ogra_> sergiusens, pinged him in -touch
[12:26] <lool> I've pinged him in -release
[12:26] <lool> gah, I'm so late in testing and in sending emails out
[12:26] <sergiusens> wow, I thought this was an off the radar fix :-)
[12:26] <lool> I've had an issue with my laptop's saucy, wasted one hour
[12:26]  * ogra_ still fights with ureadahead today 
[12:26] <ogra_> system-image breaks it :(
[12:27] <lool> ogra_: how so?
[12:27] <ogra_> 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] <ogra_> making it writable mounts  rw fs over the existing /var/lib/ureadahead and the debugfs mount is hidden
[12:29] <lool> ogra_: talk to stgraber about best way to handle this I guess
[12:29] <lool> ogra_: it's not urgent I guess
[12:29] <ogra_> 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] <ogra_> lool, well, i'd like to have a sane boot by reklease ... its one of many small issues
[12:30] <lool> ogra_: can you also track the status of the powerd changes?
[12:30] <lool> ogra_: these are in the spreadsheet for many days now
[12:30] <ogra_> (not as big as the hud dieing all the time and delaying the boot by 20sec indeed)
[12:30] <ogra_> lool, yeah, will land it today ... but probably not for 81
[12:31] <lool> ogra_: can you test the dbus binaries that got uploaded on touch?
[12:31] <lool> ogra_: I've added a row for you on this one
[12:32] <ogra_> lool, i tested it before the upload happened :) but will verify it also works with the package
[12:33] <lool> ogra_: thanks
[12:33] <sil2100> 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] <psivaa> Saviq: mzanetti: no luck yet even with the upa package above (1.1+13.10.20131001.1-0ubuntu2~sbuild1) on maguro.
[12:34] <Saviq> psivaa, do you see stuff happening on screen at all?
[12:34] <Mirv> sil2100: \o/
[12:35] <psivaa> Saviq: that i see, webbrowser is opening but the tests at some stage are failing
[12:35] <Saviq> psivaa, but I mean do the test interact with the browser at all?
[12:36] <Saviq> psivaa, or does it just launch it and sit there
[12:36] <bregma> sil2100, we track all the failures in the Unity7 builds and already have bugs open on the non-environmental ones
[12:37] <mzanetti> 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] <psivaa> Saviq: webbrowser launches, opens the localhost web and then it does not do anything more
[12:37] <psivaa> s/localhost web/web page/
[12:38] <sil2100> bregma: awesome
[12:38] <bregma> it would be more awesome if there were no bugs, but we're doing our best
[12:39] <sil2100> 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] <sil2100> bregma: not sure if that's even because of unity, or maybe an autopilot issue itself
[12:41] <Saviq> psivaa, sounds like your input issue isn't solved indeed
[12:41] <Saviq> psivaa, can you try with the version from daily-build ppa then?
[12:42] <psivaa> Saviq: ack, will do. thanks.
[12:43]  * psivaa -> reboot
[12:58] <Saviq> 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] <lool>  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] <lool> Saviq: great discovery
[12:59] <lool> Saviq: indeed, hud seems quite unhappy
[12:59] <lool> Saviq: they recently added some debug to see what was going on
[13:00] <lool> Saviq: generating the crash file will also slow down the device
[13:00] <Saviq> lool, yup
[13:00] <lool> Saviq: did you find a crash file for hud and an existing bug report?
[13:00] <lool> Saviq: could you raise it with ted/whoever worked on this last?
[13:00] <lool> sergiusens: heya
[13:00] <lool> sergiusens: we're reading up to switch to Mir
[13:00] <Saviq> lool, yeah
[13:00] <lool> sergiusens: not this image, but soon
[13:00] <Saviq> lool, it's always the same crash
[13:01] <Saviq> lool, have made apport ignore it for now..
[13:01] <lool> 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] <ogra_> 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] <lool> sergiusens: that way, people could opt out of it and they keep what they had
[13:01] <sergiusens> lool, .display-mir
[13:01] <ogra_> seems the HUD gets dbus in a weird state
[13:01] <ogra_> when it crashes
[13:01] <lool> sergiusens: if you could prepare that change in a bzr branch, that would be cool
[13:01] <lool> sergiusens: especially since I might be enabling this over the WE
[13:02] <Saviq> ogra_, /me no grok those charts ;)
[13:02] <sergiusens> 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] <ogra_> 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] <Saviq> ogra_, ught
[13:04] <ogra_> Saviq, mhr3_, pete-woods and ted are on it since yesterday
[13:04] <Saviq> good
[13:04] <ogra_> (probably longer)
[13:06] <lool> sergiusens: yes, that's useful; we still need a way to enforce the default, and that ought to be in the image
[13:07] <lool> 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] <fginther> morning
[13:09] <sergiusens> 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] <sergiusens> lool, that said, we can transform it into a property now :-)
[13:10] <lool> :-)
[13:11] <lool> fginther: good mooooornnnnniiiiiiiing!
[13:12] <thostr_1> lool: can you scheudle landing ask line 93 so that we finally get thumbnailing working?
[13:13] <psivaa> Saviq: i'll enter my maguro results at the bottom of the page if that's ok
[13:14] <Saviq> psivaa, well... if you don't get input... kind of beats the purpose
[13:15] <psivaa> Saviq: that's true.. the output is the same, even with upa from the daily ppa: 1.1+13.10.20131004-0ubuntu1
[13:15] <Saviq> lool,
[13:16] <Saviq> ↑↑
[13:16] <lool> thostr_1: ubuntu-ui-toolkit is not going in soon
[13:16] <lool> thostr_1: it's pending fixes
[13:16] <sil2100> lool: are we running ubuntu-keyboard tests now automatically on the image testings?
[13:16] <lool> thostr_1: so it would kind of pollute the view (much like the open URL stuff staged already, blocked on ui-toolkit)
[13:16] <lool> thostr_1: also, Mir going in pretty soon
[13:16] <sil2100> lool: since those are failing badly for the new ubuntu-keyboard right now
[13:16] <lool> thostr_1: so this will be likely be next week
[13:16] <thostr_1> lool: ok
[13:17] <lool> psivaa: do you know about keyboard tests in images?
[13:17] <lool> sil2100: and if you downgrade?
[13:17] <lool> sil2100: doesn't look like we are
[13:17] <mzanetti> Saviq: psivaa: I installed that python-upa thing. Now I get all input twice
[13:18] <lool> plars, doanac: When you guys come up, can we hangout on status of lab infra for Mir tests?
[13:18] <plars> lool: I wondered if it should do about the same thing, but for some reason when I tried your code by itself, it didn't work for me. When I added something running powerd-cli active in the background though, it worked
[13:18] <mzanetti> e.g. dialer_app tests dial 114444 instead of 144
[13:18] <lool> lol
[13:18] <psivaa> lool: hmm no.. iirc plars was doing it, let me see if i can get any information about it
[13:18] <plars> lool: tests are running in the lab now
[13:18] <plars> lool: you just won't see them on the dashboard
[13:18] <lool> mzanetti: it allows typing numbers like 0088112244 faster though
[13:18] <lool> mzanetti: did you reboot?
[13:18] <mzanetti> yeah... especially if you use autopilot as dialing facility
[13:18] <ogra_> yeah, pick your friends by the number :)
[13:19] <mzanetti> lool: yep, did that
[13:19] <lool> plars: \o/
[13:19] <plars> lool: I hope to get the keyboard tests added today - there was a period of time where they wouldn't work, but now they should
[13:19] <lool> plars: what's the dashboard issue?
[13:19] <psivaa> lool: mzanetti: i ran music and webbrowser tests with the upa from ppa but no improvement on maguro
[13:19] <plars> lool: it just doesn't know to add the mir tests
[13:19] <ogra_> it only shows official tests
[13:19] <plars> lool: it's possible I could just name it something different, need to talk to josepht about it in a bit, he's the expert :)
[13:19] <lool> psivaa: ok; thanks for the feedback (that's on Mir IIUC); mzanetti seem to be looking at this
[13:19] <lool> mzanetti: right? ^
[13:20] <mzanetti> lool: yes, on mir
[13:20] <lool> mzanetti, thomi: We seem to have issues with python-upa; it's not fixing the input issue on maguro
[13:20] <psivaa> lool: yea that's with Mir
[13:20] <Saviq> lool, thomi is EOW
[13:20] <sil2100> lool: I'll double check, then I'll do dogfooding and release if all is ok
[13:20] <lool> Saviq: crap
[13:20] <sil2100> lool: since from what I heard it's a known issue
[13:20] <lool> Saviq: does someone else understand his code / changes?
[13:20] <Saviq> lool, dandrader, probably, but he's on a slightly more important thing now
[13:20] <plars> lool: until then: https://jenkins.qa.ubuntu.com/search/?q=saucy-touch_mir will find the raw jobs for you
[13:21] <Saviq> lool, but greyback might, too
[13:21] <lool> plars, doanac: Which one of you could represent lab status best in the standup in 40mn?
[13:21] <Saviq> plars, lool any idea how to run clicks' autopilot tests? we managed to get the suite installed, but can't get autopilot to find the app
[13:21] <lool> plars: good
[13:21] <plars> lool: what kind of lab status are you looking for? If you need someone from the lab, that would be retoaded or rfowler. I'll be happy to be there though
[13:21] <lool> plars: Adding a view >> we plan to switch on Mir later today / this week-end; what does that mean if we create a view?
[13:22] <lool> plars: can we keep SF runs by removing the touch .display-mir thing? (rm before running SF)
[13:22] <lool> plars: Status of running our image AP tests in lab for Mir images
[13:25] <plars> lool: it means we shouldn't bother creating a view :)
[13:25] <fginther> ev, ping
[13:25] <plars> lool: so, despite the issues, we're still going to mir by default now?
[13:26] <fginther> ev, nevermind
[13:27] <plars> lool: so, one thing I guess we could do is make sure the touch_mir jobs are on there, and then reverse the logic when it becomes the default - have the touch_ro jobs remove the .display-mir file, and have the touch_mir jobs just run as normal
[13:27] <lool> plars: we're fighting our way hard to get to Mir as default
[13:27] <lool> plars: but I think we want the two views
[13:28] <lool> plars: to keep the rollback to SF option open for at least some days
[13:28] <lool> sorry for the extra work
[13:28] <lool> plars: So I'll invite you for lab status
[13:28] <plars> lool: what kind of lab status are you looking for?
[13:28] <lool> plars: 15:22 < lool> plars: Status of running our image AP tests in lab for Mir images
[13:29] <plars> ah, ok
[13:29] <plars> missed that one :)
[13:29] <lool> I think you understand this
[13:29] <lool> even if you're not directly tweaking all the knobs
[13:29] <plars> lool: yes, I can certainly talk about that
[13:30] <cjwatson> Huh, we seriously dropped flight mode?
[13:31] <cjwatson> That's a ... surprising decision
[13:31] <lool> cjwatson: the UI for it
[13:31] <lool> cjwatson: but the backend never got done
[13:31] <cjwatson> Yeah, I know, I'm surprised that's not a hard requirement
[13:31] <ogra_> you just need to switch off devices individually
[13:32] <ogra_> the individual settings use the same rfkill commands i think
[13:32] <ogra_> (as flightmode would)
[13:37] <plars> lool: I see where to add a view for it I think, pushing a branch now
[13:37] <lool> psivaa: can you confirm: webbrowser-app tests just output a bunch of broken pipe exceptions after each test, but that's normal, ys?
[13:41] <plars> lool: yes, that's normal - I talked to someone... osomon maybe? about it a while back and they confirmed it was expected
[13:41] <psivaa> lool: i have seen broken pipe exceptions once in a while.. not so every time though.. but that does not normally impact the output result
[13:41] <psivaa> plars beat me :)
[13:42] <sergiusens> lool, is 78 the latest stable image?
[13:42] <lool> sergiusens: that seems correct
[13:42] <sergiusens> lool, thanks
[13:42] <psivaa> lool: re: the puthon-upa test on maguro.. i have not updated the landing task page with my results.. don't have the permission to edit
[13:43] <psivaa> lool: task 81 that is
[13:43] <lool> psivaa: will note them; thanks a lot for testing
[13:43] <psivaa> lool: yw :)
[13:44] <lool> psivaa: Could you update bug #1234956 with your findings?
[13:44] <lool> mzanetti: ^
[13:44] <psivaa> lool: ack, will do
[13:45] <mzanetti> lool: already found it. fixing it
[13:45] <lool> mzanetti: awesome
[13:45] <mzanetti> lool: actually it was swapped with manta screensize
[13:45] <lool> psivaa: ^ new package coming up soon
[13:45] <psivaa> mzanetti: lool: ack
[13:46] <lool> mzanetti: please can you ping me when it's happroved?  I think this should be merged by hand if it's trivial enough diff wise
[13:46] <lool> mzanetti: want to land this yesterday  :-)
[13:46] <lool> sergiusens: how does it work to update kernels?
[13:46] <lool> sergiusens: do we have to rebuild android, or is this picked up at image build time?
[13:47] <sergiusens> lool, I wasn't involved in the re packaging of android; a regular android build pulls in the latest kernel; maybe ogra or xnox decoupled that when doing the packaging
[13:48] <cjwatson> I have an archive-cleanup upload to a source that generates one binary in the touch image, but it only actually changes a -dev binary not in the image
[13:48] <cjwatson> Do I need a landing ask for that?
[13:48] <cjwatson> Specifically http://paste.ubuntu.com/6192290/
[13:50] <lool> cjwatson: no that's good to upload without landing pipeline
[13:51] <lool> cjwatson: wont directly affect the image, might just break builds
[13:51] <lool> cjwatson: but thanks for the heads up
[13:52] <ogra_> lool, the android pakcage build creates the boot.img, on upgrades that gets flashed
[13:52] <ogra_> lool, android pulls in the kernel binary packages
[13:52] <ogra_> during build
[13:53] <sergiusens> ogra_, so it's not decoupled?
[13:53] <ogra_> sergiusens, nope
[13:53] <lool> ogra_: so we do have to rebuild android after each kernel upload
[13:53] <sergiusens> lool, so new kernel means new android build
[13:53] <lool> ok
[13:53] <ogra_> kernel and initrd are fed into the build, out comes a boot.img
[13:53] <lool> that's what I thought
[13:54] <lool> new kernels for AA fixes coming up soon
[13:54] <sergiusens> lool, AA means so many things :-)
[13:54] <ogra_> lool, can you talk to apw, i asked for a missing patch on mako
[13:54] <ogra_> might make sense to have that in the same upload
[13:54] <lool> Mirv, sil2100: Trying to assess time before building an image; what stuff do you guys still have in the pipe for today?
[13:55] <lool> ogra_: so shutdown is broken too
[13:55] <lool> I think we don't want to relesae without shutdown
[13:55] <ogra_> lool, yes
[13:55] <ogra_> oh wait shutdown ... i didnt test that
[13:55] <ogra_> only reboot
[13:56] <lool> I just did
[13:56] <lool> both are affected sadly
[13:56] <lool> bah
[13:56] <ogra_> :(
[13:56] <sil2100> lool: ubuntu-keyboard is coming right up, it got published so it should be in the pocket soon
[13:56] <ogra_> the upstart upload we had had only test fixes
[13:56] <sil2100> Shutdown broken?
[13:56] <ogra_> the only upstart job change i see is the one from sergiusens ... but that only touches start on stanzas
[13:57] <ogra_> sil2100, and reboot
[13:57] <mzanetti> psivaa: lool, Saviq: https://code.launchpad.net/~mzanetti/python-ubuntu-platform-api/fix-resolutions/+merge/189320
[13:57] <Saviq> mzanetti, \o/
[13:58] <sergiusens> ogra_, hmm, yeah; I only did start on
[13:58] <sergiusens> ogra_, lool any estimate on since when it was broken?
[13:58] <lool> == Published webbrowser-app ==
[13:58] <lool> Wont publish gallery-app today; AP regressions + file conflicts
[13:58] <sergiusens> ogra_, afaik rsalveti and plars were discussing this yesterday
[13:58] <ogra_> rsalveti, chanages adbd to stop on runlevel change ... but that also seems to work fine
[13:58] <lool> sergiusens: in the last 2 images I'd say
[13:58] <lool> sergiusens: should be good on #78
[13:58] <ogra_> sergiusens, worked on 78
[13:59] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/20131003.1.changes or http://people.canonical.com/~ogra/touch-image-stats/20131003.2.changes must have the offending change
[13:59] <lool> Saviq: Diff being trivial, could you land https://code.launchpad.net/~mzanetti/python-ubuntu-platform-api/fix-resolutions/+merge/189320 if it takes more than 30mn to get merged?
[13:59] <sergiusens> it indeed works on 78
[14:00] <lool> fginther: if you could bump merging of https://code.launchpad.net/~mzanetti/python-ubuntu-platform-api/fix-resolutions/+merge/189320 to top of queue, much welcome
[14:00] <Saviq> lool, will do
[14:01] <cjwatson> lool: done, thanks
[14:01] <sergiusens> ogra_, lool last time we had this it was ofono holding the shutdown (a fork/daemon miss config in the job)
[14:02] <lool> sergiusens: seems very likely; BTW we just switched dbus to doing this, maybe that's the issue?
[14:02] <lool> xnox: ^
[14:02] <ogra_> sergiusens, well, xnox added a fork, but ot the session dbus ...
[14:02] <fginther> lool, it's builidng
[14:03] <sergiusens> ogra_, lool reboot works on 79 as well
[14:03] <ogra_> but the session dbus should be teared down with the session (theoretically)
[14:03] <ogra_> yay, thanks for testing that
[14:03] <ogra_> boils down to http://people.canonical.com/~ogra/touch-image-stats/20131003.2.changes
[14:03] <sergiusens> ogra_, had that on my manta; I'm upgrading now unless you want me to test something else
[14:03] <ogra_> nah, go ahead
[14:04] <apw> ogra_, yep that will likley slide in with teh AA fixes
[14:05] <ogra_> yay
[14:05] <ogra_> thanks :)
[14:24] <doanac> plars: i'm looking at: http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/revision/41 specifically the call to "powerd-cli active"
[14:24] <doanac> is that what we merged for lool here: http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/revision/40
[14:24] <doanac> just via dbus?
[14:24] <plars> doanac: that's what lool said
[14:24] <plars> doanac: but thomi was saying I needed it still, sure enough I tried it and it worked (lool's patch alone wasn't working for me though)
[14:25] <doanac> plars: okay.
[14:25]  * doanac woke up too late :)
[14:25] <plars> doanac: I also found that you really do have to have it running in the background
[14:25] <doanac> that was going to be another question.
[14:25] <plars> doanac: I didn't believe him at first, because it looked like I could run powerd-cli active and just kill it, and the screen still appears to be on
[14:26] <plars> doanac: but it didn't work still
[14:26] <plars> doanac: I had to leave it running
[14:26] <doanac> works for me.
[14:26] <plars> doanac: so... it works, and thomi agreed it's pretty hairy to unlock the screen programatically right now, but isn't hopeful for a saner solution until post 1.0
[14:27]  * doanac wishes we weren't the ones carrying this code around.
[14:27] <doanac> plars: fginther has a copy of our unlock screen also: lp:~fginther/+junk/autopilot_executer
[14:28] <doanac> does he need our updates?
[14:28] <fginther> doanac, possibly, is this specifically for mir
[14:28] <plars> doanac: he might - fginther yes it's for mir
[14:28] <doanac> yes
[14:29] <plars> fginther: which might be the default soon
[14:29] <plars> fginther: it doesn't work for unity8 though
[14:29] <fginther> plars, doanac, thanks for the heads up
[14:29] <doanac> fginther: the two diffs you'd need are:
[14:29] <doanac> http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/revision/40
[14:29] <doanac> http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/revision/41
[14:30] <fginther> doanac, thanks
[14:30] <doanac> reading your code paid off! :)
[14:30] <plars> fginther: I think Saviq is looking at the unity8/mir autopilot issues
[14:32] <Saviq> plars, fginther, yeah, right now I'm seeing a -fullscreen being passed to unity8 for a reason I can understand
[14:32] <Saviq> it's gone from our tests...
[14:33] <fginther> Saviq, was that a recent change (I saw an MP from veebers regarding that I think last night)
[14:33] <Saviq> fginther, yeah, they removed it
[14:33] <Saviq> fginther, but it still gets passed to unity8 somehow
[14:34] <Saviq> FFFFF
[14:44] <lool> == Building qa stack ==
[14:44] <lool> (python-upa)
[14:44] <lool> (not publishing)
[14:45] <lool> sil2100: shutdown/reboot is fix uploaded
[14:46] <ogra_> well, there is an improvement
[14:46] <ogra_> which i'd like to add
[14:46] <ogra_> just testing it
[14:48] <lool> ogra_: ?
[14:48] <lool> what improvement
[14:48] <ogra_> lool, jodh suggested a slight change to the fix
[14:49] <lool> popey, ogra_: So given I haven't kicked a build yet, it might be results for 81 will show up only late tonight; do you guys plan to be around late this firday?
[14:49] <ogra_> with a better syntax for the upstart job
[14:49] <jdstrand> lool: simple bug fix: may I invoke the lool clause? http://paste.ubuntu.com/6192494/
[14:49] <popey> lool: sure
[14:49] <lool> jdstrand: sorry, nothing more going in right now
[14:49] <ogra_> lool, a bit ... cant predict how long
[14:49]  * jdstrand adds ask
[14:49] <popey> wife is out so friday night is playing night
[14:50] <lool> popey: is that playing at home near the computer, or is that playing outside?  :-)
[14:50] <popey> outside!?!
[14:50] <popey> We don't go... outside..
[14:51] <lool> lol
[14:51] <popey> do we have a slot for migrating core apps to click packages in the build?
[14:51] <lool> popey: BTW because of your G+ weekly Lego building posts, I had to buy like 5 of these Lego star wars set
[14:51] <popey> haha
[14:51] <lool> mounting one every week too
[14:51] <popey> excellent
[14:51] <lool> popey: would you please refrain from posting the next toys though?  thanks
[14:51] <lool> ;-)
[14:51] <popey> ok!
[14:51] <popey> ☻
[14:52] <lool> I've already asked for some mindstorms for my brithday
[14:52] <lool> seriously
[14:52] <lool> becoming a kid again
[14:52] <josepht> lool: awesome!
[14:53] <popey> lool: the click question above was for you btw ☻
[14:54] <lool> popey: we don't have a slot for it, we've discussed it out of band
[14:54] <lool> sergiusens: ^ I think it's a next week thing?
[14:54] <lool> popey: app by app, one by one or so I guess
[14:55] <lool> sergiusens, popey: I think we can tell upstreams to upload their apps to appstore already
[14:55] <lool> manually for now
[14:55] <lool> and setup group permissions
[14:55] <kenvandine> sil2100, are we able to publish partial stacks now?  i see services was published, but it didn't include content-hub
[14:55] <sergiusens> lool, we can start including them now fwiw
[14:55] <sil2100> kenvandine: yes, we're able to do that since a long time! ;D
[14:55] <sergiusens> lool, we just need to consume from jenkins for the builds instead of the store
[14:55] <popey> lool: for core apps do _we_ want to upload them so we can update them?
[14:55] <popey> or the upstream teams?
[14:55] <sil2100> kenvandine: but in the past we were hacking around to do that, but Didier added proper support for that
[14:55] <popey> I don't particularly mind either way
[14:55] <kenvandine> i thought we couldn't publish that way :)
[14:55] <kenvandine> ah
[14:56] <sergiusens> popey, lool I asked yesterday and currently the store only allows one login
[14:56] <sil2100> kenvandine: we do partial-stack-publishing since a few weeks since only certain elements we want to put at once
[14:56] <jdstrand> lool: fyi, click-apparmor ask on line 127
[14:56] <kenvandine> sil2100, great :)
[14:56] <lool> sergiusens: ok, can we coordinate this next week?
[14:56] <popey> it makes sense to me for us to have one login for doing the core apps
[14:56] <lool> sergiusens: want to pay attention to the first one getting through, with AP tests etc.
[14:57] <lool> jdstrand: ok, will review monday
[14:57] <kenvandine> gallery-app needs content-hub to publish, only change in content-hub is a pkgconfig file added which gallery-app now needs
[14:57] <jdstrand> lool: thanks
[14:57]  * kenvandine adds to landing asks
[14:57] <lool> or earlier if I can
[14:57] <lool> kenvandine: is there a dep between the two?
[14:57] <lool> kenvandine: tests were failing for me on gallery-app alone
[14:57] <lool> deps didnt require new content-hub
[14:57] <sergiusens> popey, so one login we control and not the individual devs?
[14:57] <kenvandine> build dep?
[14:58] <kenvandine> lool, it'll build with what's in daily-build ppa, but not against archive
[14:58] <lool> kenvandine: oh sorry, just bdep
[14:58] <lool> right, pkg-config
[14:58] <lool> kenvandine: good to know
[14:58] <sergiusens> lool, I thought dropping letters was already enabled with tests
[14:58] <kenvandine> but the only difference is looking for the pkgconfig file instead of hardcoding
[14:58] <popey> sergiusens: let me get back to you on that after my next call
[14:58] <lool> sergiusens: indeed!
[14:58] <lool> sergiusens: but we do need to flip a switch I guess?
[14:59] <sergiusens> lool, yeah, we do
[15:00] <lool> sil2100, Mirv: Did you guys manage to squeeze in some Mir time this PM?
[15:00] <lool> sil2100, Mirv: How was your experience?  :-)
[15:01] <ogra_> lool, btw, what was the background behind your kernel/android question before ? if you want to test kernels, we have scripts to flash single zImage files etc
[15:02] <Mirv> lool: helo, just receiving evening guests in a moment, but I briefly continued testing it but obviously it's the same as I reported yesterday when I released it, ie. I there are no new commits in trunk.
[15:02] <lool> psivaa: still here?
[15:02] <lool> psivaa: mind testing python-upa in PPA?
[15:02] <psivaa> lool: sure
[15:02] <lool> Mirv: I mean, just in terms of general usefulness of phone with .display-mir enabled
[15:03] <lool> sergiusens: did you get a chance to find a spot in image build to touch .display-mir?
[15:03] <Mirv> sil2100: did you mean to release compiz/nux as well? or ido/qmenumodel? I'm just wondering about the whole stacks.
[15:03] <lool> sergiusens: I might have to land this over the week-end (alone, snif...); I'd rather iron out the change with you before hand
[15:03] <Mirv> lool: well it starts to be good. as I wrote in the chart, it's not quite as smooth as with flinger, but usable and eg. video works so it starts to be quite ok.
[15:03] <sil2100> Mirv: no, I just released indicators an unity
[15:03] <sil2100> *and
[15:03] <lool> Mirv: right
[15:03] <sergiusens> lool, an upstart job?
[15:04] <sergiusens> lool, fastest I can think of
[15:04] <sergiusens> lool, or a hook in lvecd-rootfs
[15:04] <lool> sergiusens: how would we preserve removals?
[15:04] <sergiusens> lool, hooks sounds easier, let me get that
[15:04] <lool> sergiusens: yes, livecd-rootfs is what I had in mind
[15:04] <Mirv> sil2100: yeah, it says indicators stack and 'unity 7', ido/qmenumodel belong to the stack at least, not sure if 'unity 7' meant 'unity stack' (as a whole) or justunity
[15:04] <sergiusens> lool, there's already a create user hook
[15:05] <lool> plars: You got your branch for the view reviewed (pun intended)?
[15:05] <sil2100> Mirv: I guess in case of compiz and nux, I think I can publish that as well
[15:05] <lool> sergiusens: Ok; small preference for livecd-rootfs then
[15:05] <lool> this is about changing the image default
[15:05] <sil2100> Mirv: but for the indicator parts - I wouldn't publish without testing more
[15:06] <sergiusens> lool, I'm prepare an MR and you can review?
[15:06] <ogra_> lool, new upstart still boots ...
[15:06] <Mirv> sil2100: right. I'm just thinking that in a few days we should have the to-be-in-release fixes in, so I guess it's good to have currently available fixes in. not sure what's the ido/qmenumodel changes about, but at least nux seems a good performance fix.
[15:06] <ogra_> lool, what more shoudl i test ?
[15:07] <lool> ogra_: lxc-android-config?
[15:07] <Mirv> lool: but with mir trustworthy AP data is of course needed to evaluate it more fully, and performance should be improved so that it wouldn't feel like a regression.
[15:08] <lool> Mirv: yes; so performance is bad for multiple reasons, one is the number of crashes happening in the background
[15:09] <lool> Mirv: the AP tests came back pretty good in manual testing
[15:09] <lool> Mirv: https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0ApRxJIi-SaMddEdtdWtMaXNkMzYtN2puZ2YxdU9MekE&usp=drive_web#gid=0
[15:09] <ogra_> lool, lxc-android-config is already fine
[15:09] <sil2100> brrr
[15:09] <Mirv> lool: nice!!
[15:09] <sil2100> I hate jenkins, it's so easy to click the wrong thing and get stuff running without actually wanting to :|
[15:10] <Mirv> anyhow, I'm again gone, thanks all for the week
[15:10] <sil2100> Mirv: see you on Monday!
[15:10] <lool> Saviq: did you say someone was chasing the input issues for webbrowser?
[15:10] <Mirv> sil2100: see you!
[15:10] <sil2100> Have a nice weekend ;)
[15:10] <psivaa> mzanetti: lool: with the latest upa tests start to pass (dialer 2/2 pass)
[15:10] <lool> Mirv: bye!
[15:10] <Saviq> lool, dandrader is
[15:10] <lool> Mirv: have a good WE
[15:10] <lool> Saviq: cool
[15:15] <lool> Mirv: and thanks for all the landings today!  :-)
[15:15] <ogra_> lool, i think landing 113 and 114 are the same thing
[15:15] <lool> sil2100: are any indicators still in unapproved?
[15:16] <lool> ogra_: one is upstart and one is lxc-android-config
[15:16] <ogra_> lool, oh, no, thats -file-bridge, not -local-bridge
[15:16] <lool> ogra_: but I guess you tested them together
[15:16] <sil2100> lool: when I last checked, no
[15:16] <sil2100> But let me double-check
[15:16] <ogra_> lool, running here, all fine it seems
[15:16] <sil2100> lool: all clear
[15:16] <lool> ogra_: so lxc-android-config and upstart both OK?
[15:16] <ogra_> yes
[15:17] <lool> ogra_: shutdown and reboot working?
[15:17] <ogra_> one sec, reboot is ...
[15:17]  * ogra_ calls halt and waits 
[15:17] <ogra_> grmbl
[15:17] <lool> ogra_: to test shutdown, best to test the user experience of pressing the power button for 2 secs
[15:17] <mzanetti> psivaa: heh... I used the dialer too for testing
[15:17] <ogra_> halt causes a reboot
[15:17] <lool> or something like that
[15:17] <lool> gah
[15:18] <lool> ogra_: try the user thing
[15:18] <lool> psivaa: cool
[15:18] <lool> psivaa: pushing
[15:18] <lool> == Uploading qa stack ==
[15:19] <lool> (python-upa)
[15:20] <plars> lool: yes, it should be on soon
[15:20] <ogra_> lool, 2sec powerbutton doesnt do anything
[15:20] <ogra_> lool, oh, it does shut down now
[15:20] <psivaa> mzanetti: yea i used dialer to get a quick feedback :).. continuing with the rest
[15:24] <ogra_> lool, so i'm not sure that was a proper sutdown process, but it clearly shuts down the phone to hold the powerbutton for >3sec
[15:26] <lool> sil2100: indicators >> cool
[15:26] <lool> sil2100: and how is keyboard looking?
[15:27] <sil2100> lool: released!
[15:27] <sil2100> lool: the tests were failing before as well, and dogfooding revealed no problems
[15:27] <sil2100> lool: actually, it's in release already
[15:28] <lool> sil2100: cool
[15:35] <lool> just waiting on a couple of publication to release pocket
[15:37] <lool> both going in next publisher run
[15:38] <lool> sil2100: hmm
[15:38] <lool> sil2100: any idea about webbrowser-app changelog in cu2d/results?
[15:39] <lool> sil2100: I've published r367, and there's a r368 upstream, and lots of changes from <= 367 still on the cu2d/results page
[15:41] <sil2100> Let me check that
[15:43] <sil2100> lool: could you paste me the link to the results page you have in mind?
[15:43] <vila> lool: won't be able to attend the HO, got a late reminder that I have conflicting social duties :-}
[15:46] <cjwatson> lool: we're finished Rick's apps list?!
[15:48] <lool> cjwatson: well, that's how it looked like
[15:48] <lool> cjwatson: but eh, still tons of bugs to fix!
[15:48] <lool> cjwatson: I was as surprized as you when I reviewed it  ;-)
[15:48] <ogra_> bugs ?
[15:49] <lool> sil2100: http://people.canonical.com/~platform/cu2d/results
[15:49] <ogra_> there are no bugs ... its all features
[15:51] <sil2100> lool: strange, I think these are leftovers - how did you publish webbrowser-app?
[15:51] <sil2100> lool: and when?
[15:51] <lool> sil2100: I clicked force publication and listed only this package
[15:52] <lool> sil2100: when: 15:58 < lool> == Published webbrowser-app ==
[15:52] <lool> sil2100: I think it's a race
[15:52] <lool> sil2100: I shoudl have rebuilt it before hand to pick up the new rev, retested it, then published
[15:52] <lool> sil2100: but I published an "old" (from some hours earlier) rev, and then changelog merging failed
[15:53] <lool> sil2100: So I guess we need to merge by hand?
[15:53] <lool> sil2100: do you have commit access?
[15:53] <lool> I'm not sure I do
[15:53] <sil2100> I have, but I saw some release commit in trunk
[15:53] <sil2100> Releasing 0.22+13.10.20131004.1-0ubuntu1 (revision 367 from lp:webbrowser-app).
[15:53] <sil2100> It's in trunk, hm
[15:56] <sil2100> lool: I guess that the right thing got released, but cu2d didn't yet pick up the proper changes - let's rebuild that component in that stack and check if it's ok now
[15:56] <sil2100> lool: doing that
[15:56] <lool> cyphermox: how is NM?
[15:56] <lool> cyphermox: would like to kick a build
[15:56] <cyphermox> lool: it's not in daily release yet, I just need to do an upload
[15:57] <lool> sil2100: I had rebiult cu2d immediately after upload actualy
[15:57] <cyphermox> but it would be ready to upload, I think
[15:57] <lool> sil2100: in fact, that might be why!
[15:57] <sil2100> lool: right, the merge wasn't in yet then!
[15:57] <lool> sil2100: I rebuilt because I was showing up as green when some other packages should have it shown as yellow
[15:57] <sil2100> lool: since it usually takes a few minutes for it to get approved + merged
[15:57] <lool> I should have given it more time
[15:57] <lool> right
[15:57] <lool> didn't think of this
[15:57] <lool> bad luck with picking up a rev too
[15:58] <lool> sil2100: thanks for diagnosing this with me  :-)
[15:58] <lool> cyphermox: if you dont mind, let's take it in 82
[15:58] <cyphermox> lool: when is that?
[15:59] <cyphermox> if you can tell me when to upload it would be easiest :)
[15:59] <lool> cyphermox: 81 will build now
[15:59] <lool> can be uploaded in 1h
[15:59] <cyphermox> alright
[15:59] <cyphermox> It'll be ready then, I'll just run it through sbuild one last time in between
[15:59] <sergiusens> popey,  lool, I don't feel confident of starting the switch to click on Monday, can't we start today?
[15:59] <lool> cyphermox: cool; also you want to test the binaries I guess
[15:59] <lool> cyphermox: I can stage it in -proposed if it helps
[16:00] <lool> cyphermox: just let me know
[16:00] <sergiusens> popey, lool they are not being tracked daily, who knows all the issues we will find with autopilot and such
[16:00] <cyphermox> lool: ack
[16:00] <lool> sergiusens: ok, can you switch one or two in #82?
[16:00] <sergiusens> or app armor
[16:00] <lool> sergiusens: but please let's wait for test results for #81 in case something goes horribly wrong
[16:02] <lool> [16:02] <lool> sil2100: joining?
[16:02] <lool> plars: ^
[16:02] <lool> vila: ^
[16:03] <lool> fginther: ^ if you like
[16:03] <fginther> lool, omw
[16:05] <vila> lool: <vila> lool: won't be able to attend the HO, got a late reminder that I have conflicting social duties :-}
[16:05] <vila> lool: /me runs
[16:05] <sergiusens> lool, ack
[16:10] <popey> sergiusens: please
[16:10] <lool> plars: https://launchpad.net/ubuntu/+source/unity8/7.82+13.10.20131004.1-0ubuntu1
[16:14] <plars> lool: https://code.launchpad.net/~saviq/unity8/fix-mir-autopilot/+merge/189350 is the one we are going to need I think for unity8/mir, but it was just proposed a few min. ago so it won't be there yet
[16:14] <plars> Saviq: right? ^
[16:17] <Saviq> plars, that, too
[16:17] <Saviq> plars, it lest you run tests individually
[16:18] <plars> Saviq: thats *exactly* how we run them
[16:18] <Saviq> plars, cool
[16:18] <Saviq> plars, there's still the unblank & stale socket issue
[16:18] <Saviq> plars, but since you're doing that
[16:18] <Saviq> plars, then we should be good
[16:18] <Saviq> plars, greyback is reviewing that branch now - it's already in landing asks along with the maguro fix in python-upa
[16:19] <plars> Saviq: I was looking for the -fullscreen fix actually
[16:19] <plars> Saviq: and saw this from you
[16:19] <Saviq> plars, that -fullscreen one was just the first step
[16:19] <Saviq> plars, there's more trickery involved unfortunately
[16:19] <Saviq> plars, especially with the switching between mir and sf
[16:25] <sil2100> lool, everyone: good job!
[16:25] <lool> yeah!
[16:25]  * lool did a *bad* job of sending the update email this morning
[16:25] <lool> will do a single one for the day
[16:28] <ogra_> lool, also to discourse and G+ ?
[16:28] <lool> discourse?
[16:29] <lool> gosh I'm not using that yet
[16:29] <lool> will try G+
[16:29]  * ogra_ neither
[16:29] <ogra_> dider just links to it from G+
[16:29] <lool> yeah
[16:30] <sergiusens> popey, lets get 3/4 swapped, how about clock, rssreader, weather and filemanager
[16:30] <sergiusens> ?
[16:30] <sergiusens> balloons, plars  ^^
[16:31] <balloons> sergiusens, what about them? :-)
[16:31] <sergiusens> balloons, swapping to click
[16:32] <sergiusens> in the image
[16:32] <balloons> sergiusens, yes everything has click support now
[16:40] <popey> sergiusens: ok clock, calc, weather, file manager pls?
[16:41] <lool> crap, I'm seeing apps twice on my desktop
[16:41] <lool> sorry on the dash of mako
[16:41] <lool> is anyone seeing this?
[16:44] <sergiusens> popey, ok, so replace rss with calc? sounds good
[16:44] <lool> does someone else see the breakage on the home screen?
[16:44] <sergiusens> lool, dup apps was logged by mhall
[16:44] <lool> sergiusens: do you have a bug id?
[16:45] <lool> bummer
[16:45] <sergiusens> lool, hmm, let me re search for it
[16:45] <lool> I hope I dont have to roll an #82 for this
[16:46] <rsalveti> lool: when are we getting a new image? :-)
[16:46] <lool> rsalveti: it's builtr
[16:46] <lool> rsalveti: getting published to s-i
[16:46] <rsalveti> just saw we got tons of changes today
[16:46] <rsalveti> awesome
[16:46] <lool> rsalveti: yeah, lots of bug fixes
[16:46] <lool> rsalveti: trying to get a solid last SF image, with relatively safe changes
[16:46] <rsalveti> the unity8 changelog is a bit scary
[16:47] <rsalveti> right
[16:47] <sergiusens> lool, https://bugs.launchpad.net/ubuntu/+source/unity-lens-applications/+bug/1229827
[16:47] <lool> sergiusens: thanks
[16:48] <sergiusens> lool, fwiw, I saw it with regular apps too
[16:48] <lool> sergiusens: Yeah
[16:54] <lool> sergiusens: this is not actually what I'm seeing
[16:54] <lool> sergiusens: I'm seeing multiple icons
[17:01] <sergiusens> lool, oh, sorry, I thought it was multiple runnings
[17:01] <sergiusens> lool, that was an old bug that thing you see
[17:01] <lool> so where are the other apps coming out?
[17:01] <lool> these are actually new apps that got added
[17:01] <lool> WTF
[17:01] <sergiusens> lool, might be with the move of unity8 to upstart? Might need to figure out how it's generating the icons
[17:01] <lool> sergiusens: there are TWO different calculator apps here
[17:02] <ogra_> lool, LOL
[17:02] <ogra_> HAHAHAHAHA !
[17:02] <ogra_> lool, i fell into the same trap
[17:02] <sergiusens> lool, for a minute I freaked out thinking it might of been me http://people.canonical.com/~ubuntu-archive/click_packages/click_list
[17:02] <sergiusens> but the click list is ok
[17:02] <ogra_> lool, re-flash ... thats all the fake autopilot apps
[17:03] <ogra_> the ap tests pull them in ... it is super confusing
[17:04] <sergiusens> ogra_, that's the potential bug I was telling plars about yesterday
[17:04] <sergiusens> lool, ogra_ I was told that there was no apt-get update in any of the tests
[17:04] <sergiusens> ogra_, oh, fake apps
[17:04] <sergiusens> got it
[17:04] <ogra_> sergiusens, yeah
[17:04] <sergiusens> ogra_, unity does that?
[17:04] <sergiusens> ogra_, it should clean up tbh
[17:04] <lool> ogra_: oh ok
[17:04] <ogra_> just the test apps the ap packages ship along
[17:05] <sergiusens> ogra_, as in the test should clean up after it runs
[17:05] <ogra_> sergiusens, if you uninstall the ap packages they go away
[17:05] <ogra_> at least they did a few weeks ago
[17:05] <ogra_> not sure thats stiull the case :)
[17:06] <sergiusens> ogra_, hmm, the logic to install these desktop files should be in the test itself though
[17:06] <ogra_> well, i didnt research where what comes from after all :)
[17:06] <ogra_> i just re-flashed
[17:07] <ogra_> you trashed your image already when you made it writable for testing
[17:07] <ogra_> so i dont think in that case cleanup is needed ... if it also happens once we can fully do ro testing, thats something different
[17:07] <sergiusens> ogra_, well QA is asking me to support testing with ro images; this needs to be cleaned up first if that's a goal
[17:07] <ogra_> yeah
[17:08] <ogra_> for ro it needs that
[17:08] <lool> so I've freaked out 3 times on today's image being broken already
[17:08] <lool> I'm reflashing now
[17:08] <lool> keeping backup
[17:08]  * ogra_ hands lool a 1l bottle valerian and a beer glas
[17:08] <sergiusens> lool, if you keep backup you have the potential to freak out again!
[17:09] <lool> true  :-)
[17:09] <ogra_> lool, i used 80 on Mir and SF on both devices the whole day ... apart from the endless boot with Mir due to HUD issues it was all fine, dont let people make you panic
[17:09] <lool> ogra_: speaking of #81!
[17:09] <ogra_> oh, is it there already ?
[17:09] <lool> yes!
[17:09] <lool> popey: ^
[17:10] <lool> my brain less so
[17:12] <lool> plars: dashboard going ok?
[17:12] <lool> :-)
[17:14] <popey> kk
[17:15] <plars> lool: was just checking, I would have expected it to roll out at the last hour mark
[17:16] <plars> josepht: any idea? it looks like the qa-dashboard-production jobs ran ok, and the releaseprocess you pointed me at says it should resync and deploy every hour if there's anything new?
[17:17] <josepht> plars: there's still one issue I'm tracking down
[17:17] <plars> josepht: ah, ok
[17:17] <plars> lool: the jobs are running though
[17:18] <plars> I'm going to go grab some lunch while I wait for them to get farther
[17:21] <fginther> lool, would it be possible to remove gallery-app from the daily ppa? it has a broken depenency
[17:23] <lool> fginther: it will be repushed afterwards, but yes
[17:23] <lool> fginther: nuke it if you like
[17:23] <lool> fginther: what's he dep?
[17:23] <fginther> lool, thanks
[17:23] <lool> fginther: hold on, what's the issue?
[17:23] <fginther> lool, one moment
[17:23] <lool> fginther: the file conflict should be fixed in trunk now
[17:24] <fginther> lool, the png file?
[17:24] <fginther> lool, that's the one I'm hitting
[17:24] <fginther> lool dpkg: error processing /var/cache/apt/archives/gallery-app_0.0.67+13.10.20131004.2-0ubuntu1_armhf.deb (--unpack):
[17:24] <fginther>  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
[17:24] <psivaa> lool: Saviq: filled the mir testing spread sheet with maguro results as much as possible.. did not report any new bugs for the failures..
[17:25] <fginther> lool, if it's fixed in trunk, great. However, the package in the ppa is breaking the testrunner revert logic
[17:25] <lool> fginther: that's supposed to be fixed in trunk and uploaded to PPA
[17:26] <fginther> lool, ack, if the ppa is being fixed, I'll wait
[17:26] <lool> fginther: I don't see any gallery-app in PPA right now though
[17:26] <lool> ah sorry wrong one
[17:26] <ogra_> :(
[17:26] <fginther> lool, it's here https://launchpad.net/~ubuntu-unity/+archive/daily-build
[17:26] <ogra_> the dashboard doesnt look so good
[17:26] <lool> fginther: sorry MP didn't land on this
[17:27] <lool> let's nuke it
[17:27] <josepht> plars: http://reports.qa.ubuntu.com/smokeng/saucy/touch_mir/
[17:27] <lool> fginther: I can't though
[17:27] <lool> fginther: can you?
[17:27] <lool> I don't have power to kill it
[17:28] <lool> fginther: can you land https://code.launchpad.net/~mfisch/gallery-app/remove-icon-from-package/+merge/189331 and we upload to PPA?
[17:28] <josepht> lool: ^^
[17:28] <ogra_> seems HUD service is killing us
[17:28] <fginther> lool, I'm working it
[17:28] <ogra_> (on 81)
[17:29] <fginther> lool, I can't delete either :-(
[17:30] <ogra_> oh, and sensorservice too
[17:31] <lool> cjwatson: can you help
[17:31] <lool> cjwatson: we're trying to nuke gallery-app from ppa:ubuntu-unity/daily-build (saucy)
[17:31] <lool> cjwatson: to unbreak the autopilot runs for other packages
[17:31] <Saviq> psivaa-afk, great, thanks
[17:31] <lool> josepht: awesome!
[17:32] <lool> josepht, plars: Great job, thanks!
[17:38] <fginther> mfisch, I disabled the gallery-app tests for a moment until we get the ppa fixed
[17:39] <fginther> cyphermox, robru, kenvandine, can any of you remove gallery-app from https://launchpad.net/~ubuntu-unity/+archive/daily-build/+packages ?
[17:39] <fginther> it's blocking upstream merger until we get the fix to land
[17:40] <lool> popey, ogra_: Can you play with #81 and decide if it's good?  :-)
[17:40] <lool> will wait for test results
[17:40] <lool> fginther: thanks
[17:40] <ogra_> lool, dashbvoard doesnt look so good
[17:40] <popey> lool: am right now.. will let you know
[17:41] <ogra_> sigh ... my USB died on the chromebook
[17:41] <lool> fginther: thanks; will care to land the fix ASAP
[17:41] <lool> plars: who can give back the touch (non-mir) failures?
[17:41] <lool> will go to dinner, then come back
[17:42] <lool> plars: in terms of timezone, would be good if someone could keep an eye for a couple of hours on the test runs on touch
[17:42] <popey> ooh, system settings are centred now?
[17:42] <popey> http://popey.com/~alan/device-2013-10-04-184248.png
[17:44] <ogra_> nice
[17:44] <ogra_> sadly it will still fail in german i guess
[17:44] <popey> So long as it works in French!
[17:45] <popey> ooh!
[17:45] <popey> new wifi dialog
[17:46] <popey> http://popey.com/~alan/device-2013-10-04-184556.png
[17:48] <kenvandine> fginther, just delete the package from the PPA?
[17:48] <fginther> kenvandine, yes please, it has a dependency conflict
[17:49] <fginther> kenvandine, I new one is one the way, but testing was being screwed up by the one in the ppa
[17:49] <kenvandine> fginther, done
[17:49] <fginther> kenvandine, much thanks
[17:49] <kenvandine> np
[17:54] <rsalveti> ogra_: seems unity8 and hud are both killing us
[17:55] <ogra_> yeah
[17:55] <ogra_> well, unity8 is probably just fallout of the HUD
[17:55] <rsalveti> yeah
[17:55] <rsalveti> can't we just kill hud?
[17:55] <rsalveti> it's broken anyway haha
[17:56] <rsalveti> and helps us getting a better boot speed
[17:56] <rsalveti> I can only see good things happening after killing it
[17:56] <rsalveti> :-)
[17:56] <plars> lool: it looks like a lot of stuff is having problems today :(
[17:56] <plars> looking
[17:57] <ogra_> rsalveti, try and kill it for a test ... your reboots will just fly :)
[17:58] <rsalveti> ogra_: yeah, amazing
[17:58] <ogra_> and Mir makes it a lot worse
[17:58] <plars> lool: unity8 cpu hogging is back
[18:00] <ogra_> plars, i put my bets on it just being fallout of the hud service
[18:00] <lool> plars: on Mir?
[18:01] <ogra_> lool, on 81
[18:01] <ogra_> see the dashboard
[18:01] <lool> but on SF or in Mir?
[18:01] <ogra_> but siot down before
[18:01] <plars> lool: no, sf
[18:01] <lool> Saviq: ^
[18:02] <Saviq> plars, lool, we're on *some* of those
[18:04] <lool> Saviq: so another SF build tonight with unity8 CPU hogging fix?
[18:04] <lool> indeed, unity8 is at 50% CPU here
[18:04] <Saviq> lool, no, not that *on* those
[18:04] <lool> Actually it's all the time
[18:05] <Saviq> lool, straight in image 81?
[18:06] <lool> Saviq: it's broke in #81
[18:11] <lool> ogra_: so many tests are failing on settle
[18:11] <ogra_> lool, yeah, the hud, unity and sensorservice
[18:11] <ogra_> the last one is mako specific
[18:11] <rsalveti> might be connected though
[18:11] <lool> Saviq: unity8.log is quiet
[18:12] <rsalveti> my device is hot here
[18:12] <rsalveti> haha
[18:12] <lool> Saviq: strace is doing tons of futex()
[18:12] <lool> [pid  2091] recv(57, "\2\0\0\0debug.egl.swapinterval\0\0\0\0\0\0"..., 128, 0) = 128
[18:12] <sergiusens> fginther, hey, can you check this for me? http://91.189.93.70:8080/job/generic-mediumtests/684/?
[18:12] <ogra_> rsalveti, well, hud and unity are hogging maguro as well ... but sensorservice is mako
[18:13] <popey> lool: 81 looks good to me so far
[18:13]  * popey is popping out for 10 mins
[18:13] <rsalveti> lool: that's because it's rendering all the time
[18:13] <lool> popey: we have an important CPU hogging issue with it
[18:14] <popey> unity8 and sf eating some here
[18:14] <popey>  2415 phablet   20   0  394m 151m  65m S  46.9  8.1  20:09.08 unity8
[18:14] <popey>  2400 system    20   0  144m 119m 116m S  14.0  6.4   5:01.04 surfaceflinger
[18:14] <lool> Saviq: I can offer to rollback to previous unity8
[18:15] <plars> lool, Saviq: those indicator tests are still failing in unity also
[18:18] <fginther> sergiusens, I don't see anything obviously wrong, I can check back after I get some other things fixed
[18:18] <ogra_> bah
[18:18] <ogra_> my phone hangs
[18:19] <ogra_> UI completely stalled
[18:19] <sergiusens> fginther, talking to the dev, he's looking; what's odd is that I didn't change anything at all that could be picked up by this
[18:20] <ogra_> and unity8 at 100% CPU in adb
[18:20] <fginther> sergiusens, right and I saw that other MPs passed recently, might be a dependency changed
[18:20] <ogra_> hey, but at least rebooting works
[18:23] <ogra_> oh man, this is really bad ...
[18:24] <ogra_> scrolling in the G+ app starts when my finger already reached the edge of the display
[18:24] <ogra_> (and there is no unity8 heavily hogging the CPU at this moment, i have top running alongside)
[18:25]  * ogra_ switches to Mir 
[18:27] <rsalveti> ogra_: yay, reboot is indeed working :-)
[18:27] <ogra_> bah, not a bit better in Mir
[18:28] <ogra_> i see unity constantly eating ~25% ...
[18:28] <plars> maliit-server and hud-service still seem to always crash under mir
[18:28] <ogra_> but that doesnt seem to spike or anything when the UI is unresponsive
[18:29] <ogra_> oh, heh, probably because my adb session died
[18:29] <ogra_> having the cursor blink in the middle of the top output is a good indicator i guess :P
[18:30] <ogra_> input is super jumpy in Mir
[18:30] <ogra_> (on maguro that is)
[18:31] <ogra_> bah
[18:31] <ogra_> and the Ui died again
[18:31] <popey> mmmm toasty phone
[18:31] <ogra_> yeah, here too
[18:31] <ogra_> unity is at 107.2% CPU !
[18:32] <ogra_> it is breeding a new core or so i guess ...
[18:33]  * ogra_ notes that upstart seems to very busy as well 
[18:33] <ogra_> the session init constantly eats about 10%
[18:37] <fginther> bfiller, is anyone around who can review this? https://code.launchpad.net/~mfisch/gallery-app/remove-icon-from-package/+merge/189331
[18:37] <bfiller> fginther: I can
[18:38] <fginther> bfiller, thanks
[18:45] <lool> plars: I think these were passing in manual testing though
[18:48] <plars> lool: those crashes are happening in tests like install, and default - nothing that specifically targets them
[18:49] <ogra_> lool, hud doesnt work at all on Mir for me
[18:49] <lool> ogra_: could you file this against hud?
[18:49] <lool> ogra_: they have been tracking a bunch of hud issues lately
[18:49] <ogra_> it crashes on boot and tears dbus into a broken state for about 20sec
[18:49] <ogra_> lool, yes, it is filed since two days
[18:51] <bfiller> fginther: approved
[18:52] <fginther> balloons, thanks again
[18:53] <cjwatson> lool: still need help?
[18:55] <cjwatson> lool: looks like you got it sorted.  I don't have any relevant superpowers FWIW
[18:56] <ogra_> yeah, thats what clark kent claims too
[18:56]  * cjwatson quickly puts his glasses on
[18:59] <lool> cjwatson: It's still broken there, but we delisted it from the AP tests to run, so not a top issue anymore
[19:01] <cjwatson> lool: gallery-app isn't shown in https://launchpad.net/~ubuntu-unity/+archive/daily-build/+packages any more, and Ken said above that he'd deleted it ...
[19:03] <lool> ah great
[19:04] <lool> had missed that
[19:06] <lool> ogra_: did you confirm the size was large enough on maguro?
[19:07] <ogra_> lool, we use loop images, the size is set yo 2G for the system one and we use 57% according to stephane
[19:07] <ogra_> so 40M shouldnt do any harm
[19:07] <lool> popey, ogra_: So I'm obviously not thinking of promoting #81, you guys will be in bed by the time we get a #82; if you want to give it a run over the week-end and say that it's good, that's helpful, but eh it's week-end and I guess you need to recharge
[19:08] <lool> ogra_: ok
[19:08] <ogra_> lool, i can test tomorrow no issue with that
[19:08] <ogra_> i dont want to keep 81 :)
[19:08] <ogra_> (and i wont go backwards)
[19:09] <popey> lool: how late is late?
[19:09] <popey> lool: happy to hang around to test 82
[19:11] <lool> I am testing the reverted .debs, then need to uploaded reverted sources
[19:11] <lool> so guesstimate is image in 2 hours
[19:11] <lool> win 77
[19:12] <kenvandine> 77... wow :)
[19:13] <lool> 110 channels actually  ;-)
[19:13] <lool> but fortunately that's less than before
[19:13] <lool> of course I read every line on all of them
[19:16] <seb128> lol, if anyone wonders why lool doesn't get anything done.. ;-)
[19:16]  * seb128 hides
[19:16] <seb128> (sorry, it's friday right?)
[19:30] <kenvandine> ah, friday trolling, i don't think we've had much of that this cycle
[19:31] <lool> cjwatson: if you're around and you dont mind, would you bump prio of https://launchpad.net/ubuntu/+source/unity-notifications/0.1.1+13.10.20131004.2-0ubuntu1/+build/5076308 and https://launchpad.net/ubuntu/+source/unity8/7.82+13.10.20131004.2-0ubuntu1/+build/5076299 ?
[19:31] <lool> both start in 20+mn
[19:32] <lool> seb128: you're right, I'll remember that and be more careful next time you need to land something!  hint hint
[19:32] <lool> seb128: maybe you need a special process
[19:32] <lool> :-P
[19:35] <seb128> lool, oh, you missed you shot, settings are perfect, I don't need any landing anymore, so that's ok
[19:35] <seb128> (if only that was true...)
[19:37] <ogra_> *crunch* *crunch* *crunch*
[19:37] <ogra_> (that's my popcorn ^)
[19:38]  * lool goes testing settings and reporting RC bugs
[19:40] <seb128> doh
[19:40]  * seb128 sends chocolates to lool
[19:41]  * lool has an allergy to traces of nuts and chokes
[19:41] <seb128> can't win :-(
[19:42] <seb128> lool, btw you should be enjoying your w.e!
[19:42] <lool> cjwatson: and https://launchpad.net/ubuntu/+source/indicator-network/0.5.1+13.10.20131004.1-0ubuntu1/+build/5076327
[19:42]  * seb128 is calling a day/week
[19:42] <lool> ok; I'll be back in a few, when the builds are done
[19:42] <seb128> have a good w.e everyone!
[19:42] <lool> transition to release pocket etc.
[19:42] <lool> seb128: have a good week-end
[19:43] <seb128> thanks, you too!
[19:45]  * retoaded announces: 15 minutes until the jenkins instance on psoglav (aka s-jenkins) is put into "Prepare th shutdown" mode.
[19:45] <lool> oh right
[19:45] <lool> that's tonight
[19:46] <lool> of course!
[19:46] <retoaded> s/th/to
[19:46] <lool> but it's all good
[19:46] <lool> retoaded: is it the one driving image testing?
[19:47] <retoaded> lool, some of it. Some are driven by magners-orchestra. s-jenkins is more merge proposal
[19:47] <lool> apparently image testing isn't listed there
[19:47] <lool> we will see I guess  :-)
[19:49] <retoaded> lool, if everything goes well, it won't be down very long but it will be coming back up on a different IP.
[19:50] <retoaded> when it comes back up it will be http://10.97.2.26:8080
[19:54] <fginther> can someone confirm that lp does not publish all binary packages from a source package simultaneously inside a ppa?
[19:54] <sergiusens> cjwatson, from what retoaded is saying, you might want to update the cron to pull from the new instance
[19:54] <sergiusens> fginther, confirming
[19:54] <sergiusens> fginther, that's why we had all those checks in the ppa_copy script
[19:55] <fginther> sergiusens, know of any good way to workaround this with apt-get?
[19:55] <fginther> sergiusens, :-)
[19:57] <lool> retoaded: ok thanks
[19:57] <sergiusens> fginther, hmmm, but at the apt-get level you should be fine, I thought the bin was copied first and the Packages.gz updated
[19:57] <sergiusens> fginther, are you checking for one arch and then pulling for another?
[19:57] <sergiusens> fginther, oh, mirror issues is what you may see
[19:59] <fginther> sergiusens, so apt is pulling in an "all" package when then depends on an armhf package, the 'all' package appears to be available before the 'armhf'
[19:59] <fginther> sergiusens, both the all and armhf packages have the same source package
[20:02] <sergiusens> fginther, so the all depends on the bin and the bin isn't there yet? And all this in apt?
[20:02] <fginther> yes
[20:02] <sergiusens> fginther, btw https://code.launchpad.net/~sergiusens/ubuntu-weather-app/click-in/+merge/189381 is failing too
[20:02] <sergiusens> and I can't reapprove
[20:02] <fginther> sergiusens, I can
[20:02] <sergiusens> fginther, ty
[20:03] <sergiusens> fginther, so wrt to your problem, I'm thinking you want stgraber
[20:03] <fginther> sergiusens, is there a technical limitation to flashing two devices simultaneously (assuming you had a local copy already downloaded)?
[20:03] <sergiusens> fginther, I can't think of solving it just at the apt level
[20:04] <fginther> sergiusens, thanks for the help
[20:04] <sergiusens> fginther, no, there shouldn't they are on different serial interfaces
[20:04] <sergiusens> fginther, and locks are in place for the downloads so they don't step on each other
[20:05] <fginther> sergiusens, so this can be done now?
[20:05] <fginther> sergiusens, in our flash job, we have a file lock in place to serialize phablet-flash
[20:10] <sergiusens> fginther, do you have to devices to test this just in case? The last code injected for this did work and I'm almost sure doanac or plars are flashing in parallel
[20:10] <sergiusens> they came up with the feature in phablet-flash
[20:10] <lool> sergiusens: BTW, did you manage to prepare a .display-mir branch?  I think Saviq will be around tomorrow to land Mir fixes and then we can enable it
[20:10] <lool> sergiusens: I'm also thinking we want to keep a copy of the last good SF images somewhere; would you know of a place to do so?
[20:10] <lool> sergiusens: otherwise I can check with stgraber
[20:11] <fginther> sergiusens, I don't have two devices, I'll wait for doanac and plars to chime in. When I asked earlier, I understand they don't do it in parallel
[20:11] <sergiusens> lool, wrt ricmm said it wasn't ready yet
[20:11] <doanac> fginther: i was confused earlier about what you were asking. I think we allow phablet-flash to be called concurrently.
[20:12] <doanac> so we run different jobs concurrently (we just don't parrellize a single job)
[20:14] <fginther> doanac, ahh, that's good to know. I want to flash 8 devices at once, sounds like that safe to do
[20:14] <fginther> or some combination of overlapping flashings
[20:15] <lool> sergiusens: where was that?
[20:16] <sergiusens> lool, our dailies
[20:16] <lool> sergiusens: I can't connect your points to mine
[20:16] <lool> it's like we're discussing something else
[20:16] <plars> fginther: yeah, you should be safe now - at one time it was not safe to overlap them but it is now
[20:17] <doanac> fginther: not sure if we've done that many before. I know plars used to have to do "flocks" around fastboot commands back at linaro for android devices
[20:17] <lool> sergiusens: currently I'm holding up mir as default until we get a couple of fixes, input related
[20:17] <lool> or focus related
[20:17] <lool> focus as in notification focus
[20:17] <lool> not bringing apps to the front
[20:17] <sergiusens> lool, let me circle back and get that MR ready
[20:17] <lool> sergiusens: but AIUI, Saviq will be fixing these two tomorrow
[20:17] <lool> and then I'll switch
[20:19] <lool> sergiusens: thanks for preparing this BTW
[20:19] <lool> sergiusens: do you have a place for backups of the images?
[20:20] <cjwatson> lool: sorry, by the time I got to this they were all basically about to build
[20:20] <cjwatson> sergiusens: sorry, which cron job is that?
[20:20] <sergiusens> cjwatson, did click-copy one
[20:20] <lool> cjwatson: np; thanks for checking
[20:20] <cjwatson> sergiusens: right, that's pulling automatically from your branch anyway ...
[20:21] <sergiusens> cjwatson, but the IPs are set as arguments
[20:21] <cjwatson> sergiusens: oh, right
[20:21] <cjwatson> 11 0,6,12,18 * * *      bzr up -q ~/click_ready && ~/click_ready/click_copy.py https://jenkins.qa.ubuntu.com ~/public_html/click_packages
[20:21] <cjwatson> tell me what that should be
[20:22] <cjwatson> fginther: is that all/armhf thing in a PPA?
[20:22] <sergiusens> cjwatson, starting later tonight according to retoaded it should be http://10.97.2.26:8080
[20:23] <cjwatson> sergiusens: could you ask IS for a firewall hole from snakefruit to that?
[20:23] <cjwatson> sergiusens: that might take a while though - would it be horrible for the cron job just not to work for a while?
[20:23] <popey> lool: how far back in terms of backups?
[20:24] <sergiusens> retoaded, any chance of keeping the IP?
[20:24] <cjwatson> lool: well, I bumped two of those a bit, the other is building
[20:24] <sergiusens> cjwatson, you bring up a good point, lots of things will break, not just our stuff
[20:24] <lool> cjwatson: thanks
[20:25] <retoaded> sergiusens, that would be complicated as the new server for s-jenkins is also configured for and already running as the secondary BIND server.
[20:25] <sergiusens> retoaded, ok, did you replicate all the firewall rules?
[20:25] <retoaded> I will set up a page on psoglav to redirect people to the new server once it is up and running.
[20:25] <sergiusens> retoaded, since cjwatson asked me to do that; but it's not the only stuff that will break
[20:26] <retoaded> The firewall rules are (supposedly) all set up for the SNAT address coming out of m-o.
[20:26] <sergiusens> retoaded, oem talks to the plum server (forgot the full name)
[20:26] <cjwatson> retoaded: snakefruit can't talk to 10.97.2.26:8080
[20:26] <cjwatson> fginther: oh, yeah, you said it was a PPA.  This happens because architecture: all binaries are always built by an i386 builder.  The only way to avoid arch skew is to build in a staging PPA and copy over when it's done (much like saucy-proposed vs. saucy)
[20:27] <retoaded> cjwatson, that would be an incoming rule then. hmmmm.
[20:27] <sergiusens> cjwatson, btw, is snakefruit a precise machine and does it have python-oauth installed?
[20:27] <retoaded> cjwatson, but there isn't anything running to asnwer on http://10.97.2.26:8080 yet.
[20:28] <retoaded> s/asnwer/answer
[20:28] <cjwatson> sergiusens: yes and yes
[20:28] <sergiusens> retoaded, can you setup  a netcat or something for cjwatson to test?
[20:28] <sergiusens> cjwatson, that's great, make oauth implementation easier :-)
[20:29] <retoaded> sergiusens, give the nc string you want me to set up
[20:30] <retoaded> sergiusens, will something like nc -l 10.97.2.26 8080 work for you needs?
[20:30] <sergiusens> retoaded, more of a cjwatson thing to test, I don't have access to snakefruit as far as I know
[20:31] <retoaded> cjwatson, will nc -l 10.97.2.26 8080 suit your needs?
[20:31] <cjwatson> retoaded: sounds right
[20:31] <retoaded> cjwatson, it's running
[20:32] <cjwatson> retoaded: you seeing anything on its output?
[20:32] <retoaded> cjwatson, not yet
[20:33] <cjwatson> telnet: Unable to connect to remote host: Connection timed out
[20:33] <cjwatson> so that's a no
[20:33] <retoaded> hmmmm
[20:33] <cjwatson> lool: those are all built, some probably still awaiting publication
[20:37] <sergiusens> fginther, I'm still confused about this failure... http://91.189.93.70:8080/job/generic-mediumtests/687/console
[20:38] <plars> balloons: weather-app tests are all failing on both devices
[20:39] <balloons> plars, yes the changes have wreaked havoc on weather
[20:39] <plars> balloons: so it wasn't from the new weather-app version?
[20:40] <sergiusens> plars, balloons interesting, my MR is also failing...
[20:40] <sergiusens> fginther, nvm, I think it will be solved for us
[20:40] <sergiusens> plars, is calculator also breaking?
[20:41] <plars> sergiusens: yes http://reports.qa.ubuntu.com/smokeng/saucy/touch_ro/maguro/81:20131004:20131003.2/4556/ubuntu-calculator-app-autopilot/
[20:41] <plars> sergiusens: 9 failures on both phones
[20:41] <plars> (7 of which are ap tests)
[20:42] <sergiusens> plars, ok, that's sort of good news for me
[20:42] <sergiusens> plars, but that just means something outside of the tests has changed
[20:42] <sergiusens> plars, since my MRs are basically like adding READMEs and they fail
[20:43] <sergiusens> plars, was checking previous MRs and they seem solid
[20:44] <balloons> sergiusens, which MR? and no, it's not interesting trust me, heh
[20:44]  * balloons notes that looks like swiss cheese: http://reports.qa.ubuntu.com/smokeng/saucy/touch_ro/maguro/81:20131004:20131003.2/4556/
[20:44]  * lool whistles
[20:44] <lool> balloons: system-settle raised the unity8 CPU bug
[20:44] <plars> balloons: note that a lot of the failures across the tests are system-settle
[20:45] <plars> right
[20:45] <plars> but there's plenty of random breakage all over the place too
[20:45] <balloons> yes, so there is going to be breakage as francis migrates us to merging with the upstream sdk versions
[20:45] <plars> lool: I'm retrying where it makes sense to do so, but I think some of it just needs to be resolved and/or backed out to make sense of it. it's quite a mess right now
[20:46] <sergiusens> balloons, https://code.launchpad.net/~sergiusens/ubuntu-calculator-app/clicker/+merge/189392  https://code.launchpad.net/~sergiusens/ubuntu-weather-app/click-in/+merge/189381
[20:47] <plars> lool: lots of stuff on mir is taking forever and timing out
[20:47] <balloons> sergiusens, welcome to core apps merging my friend :-)
[20:47] <plars> lool: the click_image tests just timed out there
[20:47] <plars> lool: after 30 min. it timed out, for comparison, I would have expected it to take more like 1 min
[20:47] <sergiusens> balloons, if it were previous time like MWC and had more control I would of used the expedite system that everyone loved
[20:48] <sergiusens> too much of a gestapo (or nsa) now to do that :-P
[20:48] <lool> plars: I'll upload another image in a few
[20:48]  * balloons loses it @ sergiusens 
[20:48] <balloons> too funny!
[20:49] <lool> plars: this sounds quite in line with unity8 pegging the CPU
[20:51] <sergiusens> :-)
[20:53] <lool> MWC?
[20:54] <balloons> lool, mobile world congress
[20:55] <sergiusens> lool, that^
[20:55] <sergiusens> lool, https://code.launchpad.net/~sergiusens/livecd-rootfs/mir_default/+merge/189429
[20:56] <lool> I wonder who the gestapo is then
[20:56] <lool> sergiusens: thanks
[21:05] <balloons> fginther, are you testing the upstream version of UITK emulator too?
[21:05] <balloons> fginther, I mean with the apps, are they running the latest version of the emulator? I'm seeing emulator bugs in these runs
[21:07] <fginther> balloons, only the generic-mediumtests-sdk used the uitk emulator, the main generic-mediumtests job has that bug I mentioned
[21:07] <balloons> fginther, sorry, I blame the lateness of the hour on friday, but I'm missing what you are saying :-)
[21:08] <balloons> fginther, ohh wait, got it.. ok, so that's a yes :-)
[21:08] <fginther> balloons, there are too many things in flight to give a strait yes/no to any question :-)
[21:08] <balloons> fginther, hahahahah..
[21:14] <lool> == building an image ==
[21:14] <lool> ogra_, popey: ETA 45 mn or so, but since the results will take a while, I likely wont promote before tomorrow
[21:15] <popey> lool: just started watching a film, so will wait and test tonight
[21:15] <lool> ok thanks
[21:15] <balloons> offical build number is?
[21:15] <lool> I couldn't test all pending binaries due to recurring fs issues   :-(
[21:16] <lool> balloons: latest image is #81, current build is #82, last stable is #78
[21:16] <balloons> current build is what I was after.. I didn't know if it was 81 or 82 :-)
[22:00] <dobey> sergiusens: uhm. i just happened upon bug #1111598 which was marked "Fix committed" a month ago, but does not seem to actually be fixed. the keyboard stays around still
[22:03] <plars> lool: just to make you aware, I'm having trouble with the mako in the lab running the mir tests - it isn't responding, but is visible on adb
[22:04] <lool> plars: can you reflash it?
[22:04] <lool> image is being imported right now
[22:08] <lool> retoaded: is jenkins conversion done?
[22:09] <lool> retoaded: image import needs the custom tarballs from there apparently
[22:09] <retoaded> lool, the sync is still ongoing, should be done shortly.
[22:09] <lool> ok
[22:10] <lool> stéphane tells me there's a timeout anyway
[22:18] <lool> ogra_, popey: Image up; took a while due to langpacks
[22:18] <popey> kk
[22:21] <plars> lool: I can't do anything with it from here
[22:22] <lool> plars: adb reboot + fastboot boot <recovery.img>?
[22:22] <lool> plars: do we have spares?
[22:22] <plars> lool: no, reboot doesn't ever come back
[22:22] <plars> lool: checking on spares
[22:22] <lool> the good news is that CPU pegging is gone
[22:23] <lool> online music, wow
[22:23] <plars> \o/
[22:23] <lool> and it works!
[22:24] <lool> wow the goto accounts link from click actually works
[22:26] <lool> video playback in browser is audio only, green overlay
[22:26] <lool> but tha'ts better than it ws
[22:26] <lool> cool
[22:28] <plars> lool: ok, I can work around it
[22:28] <plars> one sec
[22:39] <popey> lool: ogra_ 82 seems good here
[22:39] <popey> on mako
[22:43] <sergiusens> retoaded, are you going to deal with the firewall rule as well?
[22:44] <sergiusens> dobey, osk not dismissing is a bug that comes and goes
[22:45] <sergiusens> dobey, however I don't recall marking that bug fix committed in september
[22:46] <sergiusens> dobey, oh, I was just marking the project fix committed for it to be consistent with the ubuntu package
[22:47] <lool> popey: cool
[22:48] <lool> popey: will wait for ogra's feedback and test results, likely tomorrow
[22:48] <lool> and then perhaps promote
[22:51] <popey> ok, groovy
[22:58] <Saviq> plars, the indicators tests are gone in trunk already
[23:01] <cjwatson> lool: Can I upload http://paste.ubuntu.com/6194378/ ?  In touch images but this change doesn't really affect them.
[23:12] <retoaded> sergiusens, I have an RT in with IS on the FW rule. I tried to get vanguard to work it but apparently they EOD'd/EOW'd without even responding to me.
[23:13] <cjwatson> From my POV they EODed just before you asked
[23:14] <cjwatson> 21:34 -!- fo0bar changed the topic of #is to: Vanguard: None at present; please use RT or emergency line || Known Issues: ø || Emergency number: +44 207 630 2499 || RT: rt@admin.canonical.com ||  http://status.admin.canonical.com/
[23:14] <cjwatson> 21:35 <retoaded> fo0bar, there is currently a fw rule that allows snakefruit to connect to a machine in the magners lab; specifically 10.97.2.10:8080, can a rule be added to also allow it to connect to 10.97.2.26:8080?
[23:15] <retoaded> cjwatson, it may have been a network issue on the server. see if you can hit http://10.97.0.26:8080 from snakefruit.
[23:15] <retoaded> btw, the new jenkins is up and running and can be connected to through that URL
[23:19] <cjwatson> retoaded: Afraid not
[23:21] <cjwatson> FYI I've arranged for proposed-migration to know about the specific set of things that ubuntu-touch currently depends on from the coreapps PPA
[23:21] <cjwatson> I'll try to track that as they diminish by way of conversion to click packages
[23:22] <cjwatson> But this should mean that proposed-migration will prevent the addition of any more out-of-archive dependencies without us explicitly educating it about them, which should be an improvement
[23:35] <retoaded> cjwatson, ack
[23:35] <rsalveti> lool: green overlay when playing videos will be fixed once jim fixes the software rendering path in gst, which is the same issue that's causing an invalid thumbnail