[00:54] <bfiller> robru: around? needs silo for line 34 please
[00:58] <robru> bfiller, ok you're in silo 3
[00:59] <bfiller> robru: cheers
[00:59] <robru> bfiller, oooh, triple threat, you have silos 1, 2, and 3 ;-)
[00:59] <bfiller> robru: watch out :)
[02:04] <imgbot> [03:34] <imgbot> [03:34] <imgbot> [06:53] <mandel> cyphermox_, no problem!
[07:39] <Saviq> sil2100, woops, check out this commit message http://bazaar.launchpad.net/~unity-team/unity-api/trunk/revision/145
[07:39] <Saviq> sil2100, looks like you need to set() the approvers :)
[07:40] <Saviq> sil2100, but actually really, it looks like it takes all votes into account, so even if I approved and then disapproved for some reason, I'd show up in the list?
[07:40] <sil2100> Oh!
[07:40] <sil2100> Saviq: eeek!
[07:41] <Saviq> sil2100, indeed
[07:41] <sil2100> Saviq: let me fix that quickly
[07:48] <brendand> sil2100, ah - what happened to mako results?
[07:50] <Mirv> a good question
[07:51] <Mirv> also, manta and flo are (to the extent they've run) failing/exploding a lot, so something is a miss
[07:51] <Mirv> -' '
[07:51] <sil2100> Saviq: fix ready, just let me test it this time
[07:58] <ogra_> hmm, no mako tests at all for 123
[08:01] <sil2100> psivaa-off will be a bit later today, so we'll have to wait for the answer...
[08:01] <popey> davmor2: bug 1338939 seems fixed in #123, so alarms don't go off 3 times
[08:03] <sil2100> Saviq: should be good now, the previous mechanism was a bit too simple it seems
[08:07] <brendand> sil2100, i'm going to have to miss the meeting this morning. unless new things appear in 123, we have everything under control
[08:07] <brendand> sil2100, if there's anything i need to do just ping me
[08:07] <sil2100> brendand: I like the sound of that ;)
[08:08]  * ogra_ hopes the network-service crashes might be gone 
[08:08] <ogra_> buut thats probably just a dream :P
[08:18] <sil2100> Saviq: you can now also override the default 'smartass' prereq branch reorder
[08:19] <Saviq> sil2100, thanks
[08:19] <Saviq> davmor2, good news, I say we managed to handle the deadlock bug first-class, there's already fixes in store
[08:22] <sil2100> Saviq: which bug? :)
[08:27] <Saviq> sil2100, bug #1339700
[08:32] <sil2100> Saviq: \o/
[08:34] <davmor2> excellent
[08:40] <mvo_> sil2100: its very quiet so far, I am not misisng anything, right? its just quiet this morning :) ?
[08:40] <mvo_> sil2100: action wise I mean
[08:54] <sil2100> mvo_: yeah ;)
[08:55] <sil2100> mvo_: I'm surprised actually, it happens rarely! We even have 6 silos free :O
[08:55] <mvo_> great, I do patch piloting then in my free moment, I'm on duty today for that  as well
[08:55] <mvo_> sil2100: yeah I was wondering if we already got additional ones :)
[08:56]  * sil2100 grabs a coffee
[08:57] <sil2100> I just recently discovered the moka pot for coffee, usually I was just using instant coffee
[08:57] <sil2100> As I have no coffee machine at home
[08:57] <Mirv> indeed surprisingly quiet
[08:57] <Mirv> so it's done now? :)
[09:55] <mvo_> sil2100: i'm off for lunch
[09:55] <sil2100> mvo_: ok, no worries, today seems to be really quiet
[09:56] <sil2100> And I'm around if anything, although hacking the train right now
[10:14] <camako> sil2100, Can we have the distro pull from some branch other than lp:mir, perhaps from the full path (lp:~mir-team/mir/utopic)? This will allow us to config our Mir LP project page correctly. Currently, this is not possible because we can't change the "dev focus" setting since lp:mir will point to the new setting and break distro.
[10:15] <sil2100> camako: ok, so... citrain allows that, no problem, but this makes the nice 'trunk always synced with distro' idea invalid
[10:17] <sil2100> camako: in my opinion we could do that I guess, but I must say that we prefer the trunk branch to be the 'latest distro', while other branches pointing to the 'bleeding edge'
[10:18] <camako> sil2100, currently we have devel and we MP to trunk from there... so the idea doesn't hold as things stand anyways...
[10:19] <camako> sil2100, we want to merge to trunk when we have accumulated content which come in multiple MPs... we do that in the devel branch(es)
[10:19] <sil2100> camako: right, but at least trunk is up-to-date with distro, so anyone that wants to get the snapshot from the archive can just do bzr branch trunk
[10:20] <sil2100> hm
[10:20] <sil2100> camako: let me think about that - anyway, the infrastructure allows such a change, but let me think of how it can affect our concepts
[10:22] <camako> sil2100, I appreciate you entertaining the idea... Currently, our project page has incoherent info abt the status of the project (https://launchpad.net/mir) . E.g. latest version being 0.1.9 when we have released 0.4.0...
[10:24] <popey> ogra_: can we please include https://code.launchpad.net/~sergiusens/click-sync/reminders/+merge/218803 in the next image?
[10:24] <sil2100> camako: ok, let me look into that then :) I'll get back to you with some questions later most probably
[10:25] <camako> sil2100, thanks again... feel free.. :-)
[10:33] <ogra_> popey, i'm not sure i have commit rights to that branch
[10:34] <popey> ah, i see
[10:35] <popey> Laney: are you able to approve https://code.launchpad.net/~sergiusens/click-sync/reminders/+merge/218803 ?
[10:35] <ogra_> sil2100, in case you want to find out what pulled in a new package i now wrote a script: http://paste.ubuntu.com/7774488/
[10:35] <ogra_> popey, let me check first :)
[10:36] <ogra_> ah looks like i can ... it is owned by ubuntu-cdimage
[10:36] <popey> oh you are in https://launchpad.net/~ubuntu-cdimage/+members
[10:36] <popey> ☻
[10:36] <popey> Laney: ignore me, sorry.
[10:36] <Laney> popey: Good, because I don't know what that is so would have had to find out. :)
[10:37] <popey> hehe
[10:38] <ogra_> merged ... afaik the next cron run should pick it up and add it http://people.canonical.com/~ubuntu-archive/click_packages/click_list
[10:39] <davmor2> popey: latest image can you open the contacts app?
[10:39] <popey> thank you ogra_
[10:39] <davmor2> popey: and when you do does it show contacts
[10:40] <popey> yes
[10:40] <davmor2> I think my addressbook db might of got screwed during the updates then
[10:41] <davmor2> popey: this is what I get http://davmor2.co.uk/~davmor2/screenshots-phone/device-2014-07-10-114109.png
[10:42] <popey> i see contacts
[10:42] <popey> also, do you see app names being off centre?
[10:43] <davmor2> popey: 1 second
[10:45] <davmor2> popey: yes it looks like it is aligned right
[10:46] <davmor2> popey: dropping letters is the best for a screenshot :)
[10:46] <popey> ta, will file bug
[10:47] <davmor2> popey: rebooted now I have contacts again so no idea what was going on with that :)
[10:47] <popey> heh
[10:49] <popey> davmor2: bug 1340132
[10:53] <davmor2> popey: confirmed
[10:53] <popey> ta
[10:57] <ogra_> popey, reminders is now on http://people.canonical.com/~ubuntu-archive/click_packages/click_list ... next image will pick it up
[10:58] <popey> thanks, dpm ^
[10:58] <dpm> nice one, thanks ogra_, popey!
[10:59] <ogra_> and i notice that dekko breaks threading if i answer mails :(
[11:01] <psivaa> sil2100: so all 3 mako devices failed on 'phablet-network -n /home/ubuntu/magners-wifi' step
[11:01] <sil2100> psivaa: hi!
[11:01] <sil2100> psivaa: uh...
[11:01] <psivaa> sil2100: sorry, took longer than expected for me to be back online :)
[11:01] <psivaa> sil2100: is there any signs on network setup during dogfooding?
[11:02] <sil2100> psivaa: no worries ;) It's good to have you back though
[11:02] <sil2100> psivaa: didn't see anything, davmor2 you noticed any network problems with the latest image?
[11:02] <psivaa> sil2100: ogra_: i see 'dpkg-source: warning: failed to verify signature on ./ubuntu-ui-toolkit_0.1.49+14.10.20140709-0ubuntu1.dsc'
[11:03] <ogra_> psivaa, seems it was updated since the last "apt-get update"
[11:03] <davmor2> psivaa, sil2100: no but I wonder if the tests have been update to include the flight mode button?
[11:03] <ogra_> (which if in doubt was at image build time)
[11:12] <davmor2> popey: do you have an up-to-date flow ?  if so what happens if you open the settings app from the launcher?
[11:16] <psivaa> davmor2: the network setup failed before any tests start running
[11:16] <ogra_> did it ?
[11:16] <ogra_> it says it succeeded in the console log
[11:17] <ogra_> hmm, i wonder if this upgrade of my flo will ever finish
[11:17] <ogra_> it took 3min on the google logo, and now it sits at the animation for another 3 already
[11:18] <ogra_> ah, complaining helps :)
[11:18] <davmor2> ogra_: try opening the settings app please
[11:18] <ogra_> on it
[11:18] <ogra_> hmm
[11:19] <ogra_> startup animation hangs
[11:19] <ogra_> ah, not only that
[11:19] <ogra_> UI hangs completely
[11:19]  * ogra_ reboots 
[11:20] <davmor2> ogra_: thanks for confirming that is the unity8 lock issue :)
[11:21]  * ogra_ wonders why the boot takes so long 
[11:21] <ogra_> thats really annoying
[11:23] <ogra_> davmor2, it also happens if i start it from the apps scope
[11:23] <davmor2> ogra_: yeah I was starting it from the launcher which is why I said that :)
[11:26] <ogra_> wow, so that was 1.5min for the animation screen ... not good
[11:27] <psivaa> ogra_: http://paste.ubuntu.com/7774666/ is the syslog in one of the devices. the line 'NetworkManager[1654]: <warn> could not mark modem as powered: org.ofono.Error.Failed Operation failed' is there in one device when i tried phablet-network manyally
[11:27] <ogra_> (and my bootchart device currently has my dev-mode work on it, so i cant make a bootchart :( ... )
[11:27] <ogra_> psivaa, well, might be that flight mode is on ...
[11:28] <psivaa> ogra_: by default, soon after flashing?
[11:28] <ogra_> it shouldnt, but it probably is for you
[11:28] <psivaa> ogra_: ok, may be the network in the lab at that time was bad. let me reflash them
[11:29] <ogra_> psivaa, bug 1321627
[11:30]  * sil2100 goes for lunch
[11:30] <sil2100> o/
[11:30] <psivaa> ogra_: ok, sounds relevant. see a urfkill package update in 123 too
[11:31] <ogra_> yes, thats supposed to fix this bug ;)
[11:31] <ogra_> not sure it does ... my devices never hit that condition
[11:32] <ogra_> davmor2, bah, that bug makes my flo pretty unusable ... cant use it for 5min without it locking up
[11:32] <psivaa> seems only affect mako?
[11:32] <ogra_> well, we dont have other devices with WWAN
[11:32] <davmor2> ogra_: it's only become less stable on current yesterday it was the most stable :)
[11:32] <psivaa> ack, ack
[11:33] <ogra_> davmor2, oh, but it didnt hang hard this time ... after a few mins it started moving again
[11:33] <davmor2> ogra_: yeah it's a deadlock thing :)
[11:33] <ogra_> i wonder if that also makes the boot slow
[11:33] <ogra_> though the animation doesnt seem to get stuck
[11:33] <davmor2> ogra_: might
[11:43]  * psivaa -> reboot
[11:47] <mvo_> sil2100: aha, looks like you released landing-013 before I got the chance. I'm back now :)
[11:53] <davmor2> ogra_: if I do a ubuntu-device-flash --developer-mode and then do an ota will the ota then lose the developer-mode or is it a permanent setting?
[11:54] <davmor2> ogra_: I ask because obviously getting logs and stuff is important as is filing bugs from the device which I do via adb, but it is more important to be able to test ota's too :)
[11:54] <ogra_> davmor2, it should persist
[11:54] <ogra_> if it doesnt thats a bug
[11:55] <davmor2> ogra_: nice okay I'll keep that in mind when it lands then :)
[11:55] <psivaa> ogra_: davmor2: sil2100: the wifi network setup failed again on the next run with 3 more mako devices.
[11:56] <ogra_> well, did you check whats described in the bug ?
[11:59] <davmor2> psivaa: I've had no issues but I've not done a fresh install only ota.  I can look at a fresh install after but I need to get this silo testing done first.
[12:00] <ogra_> wow, thats a pretty large plane icon
[12:04] <ogra_> (in the new system-settings)
[12:05] <davmor2> ogra_: it is isn't it :)
[12:05] <davmor2> ogra_: but planes are big right so that's okay it's to scale :)
[12:06] <ogra_> heh, yeah
[12:08] <davmor2> ogra_: and for the cup final, who does Brazil support now, Argentina Who are local rivals and obviously they hate, or the team that knocked them out of the cup and completely humiliated them and they now hate :)  Good luck to both teams dodging those missiles as they are hurled ;)
[12:11] <bzoltan> ogra_: sil2100: I have a landing request in the line 22 what you really want :)
[12:11] <bzoltan> sil2100: it brings a permanent solution for the calendar, sudoku and all other failing apps caused by that bloody overlapping OSK
[12:13] <ogra_> davmor2, well, the whole stadioum cheered for germany in the second half ... so i suspect the final will be like a game at home for germany ;)
[12:31] <davmor2> ogra_: haha
[12:31] <brendand> psivaa, so will we get results for 123 today?
[12:31] <brendand> bzoltan, did i hear permenant solution?
[12:31] <sil2100> bzoltan: o/
[12:31] <psivaa> brendand: i dont think so, bug https://bugs.launchpad.net/ubuntu/+source/urfkill/+bug/1321627 is the cause
[12:32] <bzoltan> brendand: ohh yes :)
[12:32] <brendand> psivaa, that's been around for a bit though, right?
[12:32] <psivaa> brendand: yea but there was a new urfkill update for 123 and that's made the issue appear always
[12:32] <brendand> psivaa, ogra_ - make them back it out
[12:33] <brendand> psivaa, ogra_ - or can't we do that?
[12:33] <ogra_> brendand, lets wait for cyphermox_ to get up ... he owns it
[12:34] <ogra_> psivaa, does the workaround from the bug at least work for you ?
[12:34] <brendand> bzoltan, that's great
[12:35] <psivaa> ogra_: yes, it does manually the one in comment https://bugs.launchpad.net/ubuntu/+source/urfkill/+bug/1321627/comments/17
[12:36] <ogra_> psivaa, good , something at least
[12:36] <ogra_> we should probably put that into phablet-network anyway
[12:37] <ogra_> (assuming that yu want it to work immediately if you call phablet-network)
[12:53] <psivaa> ogra_: i've just tested the workaround in our provision script and it worked. if the actual fix for the issue is going to take long, may be we could apply the workaround
[12:53] <psivaa> but i'm not sure how determinant that workaround is
[12:53] <ogra_> psivaa, exactly my thought :)
[12:54] <psivaa> i.e. that will do the trick all the time
[12:54] <psivaa> :)
[12:54] <ogra_> well, it will force all rfkill settings to enabled :)
[12:56] <psivaa> hope that wouldn't open another can of worms :)
[13:30] <brendand> psivaa, btw is this affecting all CI testing?
[13:30] <brendand> psivaa, even merge request testing
[13:31] <psivaa> brendand: i dont know. could you paste a link to a jenkins job, failing?
[13:32] <brendand> psivaa, like this one for example: https://jenkins.qa.ubuntu.com/job/generic-click-autopilot-runner-mako/316/console
[13:32] <psivaa> brendand: ok, in a meeting now. will take a look at that in a bit
[13:33] <popey> seeing a bunch of tests failing in jenkins, where the toolbar doesn't appear. http://91.189.93.70:8080/job/generic-mediumtests-utopic/945 for example, I know music app guys have seen it too.
[13:33] <psivaa> brendand: but at the first look, it looks very much related
[13:33] <popey> brendand: & balloons: ^^ any idea?
[13:34] <brendand> popey, haven't seen that one
[13:44] <cyphermox_> psivaa: I'm flashing my n4 right now to try and reproduce, but it surprises me a lot that this would be happening
[13:45] <cyphermox_> urfkill has been on the devices for a long while already, and it always defaults to not be in flight mode, that hasn't changed
[13:47] <psivaa> cyphermox_: sorry, in a meeting. will ping you back in about ~30-40 mins
[13:58] <cyphermox_> psivaa: I'm going to need syslog and /var/lib/urfkill/saved-states from a system that shows the issue, before you do much more than run phablet-network
[14:25] <alf_> fginther: Hi! I need access to the CI train document, what do I need to do?
[14:25] <alf_> robru: ^^
[14:26] <fginther> alf_, yep, try robru
[14:26] <alf_> fginther: thanks
[14:27] <fginther> hopefully there is someone else around, it's a bit early for robru
[14:30] <bzoltan> sil2100: robru: brendand: the silo2 with the new UITK to fix test failures is good to go
[14:33] <bzoltan> thank you queuebot :)
[14:42] <sil2100> ;)
[14:47] <sil2100> hm, need to configure my irssi to ping also on notices
[14:52] <bfiller> sil2100: I need a silo for line 24 please
[14:52] <sil2100> mvo_: ^ can you handle this? :)
[14:52] <mvo_> sil2100: in a sec, just writing my activity report :)
[14:53] <sil2100> mvo_: ah ha! I'm actually doing that all the time throughout the week
[14:53] <mvo_> hm, maybe not: "Message details
[14:53] <mvo_> Cell reference out of rang" <- is the error I get
[14:53] <mvo_> sil2100: when I try to do that
[14:54] <sil2100> Uh?
[14:54] <sil2100> mvo_: when does that happen?
[14:55] <sil2100> mvo_: let me try instead
[14:55] <mvo_> sil2100: when I click on row 24 and assign silo
[14:55] <sil2100> Oh, wait, I see something wrong indeed
[14:56] <sil2100> mvo_: ok, wait a moment, the spreadsheet has a problem, need to fix that
[14:57] <fginther> sil2100, are you able to give access to the ci-train spreadsheet? alf_ was asking
[14:57] <sil2100> fginther: yes :) Who needs access?
[14:59] <fginther> sil2100, sent you a PM
[15:01] <robru> alf_, https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFVHQ3FuMDJGLUZCamJfSjYzbWh3Wnc#gid=0
[15:02] <alf_> robru: great, thank you
[15:03] <mvo_> sil2100: the spreadsheet has bad data? or is there a issue iwth the script? just curious
[15:04] <sil2100> mvo_: not sure yet... it seems there's either something wrong with the onchange trigger of the spreadsheet or the function doing the updates
[15:04] <sil2100> It didn't initialize the newly added rows
[15:04] <mvo_> ok
[15:07] <psivaa> cyphermox_: do you still need those logs that you asked earlier.. syslog and /var/lib/urfkill/saved-states from a just failed device
[15:07] <psivaa> ?
[15:07] <cyphermox_> nah, I think we'll be fine
[15:07] <bzoltan> robru: sil2100: do you what is going on with the UITK from the silo2?
[15:08] <robru> bzoltan, nope, i just woke up
[15:08] <bzoltan> robru: ahh, good morning. It will be a good day :) I know from experience, since I am almost done with it.
[15:09] <robru> sweet
[15:09] <robru> bzoltan, so it looks like it's in proposed but it's not listed in excuses. was it just published?
[15:10] <sil2100> Ignore those
[15:10] <bzoltan> robru:  that would be cool
[15:10] <sil2100> Had to fight the spreadsheet
[15:10] <sil2100> mvo_: ok, so it seems it was another unidentified bug from google
[15:10] <sil2100> mvo_: suddenly it stopped executing the function onChange of the spreadsheet
[15:10] <mvo_> urgh
[15:10] <mvo_> ok
[15:16] <elopio> ping Ursinha. Are there any news about this bug? https://bugs.launchpad.net/mir/+bug/1334767
[15:17] <Ursinha> elopio: uh, no. I need to work on that
[15:17] <popey> davmor2: can you reproduce https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1340248
[15:17] <davmor2> popey: I can have a look after this
[15:17] <popey> k
[15:19] <elopio> Ursinha: that would be nice. Please let me know if you need more information to get it solved.
[15:19] <Ursinha> elopio: okay, thanks
[16:01] <sil2100> hmmm
[16:02] <sil2100> ogra_: will you make it to the meeting today?
[16:03] <ogra_> sil2100, i can, yes, just came out of the allhands call, gimme a sec
[16:09] <elopio> sil2100: my browser is stuck and I can't click the microphone.
[16:09] <elopio> Just wanted to point out that this fixes the regressions from the toolkit release: https://code.launchpad.net/~fboucault/ubuntu-ui-toolkit/fix_overlap_osk/+merge/226286
[16:09] <elopio> sil2100: cool. Thanks :)
[16:12] <sil2100> grrrr
[16:13] <brendand> sil2100, and silo005 makes the mediaplayer-app issue go away apparently
[16:13] <sil2100> brendand: yay \o/
[16:13] <sil2100> brendand: great news then
[16:14] <brendand> sil2100, green image tomorrow :)
[16:15] <fginther> elopio, just an update on the keyring addition. The simple method didn't work (created files with the wrong permissions). I'm testing an alternate method between other tasks.
[16:15] <sil2100> brendand: weeeelll.... I wouldn't be *that* optimistic ;p
[16:18] <elopio> fginther: ok, thanks. I've left the branch linked to the bug report so we can confirm if it works.
[16:20] <davmor2> popey: I'm going to do a couple of things here.  1 Setup 2 appointments in Evolution so we can see what eds does with that by default, 2 See what android does by default with 2 appointments, can you test ios or do you know what it does already.  And what are you expecting, I'm assuming 1 alarm but 2 notify osd's right?
[16:25] <asac> popey: around?
[16:25] <popey> yes
[16:30] <popey> davmor2: i get one notification, short sound, then a few seconds later another one
[16:30] <robru> sil2100, is it known in image 123 that the network indicator doesn't list any wifi hotspots? I can't get online because it literally does not show any available APs
[16:31] <sil2100> robru: that might be caused by the issues that are blocking us from getting any autopilot test results in smoketesting
[16:31] <sil2100> In overall networking is b0rken so to say
[16:31] <robru> oh good
[16:32] <robru> oh but i'm connected after a reboot
[16:32] <sil2100> Yeah, it's a very strange race
[16:39] <sil2100> robru: it seems to only happen on the first boot after flashing
[16:39] <robru> sil2100, indeed. also there's two calculator apps on a freshly bootstrapped 123. one of them is nice and one is ugly, no icon even
[16:39] <sil2100> Uh oh!
[16:40] <sil2100> I remember a workaround for that
[16:47] <robru> sil2100, also, there's no scopes? what's going on?
[17:22] <davmor2> popey: confirmed
[17:31] <bzoltan> sil2100: robru: may I ask for a silo to the line 27?
[17:33] <popey> davmor2: can you try this please....
[17:34] <popey> Unplug phone, start music app, press play, let phone go dark, it doesn't continue to the next track, but does when you wake the phone.
[17:34] <popey> also does if phone is plugged in.
[17:37] <ahayzen> popey, i assume the devices in CI are plugged in so if we made a AP test it still would pass?
[17:37] <ahayzen> popey, therefore could this be added to the list of manual tests u guys do?
[17:38] <robru> bzoltan, sorry for the delay, was eating. you got silo 13
[17:39] <popey> yes, davmor2 ^
[17:39] <bzoltan> robru: thanks :) I had my dinner too ... ham&eggs, I missed that in the morning
[17:40] <greyback> hey, I want to add 2 source packages to silo6 - do I supply .changes file + friends, or do I push branches somewhere?
[17:41] <robru> greyback, we need an MP, and then put your MPs into the spreadsheet
[17:42] <robru> greyback, MPs are the currency of CI Train ;-)
[17:42] <greyback> robru: ok. One is for a brand new package though, how do I make an MR for that?
[17:43] <robru> greyback, ok, so is everything set up? you need a launchpad project with a name that matches the source package name, and you need the trunk branch set up so that you can `bzr branch lp:source_package_name` and that works
[17:44] <robru> greyback, and then you need to create a null merge for the first release, so branch lp:source_package_name, push it to lp:~/source_package_name/null, and then MP that branch into the trunk (the MP will be empty)
[17:46] <greyback> robru: thanks for explanation. Does that process also apply to lp:ubuntu/qtubuntu-gles (for example) I think need to create a twin called lp:ubuntu/qtmir-gles
[17:47] <robru> greyback, not sure if you need a gles twin, rsalveti is the guy to talk to about that
[17:47] <greyback> robru: I definitely need the gles twin. I just don't know how to get the packaging set up for it
[17:48] <plars> sil2100: ogra_: that urfkill workaround does not seem reliable: http://q-jenkins.ubuntu-ci:8080/view/Touch/view/Ubuntu%20Touch%20Smoke/job/utopic-touch-mako-smoke-daily/450/console
[17:48] <robru> greyback, oh... well look at some of the existing gles twins and see how they differ from their original sources, and then do that same thing to qtmir ;-)
[17:48] <greyback> robru: I've that done. I just don't know where to push the code really
[17:49] <robru> greyback, in that case I don't think it really matters, just make like lp:~/qtmir/qtmir-gles or something.
[17:49] <greyback> robru: oh ok. I thought it was important
[17:50] <robru> greyback, gles stuff is usually handled as source package uploads, which means the code comes from what's in distro, and then the patches are forward-ported to the latest release.
[17:50] <robru> greyback, well, having the gles package is important, but they're not tracked as strictly as the primary branches are in citrain.
[17:50] <t1mp_> hello
[17:50] <robru> hi
[17:50] <t1mp_> we are getting weird logs in our MRs, with failures not related to the MR itself
[17:50] <t1mp_> this one for example: https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/NewColors/+merge/225230
[17:50] <greyback> robru: so I saw. Ok, I think I know what to do, thanks!
[17:51] <t1mp_> gives these failures: https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-mako/2062/console
[17:51] <robru> greyback, you're welcome!
[17:51] <t1mp_> I see the same failures in other MRs also
[17:51] <t1mp_> I don't know why this is in the log - + bzr_cmd='bzr branch lp:~fginther/ubuntu-test-cases/mp-testing test-runner'
[17:51] <t1mp_> that branch is not related to the MR
[17:51] <t1mp_> robru: any ideas? Are the logs mixed up or the devices not clean?
[17:51] <sil2100> greyback: you can prepare a source package for the -gles counterparts and ask someone with upload rights to push those to the PPA
[17:51] <robru> t1mp_, heh, well it's fginther's branch, maybe he knows? ^^
[17:52] <sil2100> greyback: just be sure to add those to the silo config in the 'additional sources to land'
[17:52] <t1mp_> I get the same branch in the log of another unrelated MR https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/englishButtons/+merge/225610
[17:52] <t1mp_> fginther: ^
[17:54] <plars> looks racy dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner of name 'org.freedesktop.URfkill': no such name
[17:54] <plars> maybe yet another delay could work around it?
[17:54] <plars> psivaa: did you ever see that?
[17:55] <psivaa> plars: nope, i dint see that
[17:58] <psivaa> plars: yea, another delay after the first restart could fix that
[18:02] <psivaa> plars: the workaround that i tried was without the first step of enabling the flight-mode.
[18:04] <plars> psivaa: that doesn't seem related to the breakage here
[18:05] <plars> psivaa: it appears to just be racy
[18:06] <fginther> t1mp_, lp:~fginther/ubuntu-test-cases/mp-testing test-runner is the branch that contains the scripts to actually perform the jenkins job. The problem causing the testing to fail is probably https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1340217
[18:06] <plars> psivaa: I'll experiment a bit
[18:07] <psivaa> plars: i thought http://pastebin.ubuntu.com/7776433/ suggesting that urfkill not fully up before we do run the '/usr/share/urfkill/scripts/flight-mode 0' command
[18:07] <t1mp_> fginther: it says "Fix Released". Does that mean if we run CI again it will work now?
[18:07] <psivaa> but leaving it to you :)
[18:07] <psivaa> plars: thanks
[18:09] <fginther> t1mp, no, it won't show up automatically until the next image. let me see if I can work it in somehow
[18:10] <t1mp> fginther: okay, thanks
[18:11] <popey> cjwatson: seen this when installing a click? http://paste.ubuntu.com/7776458/
[18:11] <fginther> plars, psivaa, looks like you have a workaround for the touch network bug?
[18:12] <psivaa> fginther: the workaround appear to meet some race related issues.
[18:13] <fginther> psivaa, ack
[18:16] <plars> fginther: wip
[18:33] <pmcgowan> hi anyone can help us with why CI keeps failing here https://code.launchpad.net/~jonas-drange/ubuntu-system-settings/1211804-allow-technology-preference/+merge/226125
[18:35] <josepht> cjohnston: ^
[18:36] <cjohnston> ack
[18:36] <bzoltan> It is sooooo waste of time to build stuff for powerpc. The hours we loose on that can add up two dozen of massive regression what a powerpc build will never prevent. Cost-benefit, ROI ... please drop powerpc builds
[18:41] <cjohnston> pmcgowan: it appears to be the networking issue
[18:42] <pmcgowan> cjohnston, pretend I don't know what that is ;)
[18:43] <cjohnston> pmcgowan: there are more details in todays landing email, but essentially bug #1340217
[18:43] <pmcgowan> oh foo
[18:43] <pmcgowan> kenvandine, ^^
[18:44] <kenvandine> ugh
[18:44] <kenvandine> ok, thanks
[18:46] <cjohnston> pmcgowan, kenvandine I don't know the entire process, but since it's fix released, maybe someone could kick off a new image?
[18:48] <pmcgowan> not sure awe_ rsalveti ^^?
[18:50] <rsalveti> did the package land in release already?
[18:50] <robru> rsalveti, yeah, 1 hour ago apparently
[18:51] <plars> ogra_: robru: can we get a new image if that nm bug is fixed then?
[18:51] <rsalveti> I can kick a new iamge, do we want that now?
[18:51] <rsalveti> or wait a few more hours?
[18:51] <plars> I'm still trying to make the workaround work properly, and having lots of problems with it
[18:51] <plars> rsalveti: oh yeah, you could do that too :)
[18:51] <robru> rsalveti, yeah I think it's a good idea to kick an image. cron will do it in ~8 hours, I doubt anybody wants to wait that long
[18:51] <rsalveti> alright, doing that now
[18:51] <davmor2> popey: play an album and just leave it.  It plays the second track after about a minute so I think the issue is the way the Qt loop handler is working maybe in qt5.3
[18:51] <awe_> pmcgowan, whatsup?
[18:52] <pmcgowan> awe_, nm
[18:52] <pmcgowan> awe_, talking about an image to pick up the urfkill fix
[18:52] <awe_> rsalveti, +1 on new image
[18:52] <davmor2> popey: I'm wondering if it is the same issue as the alarm where the clock leaps forward 5 minutes when the alarm goes off
[18:52] <awe_> we can only reliably reproduce when flashing a new image
[18:52] <cyphermox_> yes, I was about to kick it
[18:52] <plars> psivaa: in that case, I'm going to revert the urfkill workaround rather than try to make it work reliably
[18:52] <popey> davmor2: it works for you with the phone disconnected?
[18:53] <awe_> cyphermox_, kick the image?
[18:53] <psivaa> plars: go ahead. i think i mistimed it :)
[18:53] <davmor2> popey: yeap but there is a huge delay between track 1 ending and track 2 playing
[18:53] <popey> maybe I'm not patient enough
[18:53] <popey> ahayzen: ^^
[18:53] <davmor2> popey: as in at least a minute
[18:54] <plars> psivaa: it's more than that I think, I was able to get farther with a delay, but phablet-network failed still when running in phablet-config... I don't think it was as simple to workaround as we hoped :(
[18:54] <cyphermox_> awe_: yeah
[18:54] <imgbot> [18:54] <psivaa> plars: ohh, ack. ack
[18:56] <davmor2> popey: track 3 plays almost straight after track 2 though
[18:56] <davmor2> ahayzen: ^
[18:56] <davmor2> I don't know if that is the case if you wake the  system though I've just left it while I was doing other stuff
[18:57]  * popey goes for dinner
[18:57] <popey> back later
[19:01] <stgraber> robru: += and so does queuebot :)
[19:02] <robru> stgraber, great work, thanks again ;-)
[19:02] <stgraber> :)
[19:02] <stgraber> btw, so far so good, queuebot hasn't been complaining in the logs since I merged and restarted it this morning.
[19:02] <robru> stgraber, *phew* ;-)
[19:03] <robru> stgraber, I /part'ed #ubuntu-ci-choo-choo... ain't never looking back!
[19:04] <robru> stgraber, btw, lxc... I freaking love it! It's the easiest way to play with juju, but even on it's own it's also totally awesome.
[19:05] <robru> stgraber, seems to me like lxc is the easiest way to bring up an ubuntu+1 chroot... juju can't deploy utopic, you have to deploy trusty and then do-release-upgrade, it's terrible ;-)
[19:07] <cjwatson> popey: no, not going to look in the evening, please file a bug
[19:09] <popey> cjwatson: will do
[19:10] <stgraber> robru: yeah, "sudo lxc-create -t download -n utopic-dev -- -d ubuntu -r utopic -a amd64" is pretty simple and pretty quick (well, we are working on making it even simpler as it's kinda long :))
[19:12] <robru> stgraber, huh? I just did 'lxc-create -t ubuntu -n foobar' and it sucked down a fresh utopic install for me... pretty magical
[19:15] <stgraber> robru: ah yeah, the ubuntu template will debootstrap the same release you've got on your machine, but it's not terribly fast.
[19:15] <stgraber> robru: if you do lxc-create -t download -n foobar, you'll see a list of pre-built images we build daily and that can be grabbed and unpacked much much faster than the ubuntu template can debootstrap (assuming you've got fast internet)
[19:16] <robru> stgraber, right, it wasn't super fast, but just before that I had done a 'do-release-upgrade -d' from trusty to utopic inside a juju-controlled LXC and it was even worse, so I didn't mind the extra time because it worked so well ;-)
[19:17] <robru> stgraber, ah, you've got utopic images, nice ;-)
[19:19] <popey> fginther: http://s-jenkins.ubuntu-ci:8080/job/weather-app-click/215/console  any idea what's going on there?
[19:20] <fginther> popey, one moment
[19:27] <robru> stgraber, was just reading https://www.stgraber.org/2014/02/09/lxc-1-0-gui-in-containers/ thanks for that as well ;-)
[19:27] <robru> stgraber, is there any way to run a windowed X session from inside an LXC? Basically I want to bring up a whole unity desktop inside a trusty LXC running on my utopic host...
[19:29] <stgraber> robru: accelerated may be tricky, but just spawning a separate display is doable with something like Xnest or Xephyr
[19:29] <robru> stgraber, hmmm, interesting... ;-)
[19:36] <ahayzen> davmor2, i'm back.... so your saying it works?
[20:04] <bfiller> robru: silo request for line 23 when you get a chance
[20:05] <robru> bfiller, yeah, hey... ^^ ;-)
[20:05] <robru> bfiller, does your IRC client not highlight channel notices or something?
[20:08] <bfiller> robru: yeah, thought I still need to ping you. all automated now?
[20:08] <bfiller> oh
[20:08] <bfiller> didn't read it carefully
[20:08] <bfiller> sorry
[20:09] <robru> bfiller, well you can ping me if nothing happens ;-) but I just found it funny that queuebot pinged you to say the silo was ready, and then a minute later you pinged me asking for the silo.
[20:09] <bfiller> robru: right - sorry I didn't read it
[20:10] <robru> bfiller, no worries!
[20:10] <robru> bfiller, just growing pains, we made some changes to the bot recently to make it more responsive
[20:11] <robru> bfiller, so I can see how you wouldn't have expected it to be ready already!
[20:18] <robru> fginther, heya, do you have any clue where I might find the documentation for this file format: http://bazaar.launchpad.net/~cupstream2distro-maintainers/cupstream2distro/trunk/view/head:/citrain/manual/jenkins-templates/prepare-silo.xml.tmpl ? I've been googling for an hour and I'm totally stumped.
[20:18] <robru> (like upstream jenkins documentation)
[20:19] <fginther> robru, I don't know of any documentation and the format varies depending on what plugins are in use and installed
[20:20] <robru> fginther, yeah, that's the problem. I need to add a trigger but I have no idea what the trigger tag name would be called
[20:20] <fginther> robru, what I do is generate the job I'm looking for in jenkins itself, pull the config.xml and then replace the templatable parts
[20:20] <robru> fginther, if I make a change to the jenkins config, is there a way to export that config into this xml format to see what tags it uses?
[20:20] <robru> fginther, right, how do I do that? ;-)
[20:21] <fginther> the xml file is availble by just adding '/config.xml', for example - https://ci-train.ubuntu.com/job/prepare-silo/config.xml
[20:22] <robru> fginther, you are the man! thanks a ton ;-)
[20:22] <fginther> robru, so you could copy that job to prepare-silo-robru, make your changes there, and then extract the xml
[20:23] <robru> fginther, it already has my changes, I just need to push a branch so that they don't get clobbered next time they get deployed
[20:23] <fginther> popey, fixed, a new weather app is built
[20:23] <fginther> ahh
[20:24] <imgbot> [20:24] <imgbot> [20:25] <rsalveti> pmcgowan: awe_: 124 is out
[20:25] <rsalveti> plars: ^
[20:25] <awe_> cool, just ran 'ubuntu-device-flash' two seconds ago...
[20:25] <awe_> synchronicity
[20:26] <plars> rsalveti: cool, I already updated the CI scripts to take out the workaround, I'll keep an eye on the results
[21:06] <robru> tedg, you're conflicting with silo 8
[21:06] <tedg> robru, Who doesn't conflict with silo 8? :-)
[21:07] <tedg> robru, I thought that silo was still a WIP, no?
[21:07] <robru> tedg, well, none of bfiller's silos conflicted with silo 8! I ain't sayin, I'm just sayin...
[21:07] <robru> tedg, so you want me to override that then?
[21:08] <tedg> robru, Yeah, I think so. I think that's still being put together.
[21:09] <robru> tedg, ok, you got silo 10
[21:09] <tedg> Woot!
[21:09] <tedg> Thanks robru
[21:10] <robru> tedg, you're welcome!
[21:10] <Guest36942> fginther, could you help me with that? https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-mako/2083/console
[21:12] <dobey> robru: hi. silo 014 is tested now. i think it's good to land
[21:14] <fginther> Guest36942, this is caused by https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1340217, a new image is being built
[21:15] <fginther> renato__, actually, it says the new image is ready now
[21:15] <renato__> fginther, thanks
[21:15] <renato__> I will trigger a new build
[21:47] <cyphermox_> psivaa: robru: fginther: so, we're good with 124?
[21:48] <cyphermox_> seems to me like it's working..
[21:48] <robru> haven't tested it yet
[21:50] <psivaa> cyphermox_: smoke test side appear to be OK, the network setup after the flashing appears to have gone good
[21:50] <cyphermox_> cool
[21:55] <robru> cyphermox_, just flashed, seems fine
[22:03] <cyphermox_> great
[22:22] <popey> networking seems broken on 124 here
[22:22] <popey> cyphermox_: ^
[22:22] <popey> my phone booted with network disconnected, pull down indicator, flight mode is off
[22:22] <popey> if i toggle it on, it flips off again
[22:23] <popey> /dev/mmcblk0p23                 5.7G  5.4G     0 100% /home
[22:23] <popey> bah