[07:27] <elfy> pitti: I'm using something as ps3 media server - worked fine in vivid, works fine in wily if I boot with upstart, but if I boot with systemd - reboot/shutdown hangs for exactly 90s - what can I do to troubleshoot this now I've found what it is?
[07:27] <elfy> the something is serviio - uses java 8
[07:27] <pitti> elfy: I assume you mean "works fine in vivid" == if you boot with upstart?
[07:28] <elfy> in vivid it works fine with either upstart or systemd
[07:28] <pitti> elfy: /usr/share/doc/systemd/README.Debian "Debugging boot/shutdown problems"
[07:28] <pitti> elfy: i. e. enable debug shell, switch to it while shutdown hangs, systemctl list-jobs will show you the running job(s); then you can inspect with systemctl status, journalctl, poke processes, etc.
[07:28] <elfy> ok - I'll have a look then - thanks :)
[07:29] <pitti> elfy: 90s is the standard systemd timeout for start/stop commands
[07:29] <elfy> pitti: ok ty
[13:36] <oSoMoN_> davmor2, hey, have you had a chance to check silo 32 ?
[13:52] <alesage> oSoMoN__, some latency here as we're sprinting
[13:54] <oSoMoN__> alesage, thanks! I understand there is some latency due to the sprint, I just wanted to make sure it doesn’t fall off the radar
[13:54] <alesage> oSoMoN, it never hurts to ping :)
[14:02] <davmor2> oSoMoN: yeap first one today was just in a meeting
[14:02] <oSoMoN> davmor2, awesome, thanks!
[14:02] <oSoMoN> how is it going in Orlando btw?
[14:14] <davmor2> oSoMoN: slowly but it is going.
[15:04] <elfy> pitti: seems2 things are still running, session-c2.scope and sys-subsystem-=net-device-virbr0-nic.device, no idea what either of those have got to do with this ps3 server though - and without that (and it's java tasks) it reboots as expected
[15:10] <pitti> elfy: the virbr0 thingy sounds relevant, something from libvirt? I think I faintly remember some similar reports during vivid, but they were pretty much completely fixed with bug 1438612
[15:10] <pitti> elfy: if you can reproduce that in a VM somehow, I'd highly appreciate a bug report
[15:11] <pitti> elfy: if you manually shutdown the virbr0 device in the debug shell, does shutdown resume normally then?
[15:11] <elfy> not sure pitti
[15:11] <elfy> what I'm right in the middle of is removing qemu as I don't use it much anyway
[15:11] <pitti> qemu?
[15:12] <pitti> that shouldn't affect shutdown at all; libvirt surely would
[15:12] <elfy> kvm or whatever - that I believe is where libvirt got installed at least
[15:14] <balloons> breaking things again I see elfy
[15:14] <elfy> balloons: there is a Y in the day :)
[15:15] <balloons> if you are up for it, the live q and a in 45 mins will have some QA folks in it.. I'd love for you to grill them :-)
[15:17] <ianorlyn> although if you end up dual booting with qemu I might need to find a way to manually eject the disk as it won't eject the install media if it is not the first install on the vm if you try to disconnect the cd in virt manager for me but I think that is basically virt-manager doesn't expect dual boot vms
[15:23] <elfy> pitti: so without libvirt - it was just session-c2.scope running - seemingly no way to stop that
[15:23] <pitti> elfy: that's your user session; perhaps something is hung there?
[15:23] <elfy> anyway I'll see if I can see it in a vm install and use that
[15:23] <pitti> elfy: loginctl session-status c2
[15:24] <pitti> elfy: that shows you the processes that are running in that session
[15:24] <pitti> elfy: kill them one by one to find the culprit?
[15:24] <elfy> pitti: if I don't go to vt9 with the debug shell - but just let it do it'sd thing - and then ctrl+al+del a bunch of times - it tells me alsa is trying to start
[15:24] <elfy> but - as I said going to set up a vm the same as this and hope that fails too - this rebooting in 90s is driving me nuts :p
[15:25] <pitti> elfy: yes, please let's debug this; you can be sure that affects more people :)
[15:25] <elfy> balloons: where live session- and is there an IRC channel to grill people
[15:25] <pitti> elfy: but I haven't gotten a report about hanging session-*.scope yet, so I can't give any tips in advance
[15:26] <elfy> pitti: yep,aas soon as I'm set I'll let you know and we can go from there
[15:27] <balloons> ubuntuonair.com, #ubuntu-on-air
[15:27] <balloons> happening in 30 mins :-)]
[15:29] <elfy> ok - just opening up the 50 page doc of grievances ...
[15:29] <elfy> I'll just paste that :p
[15:30] <balloons> elfy, perfect.. we won't be short on content
[15:32] <elfy> ha ha ha
[15:33] <elfy> balloons: 1700UTC is in ~90 minutes ...
[15:34] <elfy> oh nvm - got an e-mail just now :p
[15:42] <balloons> elfy, I was wrong.. mhall119 corrected me,,. 1700 it is
[15:45] <elfy> balloons: so 17:00 UTC for sure?
[15:45] <elfy> I have 3 nice questions lined up :)
[15:46] <wxl> awwwwwwwww fooey
[15:46] <balloons> elfy, yes 1700 for sure
[15:46] <balloons> wxl, if you have a question, leave it and I'll ask it
[15:47] <balloons> I'm sorry i jumped the gun on the time!
[15:47] <balloons> just excitied
[15:47] <wxl> thx balloons
[15:47] <wxl> esp. thx for including lubuntu-qa!
[15:47] <wxl> saves me the trouble XD
[15:47] <balloons> ofc!
[15:48] <elfy> hong kong phooey
[15:49] <elfy> xubuntu didn't get one :|
[15:49] <elfy> hating on Nick now ...
[15:49] <wxl> i ♥ hong kong phooey
[15:49]  * wxl used to have the lunch box
[15:50] <elfy> lol
[15:51] <mhall119> balloons: yeah, I've updated our calendar event to match
[15:52] <balloons> excellent
[15:54] <balloons> elfy, xubuntu-devel@lists.ubuntu.com or >
[15:54] <balloons> ?
[15:54] <elfy> balloons: that is our dev list - that's where our QA stuff goes
[15:58] <balloons> there you go
[16:40] <elfy> pitti: ok - reproduced in vbox - if you really want me to jump through the hoops from qemu let me know, but at least I can debug sensibly now
[16:53] <aikidouke> are there scheduled quality team meetings?
[16:56] <pitti> elfy: how do you mean "jump through the hoops"? if you can reproduce it and have a recipe how to set up QEMU that it hangs, that's all I need :)
[16:57] <elfy> pitti: I mean actually reinstall something I don't use :p
[16:57] <elfy> but I'm doing that now
[16:57] <pitti> elfy: oh, "vbox" -- that'll do too
[16:58] <pitti> elfy: when I said "QEMU" I really meant "check if you can reproduce this from a clean install in a standard environment"
[16:58] <pitti> elfy: i. e. just open a bug, tell me what exactly you did to get the hang, and I'll see to reproduce it
[16:59] <elfy> pitti: what shall I report it against then?
[17:00] <mhall119> balloons: and whomever is joining you on the Q&A: https://plus.google.com/hangouts/_/hoaevent/AP36tYc_Jg_IyTLOUIpvtL24uYefe8mWf-6639QfspZIAHUEtjyPdg?authuser=2&hl=en
[17:00] <elfy> pitti: I assume systemd
[17:00] <balloons> mhall119, ack
[17:02] <balloons> mhall119, we'll be a moment
[17:02] <mhall119> ok
[17:03] <pitti> elfy: systemd sounds okay, I'll reassign it as appropriate (probably libvirt -- but do start with sytsemd, it collects interesting logs)
[17:03] <elfy> pitti: ack
[17:03] <elfy> I'll just finish up qemu as well now I've started :)
[17:04] <pitti> elfy: argh, sorry for the confusion and double work
[17:04] <elfy> pitti: no matter - best to prove it where I can I think :)
[17:35] <elfy> pitti: bug 1456730 I think I got everything
[17:47] <Kamilion> Curious about how/if Xen gets tested (in or out of openstack)
[17:51] <kenvandine> ubuntu-qa: is it possible to automate integration testing for content transfers that require using multiple processes yet?
[17:51] <kenvandine> i created those testability peers to aid in this, but i think we still need work there
[17:52] <kenvandine> i think we could possibly test transfers between the testibility peers, but not initiated by url-dispatcher
[17:53] <kenvandine> there wouldn't be a way to test the success or failure
[17:53] <kenvandine> this is specifically around testing this branch: https://code.launchpad.net/~ken-vandine/content-hub/url-dispatcher/+merge/259039
[17:54] <kenvandine> url-dispatcher is a fire and forget kind of thing, we won't have any way to confirm the other end succeeded in an automated way... it would launch another app
[17:54] <kenvandine> vrruiz, ^^
[18:10] <balloons> nuclearbob, https://lists.ubuntu.com/archives/ubuntu-quality/2015-May/005962.html is the mailing list thread. I think a reply from you would make some folks happy :-)
[18:12] <elfy> balloons: anyway - so my main milestone issue is that last couple of cycles - everyone but Ubuntu has had to chase up issues that do affect Ubuntu
[18:13] <elfy> if - everyone diodn't bother with milestones until Final - there's just going to be more being shouted about right at the end
[18:14]  * wxl notes that there does not seem to be a ticket for the jenkins thing on rt
[18:15] <balloons> elfy, ahh. Sorry I didn't pick that up in the question. So your concern is that the issues wouldn't be noticed if flavors didn't test during milestones
[18:15] <wxl> in fact a search for jenkins in content only pulls up two tickets, both of which are resolved
[18:16] <wxl> so maybe it would be wise to report this to rt so we can track status, elfy/balloons
[18:16] <balloons> wxl, that's correct, there is no RT atm.
[18:16] <wxl> that way we don't have to ask the question about where it's at
[18:19] <wxl> balloons: elfy: if you guys don't have time, let me know and i'll jump in!
[18:19] <balloons> wxl, sure go for it :-)
[18:21] <wxl> oh man so excited to hear that formal testing is on the way!!!
[18:21]  * wxl just catching up on what i missed on ubuntu on air
[18:25] <elfy> balloons: yes - that's my issue in a nut shell :)
[18:27] <balloons> elfy, that's an excellent point. So given the fact ubuntu will continue with only a couple milestones, what can we do to mitigate issues? I think having those installer tests and the information obtained more readily consumable would allay your concerns. Would you agree?
[18:29] <elfy> I'd hope that would get closer to allaying them :p
[18:31] <wxl> sent
[18:31] <elfy> balloons: tbh - not sure what *we're* going to do yet milestone wise
[18:31] <elfy> balloons: also concerned that ALL flavours help with setting the 'pre-Ubuntu'milestones up too
[18:32] <elfy> Kubuntu/Xubuntu and Lubuntu did the last cycles ones
[18:33] <balloons> elfy, do you not think it's well represented? As I said, I thought you collectively have been doing a great job
[18:33] <elfy> balloons: not what I mean at all - I'll be sorely pissed off if the same people end up doing it over and over again is all :)
[18:34] <elfy> the other flavours need to also step up to the plate
[18:34] <balloons> elfy, it would seem to me however, dropping a milestone or two is still probably a good idea for most flavors. But that's just me. I think this has been reflected by teams skipping one
[18:35] <elfy> yea - we're likely to start at Beta again - though that's not set in stone yet
[18:35] <balloons> elfy, ahh.. yes, ubuntu gnome and ubuntu mate should play a role this time around. I believe / trust they will, but we can urge them towards that
[18:35] <elfy> ali hates irc :p
[18:35] <balloons> kylin as well.. :-)
[18:35] <elfy> yep
[18:35] <balloons> elfy, :-)
[18:36] <balloons> ok, so I think for the moment then focusing on getting ubiquity tests running again is a good way forward
[18:37] <elfy> yep - agreed
[18:37] <balloons> then, making sure other flavors provide coverage for milestones, while encouraging them to review how many they wish to have would be next
[18:37] <balloons> awesome, nice to be on the same page :-)
[18:37] <elfy> for sure :)
[18:38] <alesage> kenvandine, FYI we're sprinting, sure that ubuntu-qa wants to answer your q in time :) ^^
[18:38] <elfy> balloons: so the next question - who was that bouncing about on your bed :p
[18:39] <kenvandine> alesage, thx, i can't think of a way we can test the url-dispatcher stuff, since it's really a fire and forget
[18:39] <veebers> kenvandine: what would be involved? Do you need to launch 2 apps or something at a lower level?
[18:39] <kenvandine> but vrruiz is blocking my landing :)
[18:39] <kenvandine> well i need to run url-dispatcher with a content url
[18:39] <kenvandine> then handle the app that it opens
[18:40] <kenvandine> but url-dispatcher won't tell me if the content transfer succeeded or not
[18:40] <kenvandine> it just hands it off
[18:43] <veebers> kenvandine: If the app that is launched is launched with testability that autopilot will be able to introspect it
[18:43] <balloons> elfy, you got to see Leo and Max, who are elopio and nuclearbob respectively
[18:44] <kenvandine> veebers, can url-dispatcher launch an app with testability?
[18:44] <elfy> balloons: I thought Leo was elopio -wasn't sure the hairy beardy was though :p
[18:45] <kenvandine> and actually it's harder than that
[18:45] <kenvandine> url-dispatcher calls content-hub-send which creates a transfer with the content-hub-service which launches messaging-app with ubuntu-app-launch
[18:46] <kenvandine> so quite a few levels there, plus dbus
[18:47] <kenvandine> we've never been able automate that stuff, and hadn't allocated the time to do all that for this sprint
[18:47] <pitti> elfy: thanks for your report! will check tomorrow
[18:48] <elfy> pitti: okey doke - thought you'd gone home by now :)
[18:48] <pitti> elfy: technically I never left home :)
[18:48] <pitti> elfy: but I was checking some important bug again
[18:48] <elfy> :)
[19:03] <veebers> kenvandine: If you want to <trigger url-dispatch> -> [blackbox] -> Apps is launched and displays received details. You should be able to.
[19:04] <veebers> kenvandine: Just in a meeting at the mo. but you should be able to set the testability env var for the launch of the app (at the end there)
[19:14] <elfy> wxl: lol - where did you drag piskie up from :) I don't see that nick much anymore
[19:36] <balloons> elopio, http://people.canonical.com/~nskaggs/core-apps-test-sponsoring.html. I believe calc, terminal and docviewer are worthy of a look
[20:10] <wxl> elfy:
[20:11] <wxl> 1310 -!- elfy [elfy@ubuntu/member/forestpiskie]
[20:11] <wxl> 1310 -!-  ircname  : forestpiskie
[20:11] <elfy> heh - don'toften look at that :)
[20:11] <wxl> is that your launchpad id??/
[20:12] <elfy> elfy is
[20:12] <elfy> everywhere but the old freenode account
[20:12] <elfy> and that e-mail address is almost dead now too
[20:13] <elfy> LP is correct
[20:59] <elopio> sjcazzol: http://people.canonical.com/~nskaggs/core-apps-test-sponsoring.html
[21:01] <elfy> evening elopio - you made my day bouncing on that bed :p
[21:01] <elfy> at least it looked like a bed ...
[21:40] <balloons> sjcazzol, hello
[21:40] <balloons> sjcazzol, https://code.launchpad.net/~nskaggs/autopilot/add-wm-sandbox-run/+merge/242274
[21:43] <balloons> sjcazzol, elopio autopilot3-sandbox-run -X -s 400x600
[21:43] <sjcazzol> balloons,
[21:43] <sjcazzol> balloons, thanks