[02:09] <imgbot> [03:29] <imgbot> [03:29] <imgbot> [06:08] <davmor2> popey: confirmed ota for all devices has wifi disabled
[07:17] <popey> davmor2: intentional?
[07:17] <didrocks> hey popey! how was your travel?
[07:17] <popey> great!
[07:18] <didrocks> the 1h jetlag isn't terrible, right? :p
[07:18] <didrocks> do you confirm they really have the wrong type of plug btw? :)
[07:18] <popey> ☻
[07:20] <popey> ['/90
[07:32] <davmor2> popey: I assume not
[07:32] <didrocks> hey davmor2! Hoping that your flight was uneventful :)
[07:33] <davmor2> didrocks: how little you know
[07:33] <popey> davmor2: ok, will file a bug
[07:33] <didrocks> waow, sounds… epic
[07:33] <davmor2>  popey thanks
[07:36] <popey> davmor2: bug 1320780
[07:45] <davmor2> popey: confirmed
[07:48] <popey> ta
[07:51] <bzoltan> didrocks: do you know if there are a QA master who could ack our UITK in the Silo15?
[07:51] <didrocks> bzoltan: I think they stopped doing the validation, you can maybe check with someone in Malta? (I guess you have QA folks there)
[07:53] <bzoltan> didrocks: OK, thanks. I will look around. I have attached all the autopilot logs to the Silo15 sheet.. that should help a bit.
[07:54] <didrocks> great :)
[08:02] <Mirv> didrocks: they also drive on the wrong side of the road
[08:04] <didrocks> Mirv: wrong plug, wrong side of the road but good timezone
[08:04] <didrocks> I give them 33% then
[08:10] <asac> didrocks: do they have UK plug?
[08:11] <didrocks> asac: yeah…
[08:11] <asac> didrocks: can you ping me in 20 seconds? wanbt to check something :)
[08:12] <didrocks> asac: ping!
[08:12] <asac> didrocks: ack. thanks!
[08:12] <didrocks> yw :)
[08:12] <sil2100> ;p
[08:13] <asac> didrocks: wanted to check what the time offset ist hat bip displays here... seems it displays UTC time
[08:13] <didrocks> your bip service is in an UTC machine?
[08:13] <asac> yeah
[08:13] <asac> seems so :)
[08:16] <Laney> wait, do they drive on the right (left) side there?
[08:16] <Laney> I like the sound of this place!
[08:17] <didrocks> Laney: right is right, left can't be right. It's in the name! :)
[08:18] <Laney> rong!
[08:21] <ogra_> oh ! 37 looks really nice on the dashboard
[08:22] <asac> :)
[08:23] <ogra_> that was surely worth all the hassle on thu and fri :)
[08:23] <seb128> Laney, it was a British colony until 1974
[08:23] <seb128> Laney, so it's pretty much on u.k standards
[08:23] <Laney> yeah
[08:23] <sil2100> ;)
[08:23] <Laney> I knew about the plugs, but not about the road side
[08:23] <Laney> but it does make sense
[08:24] <sil2100> ogra_: we even had 8 tests ran on manta!
[08:24] <ogra_> lol
[08:24] <sil2100> All of them were a big success as well
[08:24] <asac> when did manta fall over?
[08:24] <asac> 26 is the last image that gave more than 0 results?
[08:24] <asac> guess 27 is when it fell apart
[08:25] <ogra_> asac, it never worked right ... the devices started failing around 27 though
[08:25] <sil2100> asac: there were networking issues there, from what I remember someone mentioned driver failures
[08:26] <ogra_> (but until someone makes Mir/oxide behave it is pretty unusable anyway)
[08:26] <ogra_> right, cyphermox is looking actively into it
[08:26] <veebers> Saviq: hey how's it going. Can you you let me know when you're done with the gatekeeper? :-)
[08:26] <sil2100> You can always use it as a digital picture though
[08:26] <Saviq> veebers, oops, if you need it cancel my job
[08:26] <ogra_> heh, yeah
[08:27] <ogra_> as long as you dont want to display pics from a html site
[08:27] <ogra_> :)
[08:27] <Saviq> veebers, didn't think you guys would still be around
[08:27] <veebers> Saviq: well, if you need the run I can wait a little bit
[08:27] <veebers> Saviq: we're currently in Malta for a sprint
[08:27] <Saviq> veebers, aah that explains things ;)
[08:28] <Saviq> veebers, you could just queue the job now
[08:28] <veebers> Saviq: aye, good point I'll do that :D
[08:28] <ogra_> Wellark, so we have two lindicator-network-service crashers during dualer-app and messaging-app tests on mako (this is with ofono-phonesim-autostart installed FWIW) see http://ci.ubuntu.com/smokeng/utopic/touch/mako/37:20140519:20140513.2/8093/ (click on the test name and scroll down to find the .crash files)
[08:29] <ogra_> *dialer-app ...
[08:29] <ogra_> thought you would be interested :)
[08:31] <sil2100> ogra_: do you know if psivaa is on the sprint this week or the next?
[08:31] <ogra_> is he QA ir CI ?
[08:32] <psivaa> sil2100: on the way
[08:32] <ogra_> QA is there this week i think
[08:32] <ogra_> ha
[08:32] <psivaa> not to the sprint but to the meeting. hangout is failing me
[08:46] <sil2100> Too many things happening right now, geh!
[08:47]  * sil2100 wonders if anything landed inbetween 37 and now
[08:47] <ogra_> i was asking if you want the summary :P
[08:49] <xnox> didrocks: wouldn't the right currency push it to 50%? =)
[08:49] <ogra_> 34 fixed a firewall test issue (py2->3 switch) ... and had a unity8 landing, as well as the final indicator-network fix
[08:49] <didrocks> xnox: well, did you here about what happened between Malta and euro? :p
[08:49] <ogra_> 35 had another unioty8 and addressbook-app landing
[08:50] <didrocks> xnox: so not sure I'm going to vote for it ;)
[08:50] <ogra_> in 36 Laney has gone wild and uploaded our seed !! (for desktop session changes)
[08:50] <ogra_> and 37 had nothing interesting
[08:50] <ogra_> sil2100, ^^^
[08:51] <xnox> didrocks: not sure what happened between Malta and euro, but i do know what happened between Lats and Euro =) which was only this year.
[08:53] <popey> Laney: I only noticed the road side half way to the hotel from the airport
[08:54] <Laney> "wait, everything is normal"
[08:54] <popey> very.
[08:54] <ogra_> lol ... normal
[08:54] <popey> its nice not being the guy hogging the mains strip
[09:05] <popey> davmor2: video lens, put videos on device, check out thumbnails - they're broken
[09:05] <popey> saw this on #36 last night and #37 today
[09:06] <popey> imgur.com/p0oiNEo
[09:06] <popey> like that
[09:09] <sil2100> ogra_: I meant like, if anything landed after 37 ;)
[09:10] <sil2100> ogra_: since I'm thinking about publishing UITK, and prefered to have an image 'before' that
[09:10] <sil2100> brb, vet
[09:25] <mhr3> Saviq, ^^ see the imgur link
[09:26] <Saviq> mhr3, :|
[09:30] <Wellark> ogra_: ok. thanks! isn't the smoketester doing retraces automatically? :(
[09:36] <ogra_> i dont think so
[09:37] <ogra_> Wellark, oh, and it seems we still come up with wifi off after a flash .... which might be fine on first boot but is surely wrong after an OTA upgrade ... popey opened a bug for  that
[09:37] <ogra_> (works fine after enabling wlan again)
[09:42] <Wellark> ogra_: I would still think the wifi off thingy relates to lower level
[09:42] <t1mp> sil2100: do we still need QA signoff for the landing in silo15? I think that's the only thing we are still waiting for
[09:44] <Wellark> ogra_: so, how do I retrace that thing manually?
[09:45] <ogra_> dunno, there is a wikipage for that ... apport-retrace or so
[09:51] <mhr3> Mirv, can i have silo for #36?
[09:52] <mhr3> 35
[09:52] <Mirv> mhr3: sure
[10:16] <sil2100> Damn
[10:16]  * sil2100 is back
[10:16] <sil2100> t1mp: no, no sign-off needed right now
[10:17] <t1mp> ok, thanks
[10:20] <sil2100> t1mp: I'll try publishing it in some nearest minutes
[10:21] <t1mp> sil2100: great
[10:30] <Mirv> ogra_: ui-toolkit needs packaging ack, they depend on one more module from qtdeclarative-opensource-src: https://ci-train.ubuntu.com/job/landing-015-2-publish/21/artifact/packaging_changes_ubuntu-ui-toolkit_0.1.46+14.10.20140516-0ubuntu1.diff
[10:30] <Mirv> t1mp: sil2100: I think you are talking about the same landing ^ :)
[10:30] <ogra_> Mirv, oooh i see my name imn there ACK ACK ACK !!!
[10:30] <ogra_> :)
[10:31] <Mirv> that was easy :)
[10:31] <sil2100> :)
[10:31] <ogra_> no more crazy vibrating when touching buttons :)
[10:31] <Mirv> +1 to that
[10:31] <sil2100> +1
[10:32] <sil2100> I was still looking at a possible image before publishing that one, but well, it's not that important - we have all we need in 37
[10:32] <ogra_> hmm, all these bug references ... is the janitor evn reacting to such entries ?
[10:33] <ogra_> should be (LP: #nnnnnn)
[10:33] <Mirv> sil2100: oh, I figured there weren't much landed after 37 that'd need a separate image
[10:34] <sil2100> Mirv: yes, as I said, all we need is in #37, so it's cool
[10:34] <sil2100> Just wanted to make sure, that's why I wasn't publishing instantly :)
[10:49] <Wellark> ok,  errors.u.c does not have stack traces
[10:50] <Wellark> and pete-woods told me that it seems that retracing seems to be totally broken and has been for some time now
[10:50] <Wellark> is this a known problem and is someone working on it?
[10:51] <pete-woods> Wellark: it doesn't quite look like retracing itself that is broken, the original stacktraces appear not to be being saved
[10:51] <pete-woods> Wellark: e.g. if you look into a specific crash here (https://errors.ubuntu.com/oops/90362158-dd16-11e3-bb6e-fa163e707a72)
[10:51] <pete-woods> there's just no stacktrace field at all
[10:51] <Wellark> or these ones https://errors.ubuntu.com/problem/f761f1b6abedfe3a66f40e2108453a087f22523c
[10:52] <Wellark> obviously a retrace has been made to be able to generate the "function"
[10:52] <Wellark> (title)
[10:52] <Wellark> but then it's lost.
[10:53] <Wellark> which makes it pretty much quite impossible to reliably figure out what's going on.
[10:54] <ogra_> well, you could pull the .crash file to your own devices and retrace yourself
[10:55] <Wellark> ogra_: errors.u.c does not offer the .crash files
[10:55] <ogra_> they are linked at the test results i gave you above
[10:56] <Wellark> ogra_: this is not about those tests. this is about why errors.u.c is not providing the stacktraces anymore
[10:57] <Wellark> + there is no way of making a connection between a random .crash file you get from somewhere and a report in errors.u.c.
[10:57] <ogra_> i think there was a race that the upload gets corrupted or so ...
[10:57] <Wellark> well, that's quite critical
[10:57] <ogra_> there is ... there is a device ID involved
[10:58] <ogra_> but someone from CI would have to determine it for you i guess
[10:59] <Wellark> is anyone working on getting the stactraces on errors.u.c fixed?'
[11:00] <Wellark> is there a bug filed for it?
[11:00]  * ogra_ has no idea, ... 
[11:00] <ogra_> probably ev knows
[11:01] <sil2100> davmor2: just give me a sign once you have some dogfooding results
[11:01] <ogra_> ++
[11:01] <sil2100> davmor2: I personally wouldn't block promotion on the wifi-not-enabled-by-default thingy, but it's you as the QA-master to decide ;)
[11:02] <ogra_> yeah, not enabled after installl isnt a biggie ... switched off after OTA is something that needs to be mentioned in your mail though
[11:02] <ogra_> (but i agree it is no blocker)
[11:03] <sil2100> Right, +1 on mentioning that
[11:03] <Wellark> sil2100: we need more info on that "wifi off"
[11:03] <Wellark> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1320780
[11:09] <sil2100> Wellark: valid points
[11:09] <sil2100> davmor2: ^^
[11:29] <ev> pete-woods, Wellark, ogra_: completed stacktraces will never appear next to an instance of an error (an OOPS). This is because we group instances of crashes together by their stacktrace (well, a signature formed from it). So the problem page (a collection of crashes) should show the stacktrace
[11:30] <ev> obviously it's not for that particular one
[11:30] <ev> and it's not immediately clear why
[11:30] <ev> I'll ask bdmurray to have a look at it tomorrow
[11:30] <Wellark> ev: do you need more examples?
[11:30] <ev> any you have would help
[11:30] <Wellark> there is now one for hud and one for indicator-network
[11:30] <Wellark> pete-woods: do you have more examples?
[11:33] <pete-woods> Wellark: it actually looks like the HUD examples "fixed themselves" since I looked last https://errors.ubuntu.com/problem/b649801824262e51a5430cdf72a85fc3fe951765
[11:34] <pete-woods> it claims both a failure to retrace, but now has actually retraced
[11:35] <ev> Wellark, pete-woods: I've created this task to track it: https://app.asana.com/0/11345516654327/12422265621458 (you should have invites to Asana)
[11:36] <Wellark> ev: thanks!
[11:48] <mhr3> sil2100, /me off for today, if someone asks you to set one of my silos as tested, pls do ;)
[11:52] <sil2100> mhr3: aye! ;)
[11:56] <davmor2> sil2100: no worries it sounds like design are saying it's not them but I need to chase it down so more
[11:58] <Mirv> argh, why oh why I've problems running ap locally on #37 for address-book-app/calendar/clock. always failures.
[12:00] <davmor2> Mirv: I got no issues here, are you running autopilot tests?
[12:00] <sil2100> Mirv: how is it failing?
[12:20] <Mirv> davmor2: yes, AP
[12:20] <Mirv> davmor2: you got no issues, great! #37? there's a really nice PPA called ppa:ci-train-ppa-service/landing-005 that just begs you to upgrade to!
[12:21] <Mirv> sil2100: the tests just fail. on the other hand, now my phone is crashing on bootup so I guess it's maybe a sign to do a --bootstrap --wipe...
[12:21] <sil2100> uh
[12:22] <Mirv> I repeat that I'd like to understand what's happening a bit more often..
[12:28] <davmor2> Mirv: no there isn't :P
[12:39] <cgoldberg> thomi:
[12:39] <cgoldberg> $ python3 -m autopilot.run run autopilot.tests.functional.test_autopilot_functional.AutopilotVerboseFunctionalTests.test_local_module_loaded_and_not_system_module
[12:40] <ogra_> sil2100, davmor2, any news on promotion ?
[12:41] <didrocks> are you really considering promotion for an image with wifi off by default?
[12:41] <ogra_> didrocks, its a single switch you need to flick after flashing
[12:42] <ogra_> (and only then)
[12:42] <didrocks> seems like we are getting down on our quality expectations though
[12:42] <sil2100> didrocks: it's for davmor2 to decide - but since you can 'enable' it easily, I wouldn't personally block on that
[12:42] <sil2100> QA makes the final decision though
[12:42] <didrocks> yeah, let's see
[12:43] <ogra_> i wouldnt see it as a drastic blocker of you have to enable it once after the flash ...
[12:44] <davmor2> sil2100: no I'm temped to say not to block on it as you only need to flick it on and then it works
[12:46] <sil2100> davmor2: any more news on design about this? :) Since you mention they say they most probably didn't intend this
[12:46]  * sil2100 still waits for UITK to move out of proposed
[12:47] <davmor2> sil2100: yeah it appears that there is a lot of discussion around it Wellark though didn't actually set it up so it sounds like a race condition
[12:47] <sil2100> davmor2: did you see his comment on the bug btw.?
[12:47] <ogra_> already passed all tests ... next publisher run should promote it
[12:47] <sil2100> davmor2: (I know you have a lot going on there thought ;) )
[12:48] <davmor2> sil2100: #phablet
[12:48] <sil2100> ogra_: would like to have an image kicked after UITK lands ;) What do you say?
[12:48] <ogra_> ++
[12:48] <ogra_> definitely
[12:51] <davmor2> sil2100: so other than the wifi issue I don't really see anything more broken on this image
[12:51] <ogra_> davmor2, 3G is fine =
[12:51] <ogra_> ?
[12:53] <davmor2> ogra_: I can't test it, I have no data connection.  Please feel free to add comments on it
[12:53]  * didrocks always fears when he heard "it's a race" and we don't have great understanding of it
[12:53] <ogra_> davmor2, that would require me to have a device to test -proposed
[12:53] <davmor2> ogra_: as far as I can tell it is only wifi here that is effected
[12:54] <ogra_> i thought you guys had test SIMs over there for exactly this
[12:54] <davmor2> ogra_: no I have my sim
[12:55] <ogra_> davmor2, i mean there were management discussions to bring a handfull of SIMs for the dogfooders
[12:55] <ogra_> ask pmcgowan ...
[12:55] <davmor2> will do
[12:55] <davmor2> brb
[12:56] <ogra_> i know popey checked 3G on 36 ...
[12:56] <ogra_> (but thats indeed not 37)
[12:56] <sil2100> Let's test the image that's the candidate
[12:56] <didrocks> ogra_: do you understand exactly what changed to not have wifi on first startup?
[12:56] <ogra_> didrocks, nope
[12:57] <didrocks> that's… concerning
[12:57] <ogra_> didrocks, but we know the symptoms and their impact
[12:57] <sil2100> didrocks: no worries, I don't intend to promote it like now before there is more clarification
[12:57] <sil2100> I saw some discussion on #phablet
[12:57] <didrocks> ogra_: exact impact? do you have enough reboot to ensure it's not a race and can happen randomly, even on configured upgraded setup?
[12:57] <ogra_> didrocks, it definitely needs research, but as long as it works and only has that little annoyance i dont think we need to block on it
[12:58]  * didrocks feels it's a potential issue that can strike back in a worse state and side-effects
[12:58] <ogra_> didrocks, it happens after any flash action ... but works fine after reboots
[12:58]  * ogra_ doesnt think it is that bad
[12:58] <ogra_> its an annoyance
[12:59] <didrocks> but we don't really know the consequences because we don't know the why
[12:59] <ogra_> and as long as we know people look at it i'm confident we'll get a fix soon
[13:01] <ogra_> didrocks, the problem is you cant just bisect it ... the whole set of images of the last week had massive network issues due to various new issues every day ... getting the image out to users is the best way to get more data on the issue ...
[13:01] <didrocks> ogra_: and potentially to put people using their phone as daily driver on trouble
[13:02] <ogra_> well
[13:02] <ogra_> making them flick a switch once, after OTA or fresh flash
[13:02] <ogra_> surely not such a big trouble
[13:02] <didrocks> without knowing the cause, you are not clearly not sure about the consequence and trouble :)
[13:02] <ogra_> we know it is a problem related to booting ... and obviously only happens after flashing
[13:03] <didrocks> but I guess I gave my opinion, then, you are the one in charge :)
[13:03] <ogra_> nope, i'm not :)
[13:03] <ogra_> i also only give my opinion here :)
[13:03] <ogra_> last word is on sil2100 and davmor2
[13:04] <ogra_> i know that Wellark looks into indicator reaalted issues and cyphermox into NM urfkill and driver related ones
[13:04] <ogra_> so the problem is in god hands
[13:04] <ogra_> *good
[13:05]  * didrocks notices ogra_ retrogaded some people from "god hands" to "good hands"
[13:05] <ogra_> heh
[13:06] <Mirv> ogra_: rmadison tells me ui-toolkit is in release pocket now
[13:06] <ogra_> build triggered
[13:07] <sil2100> o/
[13:10] <davmor2> sil2100: ogra_: there is a guy here with a local sim 3g works
[13:10] <ogra_> awesome !
[13:14] <imgbot> [13:15] <jdstrand> I'm looking at http://ci.ubuntu.com/smokeng/utopic/touch/mako/36:20140518:20140513.2/8078/security/1137284/, which passed, but the 'Console Log' and 'Artifacts' seems to be wrong
[13:16] <jdstrand> as in, it seems to come from another test run
[13:16] <sil2100> jdstrand: so, we had some issues with 36, some tests didn't run and had to be ran later, maybe that's the reason
[13:16] <sil2100> Let me take a look
[13:16] <sil2100> psivaa: ^
[13:17] <psivaa> sil2100: jdstrand: let me take a look
[13:17] <jdstrand> well, like I said, the 'Test case data' looks ok. it is just that the attached logs all seem to be for a different set of tests. eg, I see nothing about ufw in either
[13:18] <jdstrand> https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/126/console and https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/126/artifact/clientlogs/security/
[13:30] <psivaa> jdstrand: http://pastebin.ubuntu.com/7488517/ is the segment of copying the logs for the security test. are the ufw logs stored somewhere else in the device?
[13:30] <psivaa> i.e. other than /home/phablet/.cache/upstart/
[13:32] <ogra_> most likely in a system path like /var/log
[13:36] <psivaa> ogra_: ok, i can only see /var/log/apt/history.log and /var/log/dpkg.log that has any reference to 'ufw' on a device that ran the security tests.
[13:37] <ogra_> well, there should surely be an upstart log of the upstart job
[13:37] <ogra_> not sure what else ufw logs ... or where
[13:38] <ogra_> jhodapp, we are still seeing a media-hub crash during automated testing, is that still on your plate ?
[13:38] <jdstrand> psivaa: ufw won't log somewhere else. mostly I was confused that console log didn't have stdout/stderr in it
[13:38] <jdstrand> s/ufw/the ufw tests/
[13:39] <ogra_> jdstrand, http://ci.ubuntu.com/smokeng/utopic/touch/mako/37:20140519:20140513.2/8093/security/1139053/
[13:39] <jdstrand> I know
[13:39] <ogra_> that should show stdout on the website at least
[13:40] <jdstrand> what I was saying was that 'Console' did not have it. I'm not blocked, I'm just reporting that the link for 'Console' doesn't have stdout/stderr from the test run
[13:41] <jdstrand> https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/128/console
[13:41]  * ogra_ thinks these console logs are weird anyway ... they have the whole log for all runs usually
[13:41] <jdstrand> ^ (no mention of ufw)
[13:41] <ogra_> you want https://jenkins.qa.ubuntu.com/job/utopic-touch-mako-smoke-daily/128/consoleFull
[13:41] <psivaa> jdstrand: ogra_: yea, console log caching is coming in the way i think
[13:41] <ogra_> else the first 1M is cut off
[13:42] <jdstrand> ah, well, we should link 'Console Log' to consoleFull, no? I had never heard of consoleFull
[13:42] <ogra_> i see a lot of ufw mentionings in the "Full" log
[13:43] <ogra_> jdstrand, go to console log, check the top of the log
[13:43] <ogra_> there is a small link
[13:43] <jdstrand> yes, me too. I wouldn't have said anything if the 'Console Log' link in http://ci.ubuntu.com/smokeng/utopic/touch/mako/37:20140519:20140513.2/8093/security/1139053/ went to consoleFull
[13:44] <ogra_> it is well hidden in front of your face ;)
[13:44] <jdstrand> I see the 'Full Log' link now. I missed it
[13:44] <jdstrand> it is pretty small
[13:44] <ogra_> yeah, should be <h2> and <blink> ;)
[13:44] <jdstrand> but I don't see why one wouldn't want to see all the logs. call it user error if you choose, but I think the usability could be improved
[13:45] <ogra_> i guess jenkins is just being clever here
[13:45] <ogra_> (it is properly translated to german, so i suspect its from jenkis itself)
[13:51] <psivaa> jdstrand: doing an MP to try and improve that to direct to consoleFull, hope it'd improve that bit.
[13:51] <jdstrand> thanks! :)
[14:07] <rsalveti> sil2100: can I get a silo for 32?
[14:07] <sil2100> rsalveti: looking
[14:07] <rsalveti> sil2100: platform-api is blocked by landing 01, but that's just a pre-flight silo
[14:07] <rsalveti> aka, in development
[14:08] <rsalveti> nothing should be blocked by it
[14:08] <sil2100> rsalveti: right! Let me get one for you straight away
[14:17] <Mirv> oh right 001 was preplanning only
[14:19] <sil2100> Mirv: indeed ;) I missed that as well somehow
[14:22] <Mirv> if we would live for Train longer it'd be good to simply have separate testing silos
[14:22] <Mirv> s/for/with/
[14:24] <rsalveti> sil2100: thanks!
[14:26] <sil2100> rsalveti: yw!
[14:26] <sil2100> Mirv: we might think about that, such as SRU-silos - but I think just increasing the number of silos would be sufficient
[14:34] <imgbot> [14:34] <imgbot> [14:45] <Mirv> not upgrading, trying these crappy test runs
[14:45] <Mirv> so --wipe --bootstrap helped, but one problem has been flaky network that might bring the wlan AP password dialog to front, and for example clock app at least requires network etc etc.. so I guess I have explanations for the problems I had
[14:46] <ogra_> Mirv, hmm, interesting ... the UITK dep you added seems to be on the image already
[14:46]  * ogra_ sses no added packages
[14:47] <Mirv> ogra_: I didn't add it, but ok
[14:48] <Mirv> there are probably other users of it, but UITK itself started using it only now
[14:48] <ogra_> yeah
[15:25] <Mirv> so another thing I have fairly frequent when running AP tests is that indicator-datetime and evolution-calendar-factory are consuming 100% CPU (well, 50%, or 100% of two CPU:s), which negatively affects tests
[15:38] <popey> sil2100: YO! updated bug 1320780
[15:40] <sil2100> Wellark: ^
[15:40] <sil2100> popey: thanks! :)
[15:44] <Mirv> quite a testing spree that was
[15:50] <sil2100> cyphermox: hi! Are you around already?
[15:50] <sil2100> cyphermox: did you have a look at bug #1320780 ?
[16:01] <sil2100> davmor2: poke, meeting, are you busy?
[16:01] <sil2100> popey: same ^ :)
[16:02] <popey> lemme join
[16:15] <sil2100> popey: beer it is! You deserve it!
[16:16] <cjwatson> Damnit I keep having to restart my livefs tests 'cos you guys have published silos :-)
[16:16] <popey> \o/
[16:18] <ogra_> cjwatson, let it run over night ... canada is off today we dont have an US TZ shift today
[16:18] <ogra_> so landings wont happen i gues
[16:18] <ogra_> s
[16:20] <cjwatson> I need to iterate during the day
[16:20] <cjwatson> It's not a problem, just amusing
[16:20] <ogra_> :)
[16:22] <sil2100> cjwatson: sorry! Just give us a sign when not to land and we'll wait ;)
[16:22] <asac> ogra_: no robert?
[16:22] <ogra_> asac, maple celebration day or some such in .ca today
[16:23] <sil2100> asac: holiday in Canada, but he was on the meeting and will be on the meeting with you :)
[16:23] <asac> inded
[16:23] <asac> sil2100: oh :)
[16:23] <asac> thats cool
[16:23] <sil2100> Maple celebration, sounds nice!
[16:23] <ogra_> asac, he was around in the landing meeting because he said he had a meeting with you later
[16:23] <asac> robru: we can also talk tomorrow!
[16:23] <asac> :)
[16:23] <asac> robru: no need to stick around for me during your public holiday
[16:23] <asac> robru: that was not my intend :/
[16:23] <robru> asac, ah, if it's ok with you.
[16:23] <robru> asac, I scheduled this before I realized it was a holiday
[16:23] <asac> robru: yes of course. if you would have told me, i wouldnt have it schedueld there
[16:24] <asac> robru: go off!!
[16:24] <asac> talk to you tomorrow
[16:24] <robru> asac, ok, see you tomorrow, thanks!
[16:24] <ogra_> and happy maple !
[16:24] <asac> see you and sorry!
[16:24] <ogra_> :)
[16:24] <robru> ;-)
[16:24] <asac> jummy :)
[16:24] <asac> ok tomorrow will be a fun long day
[16:24] <asac> nice
[16:28] <cjwatson> sil2100: no need, but thanks :)
[16:30]  * ogra_ goes to mow the lawn
[16:31] <cjwatson> woo, I now have a local setup that can do ubuntu-touch builds against a silo using a local Launchpad instance
[16:34] <didrocks> cjwatson: nice work! \o/
[16:36] <sil2100> Oh my! This smells CI Airlines :)!
[17:51] <ogra_> plars, in case you feel bored, shorts, filemanager and gallery on flo could need some love too
[18:01] <plars> I'll take a look
[18:05] <sil2100> o/
[18:20] <Wellark> popey: thanks!
[18:20] <Wellark> I've EOD'ed, but let's hope cyphermox has time to look into those
[18:21] <Wellark> at least the "unavailable" state for the wifi device looks suspicious
[19:08] <ogra_> Wellark, do you knwo if anything in the stack ever made use of pm-utils ? we recently dropped it ... (and i still cant find out why)
[19:14] <josharenson> ping fginther
[19:46] <barry> mandel: i think we have at least two regressions in udm that cause failures in s-i.  we really need to add some integration tests to gate landings in udm.
[19:46] <barry> mandel: LP: #1320987 and LP: #1320306