[07:47] <Saviq> cihelp, hey, can anyone here reconfigure a silo for me?
[08:26] <ogra_> "<Fishscene> I want to give a HUGE thank you to whoever gave the greenlight for Mir 0.1.4 to be in the Ubuntu touch image."
[08:27] <ogra_> i want to frame that for my wall (or at least have a T-Shirt with it) !!!
[08:46] <tvoss> popey, good morning
[08:49] <popey> tvoss: good night ☻
[08:50] <tvoss> popey, ah yeah, you are in a different part of the world
[08:50] <tvoss> popey, can I ask you to test something on mako for me?
[09:07] <psivaa> Saviq: hello, do you know where that's configured. (or a link to the job)
[09:07] <psivaa> my guess is that this needs access to lillypilly
[09:08] <Saviq> psivaa, Mirv is taking care of me now, thanks
[09:08] <psivaa> Saviq: great. thanks
[09:38] <didrocks> http://ci.ubuntu.com/smokeng/trusty/touch/mako/168:20140206.2:20140115.1/6487/music-app-autopilot/
[09:38] <didrocks> ogra_: psivaa ^
[10:01] <psivaa> ogra_: i just tried one test after installing uidmap on 169, but the lxc-autostart crash still occurs.
[10:06] <ogra_> psivaa, thanks, then it sits deeper down somewhere, i'lkl talk to stgraber ... (i dont think we ever used lxc-autostart so worst case i will just disable the upstart job)
[10:06] <psivaa> ogra_: ack
[10:41] <sil2100> hm, mediascanner2 and hud don't seem to be the ones causing the music-app problem, chasing down further
[10:43] <sil2100> I have another candidate
[10:57] <tsdgeos> guys, any idea what this error is http://s-jenkins.ubuntu-ci:8080/job/autopilot-testrunner-otto-trusty/2647/console ?
[10:57] <tsdgeos> vanguard is not here :D
[10:58] <sil2100> tsdgeos: poke cihelp ^
[10:58] <tsdgeos> there's no cihelp ?
[10:58] <psivaa> tsdgeos: sil2100: let me take a look
[10:59] <psivaa> tsdgeos: bzr: ERROR: Invalid http response for https://xmlrpc.launchpad.net/bazaar/: Unable to handle http code 502: Bad Gateway
[10:59] <didrocks> tsdgeos: the keyword, from what I know, ping everyone on the ci team (if there is no vanguard)
[10:59] <tsdgeos> ahhh
[11:00] <tsdgeos> psivaa: yes i saw that too, but is that something that will heal itself or does anyone need to act on that
[11:01] <vila> tsdgeos: lots of timeouts on lp this morning, 502: Bad Gateway is a known fallout
[11:01] <tsdgeos> ok
[11:01] <tsdgeos> so it'll autoheal
[11:01] <tsdgeos> tx
[11:01] <vila> tsdgeos: lp will probably recover, depending on when this happened, you may have to re-run your job
[11:01] <psivaa> tsdgeos: the issue normally goes away after some time if you try. i've kicked off one now
[11:06] <tsdgeos> ok, tx
[11:13] <robru> Saviq, ping about maguro unity8 failure http://ci.ubuntu.com/smokeng/trusty/touch/maguro/168:20140206.2:20140115.1/6490/unity8-autopilot/744272/ are you aware of this? can it be fixed?
[11:15] <Saviq> robru, no, didn't have time to look at it, but for the last few days a random test was failing almost every image
[11:16] <Saviq> robru, so it's rather weird
[11:16] <robru> Saviq, yeah, we're hoping to resolve these random failures. i don't understand them either
[11:16] <robru> Saviq, some kind of timeout or race condition i guess
[11:17] <Saviq> robru, also, nothing changed in unity8 anywhere around that code, I'd like to check whether the autopilot release had anything to do with it
[11:18] <robru> Saviq, oh good idea. we did have an autopilot regression recently that needed to be reverted, this could be similar
[11:18] <robru> didrocks, ^
[11:22] <robru> davmor2, can you try running unity8-autopilot on maguro, see if you can reproduce http://ci.ubuntu.com/smokeng/trusty/touch/maguro/168:20140206.2:20140115.1/6490/unity8-autopilot/744272/
[11:38] <robru> Saviq, so the decision from didrocks is that we can't land unity8 until these failures are resolved. it's really important to us to get maguro working because it'll put us in better shape for when the emulator becomes the primary target
[11:38] <didrocks> robru: Saviq s/resolved/figured out the cause/
[11:39] <Saviq> since when the fuck is maguro a target again
[11:39] <Saviq> I'm getting tired of this really
[11:40] <didrocks> Saviq: have you tried on the emulator? I guess robru is doing it now
[11:40] <Saviq> didrocks, I don't have time for this
[11:41] <Saviq> didrocks, I'm trying to deliver everything that we need for MWC
[11:41] <didrocks> Saviq: I understand that, we you need to understand that we try to not build technical debts
[11:41] <Saviq> can we do the "when emulator becomes the primary target" when it actually does become a primary target? and not a week before MWC?
[11:42] <didrocks> Saviq: I guess that's something to discuss at the management level. If they agree to build technical debts, that's ok then, not a decision that you or I should take
[11:43] <didrocks> Saviq: so, to help your team, I asked robru to test on the emulator
[11:43] <Saviq> didrocks, also, IIUC it's emulator on x86 that we'll be targetting, not the QEMU one, which is simply unusable and uncomparable to anything that we plan to ship on?
[11:43] <didrocks> Saviq: I have no idea/didn't hear any decision on that particular one
[11:44] <didrocks> but yeah, I agree that we should target as emulated should just be the slowest device that we'll ship
[11:44] <didrocks> (and not slower or quicker)
[11:58] <robru> thostr_, ping about silo 5 upstart app launch. did you finish testing it? can i publish?
[12:01] <thostr_> robru: we did a first round of testing and it was ok, but I want to give it another shot
[12:02] <robru> thostr_, ok great. just ping me when you're ready to publish. i'm here for 6 more hours
[12:02] <robru> didrocks, http://162.213.34.102/job/landing-006-2-publish/lastSuccessfulBuild/artifact/packaging_changes_ubuntu-keyboard_0.99.trunk.phablet2+14.04.20140206-0ubuntu1.diff
[12:02] <thostr_> robru: but you can give us a silo for 54
[12:03] <robru> thostr_, sorry, in a sec
[12:06] <Mirv> didrocks: it seems I got the (familiar) backtrace bug #1277480. sorry for being carried away with Qt, I should have started with this. it seems the proposed fix unity-mir branch is still to be released, bug 1271879
[12:08] <davmor2> robru: possibly but not till after Lunch I got my hands full till then
[12:09] <robru> davmor2, ok thanks
[12:10] <davmor2> robru: oh actually it's just the one set let me see if I can set that off now and then I'll carry on with the stuff I need to get on with
[12:10] <robru> davmor2, great, thanks
[12:10] <robru> didrocks, http://162.213.34.102/job/landing-010-2-publish/lastSuccessfulBuild/artifact/packaging_changes_messaging-app_0.1+14.04.20140206-0ubuntu1.diff
[12:15] <didrocks> Mirv: hum, this was released
[12:15] <didrocks> IIRC
[12:15] <robru> thostr_, ok, just looking at 54 now. since it's a new package i'm going to review the packaging a bit before starting the silo.
[12:15] <didrocks> let me check
[12:16] <didrocks> Mirv: ah no, it's in a silo
[12:16] <didrocks> landing-004
[12:17] <didrocks> Mirv: ok, ignore it for now then, thanks!
[12:25] <robru> didrocks, please preNEW https://code.launchpad.net/~robru/unity-scope-scopes/trunk/+merge/205352 ;-)
[12:25] <Mirv> didrocks: yeah, still in a silo
[12:26] <sergiusens> Mirv, have you tried the qt 5.2 to upgrade with the latest image?
[12:26] <sergiusens> didrocks, can we enhance trains (not today), to work with either packaging branches and/or udd?
[12:30] <didrocks> sergiusens: as long as bzr bd works, yeah, it should work (but we need to ensure that the bot can push)
[12:30] <didrocks> sergiusens: let's see that next week if you don't mind
[12:31] <robru> thostr_, ok, for line 54 please update the description (explain what the package is, and mention that it's a new package. then i will make a silo for you)
[12:31] <thostr_> mhr3 ^^^
[12:32] <sergiusens> didrocks, yeah, no rush; but getting a as close to image build is awesome IMO and reduces the personal build effect (and covers much more hw)
[12:33] <mhr3> robru, done
[12:33] <robru> mhr3, thanks
[12:34] <didrocks> sergiusens: more than agreed
[12:34] <didrocks> sergiusens: we are going over the silo with the team btw to attribute (you should get one soon)
[12:34] <Mirv> sergiusens: the last I checked was yesterday, but no I haven't yet checked how the qtmultimedia-touch upload affects the upgrade. I'd like to test that ASAP.
[12:34] <didrocks> sergiusens: as I'm not around on Monday and Tuesday, I try to ensure the service doesn't stop :)
[12:34] <robru> mhr3, thostr_: ok, line 54 got silo 002. go ahead with building & testing
[12:35] <robru> mhr3, no wait hang on
[12:36] <sergiusens> didrocks, thanks
[12:37] <sergiusens> Mirv, great, sorry for the delays, had symbol issues on the no code change rebuild ;-)
[12:38] <Mirv> sergiusens: can you clarify a bit if you intend qtmultimedia-touch 5.1.1 to be still used with Qt 5.2, or will you rebase it to 5.2? if the former, I should probably rebuild it against Qt 5.2 in the PPA (have you tried it?)
[12:38] <sergiusens> Mirv, I will provide an upgrade path to whatever Qt version you use
[12:39] <Mirv> sergiusens: what would be the quickest path to getting working multimedia in the Qt 5.2 PPA now? I guess I could simply try to upload the qtmultimedia-touch as is to there? https://launchpad.net/~canonical-qt5-edgers/+archive/qt5-beta2
[12:39] <robru> mhr3, thostr_: sorry for the false start, silo 003 is ready to go, please begin build now
[12:39] <sergiusens> Mirv, given that the -touch package was supposed to die 2 months ago I didn't provide an upgrade path; so I need to write prerm's for diversion first and then rewrite all the diverts for the new multimedia package
[12:39] <Mirv> sergiusens: because I believe a rebuild is always needed
[12:40] <Mirv> sergiusens: yeah.. too bad it didn't agree to die yet :)
[12:42] <sergiusens> Mirv, let me try the upgrade path later today and see how to solve it (if there's a delta)
[12:42] <Mirv> sergiusens: thanks!
[12:49]  * ogra_ hugs cyphermox_ ... thanks for the lxc fix
[12:51] <didrocks> ogra_: we are almost back to everything fixed!
[12:51] <ogra_> yeah, i see that :)
[12:51] <didrocks> just this random unity8 failure that needs investigation
[12:52] <sil2100> music-app failures should be no more \o/
[12:52] <ogra_> yay
[12:53] <robru> sergiusens, silos 11 and 12 for landings 60 and 61, respectively.
[12:56] <sergiusens> ty
[12:59] <robru> mhr3, silo 3 assigned for landing 54, ready to build.
[13:00] <mhr3> robru, thx, building
[13:00] <robru> yw
[13:10] <psivaa> didrocks: no big surprises on maguro with 169 except rssreader failures probably caused by the unity8 crash in http://ci.ubuntu.com/smokeng/trusty/touch/maguro/169:20140207:20140115.1/6491/ubuntu-rssreader-app-autopilot/
[13:13] <Saviq> robru, hey, any luck reproducing with the emulator?
[13:13] <robru> Saviq, no sorry. had a few false starts with it but it's only just started running in the last 5 minutes or so
[13:13] <Saviq> robru, ok thanks
[13:14] <robru> davmor2, any word on maguro unity8 tests?
[13:14] <davmor2> robru still running
[13:14] <Saviq> robru, FWIW, when I ran the unity8 suite in the emulator, the emulator segfaulted at some point
[13:14] <robru> Saviq, haven't seen a segfault yet, but it took me a couple tries before it would even boot at all
[13:18] <Saviq> robru, do you know if emulator is supposed to work on proprietary drivers at all?
[13:19] <robru> Saviq, no idea, sorry. just poking at this because didrocks told me it was a priority
[13:19] <Saviq> robru, ok thanks
[13:22] <davmor2> robru: grrr phone locked up
[13:23] <robru> davmor2, no worries. you can probably restart it and finish before my emulator finishes ;-)
[13:24] <davmor2> robru: right reboot done starting again
[13:25] <davmor2> robru: I'm off for lunch in a minute I'll just leave it running
[13:25] <robru> davmor2, sure, thanks
[13:33] <robru> Saviq, yep, segfault :-/
[13:34] <Saviq> didrocks, ↑ unity8 ap tests + emulator == emulator segfault
[13:57] <didrocks> Saviq: waow… :/
[14:00] <ChrisTownsend> josepht: Hi, is there an issue with the Unity7 automerger?  We've had an MP approved since yesterday that has not merged yet: https://code.launchpad.net/~attente/unity/hud-controller-gvariant-type-error/+merge/204893
[14:01] <josepht> ChrisTownsend: looking
[14:01] <ChrisTownsend> josepht: ThankS
[14:09] <plars> Laney: http://ci.ubuntu.com/smokeng/trusty/touch/mako/169:20140207:20140115.1/6492/ubuntu-system-settings-autopilot/ system settings tests are getting some failures occasionally and some crashes - any ideas?
[14:10] <josepht> ChrisTownsend: it looks like the unity autolanding job is running now, once it's done I'll check on that MP and run it manually if needed.
[14:10] <Laney> plars: seb128 is looking at it because I can't reproduce
[14:10] <ChrisTownsend> josepht: Ok, cool, thanks for looking.
[14:10] <seb128> seems like an autopilot issue to me
[14:10] <seb128> plars, ^
[14:11] <seb128> it's hitting an utf error in autopilot
[14:14] <thostr_> robru: line 36 should be good for landing now
[14:17] <plars> seb128: I don't think we see that in the other tests, but they may be decode()ing around it. Might be worth asking the QA team if they have some best practices there, or opening a bug against autopilot
[14:17] <plars> seb128: what about the crashes though?
[14:19] <seb128> plars, I didn't look at those yet
[14:19] <robru> thostr_, ok thanks. we are waiting for lxc to hit the archive, then we will kick an image build, then publish yours.
[14:21] <plars> seb128: the lxc crash seems to be happening on every test
[14:21] <plars> didrocks: ^
[14:21] <didrocks> plars: yeah, we already know it and we have a fix publishing right now :)
[14:22] <plars> seb128: the dbus one is unique though I think, and new to this build. The previous two builds went through the system settings test without hitting it, it seems
[14:23] <seb128> Laney, plars: http://paste.ubuntu.com/6891523/
[14:27] <davmor2> robru: 1 failure checking if it is the same
[14:28] <robru> davmor2, can you pastebin it?
[14:28] <Laney> how can lxc and dbus crashing be the fault of system-settings?
[14:29] <ogra_> Laney, lxc-autostart ?
[14:29] <ogra_> we dont use it so it shouldnt have any ill effect
[14:29] <davmor2> robru: http://paste.ubuntu.com/6891542/
[14:31] <tedg> thostr_, Is there anything blocking publishing the UAL silo?
[14:31] <robru> davmor2, ok, that's not the same one from today but it is the same one from yesterday. http://ci.ubuntu.com/smokeng/trusty/touch/maguro/167:20140206.1:20140115.1/6480/unity8-autopilot/741839/
[14:31] <robru> davmor2, can you run it again to see if it's reproducible, or if it's flaky?
[14:31] <davmor2> robru: will do
[14:31] <robru> Saviq, ^
[14:31] <robru> davmor2, thanks
[14:32] <robru> tedg, we are waiting for lxc to hit the archive, then we will kick an image build, then publish UAL.
[14:33] <tedg> robru, Uhg, okay.  Can we allocate another silo to get that one building then?  Or does the locking stop us?
[14:34] <tedg> Can we run the merge step without publish?
[14:34] <robru> tedg, er, which? lxc is already in -proposed, it will be done soon, we just want an image built before we release the new UAL
[14:34] <robru> didrocks, ^
[14:36] <didrocks> tedg: once we publish, the branch is pushed to ~ps-jenkins/<component_name>/trusty-proposed
[14:36] <didrocks> so you will be able to base on that
[14:36] <didrocks> robru: FYI ^
[14:37] <robru> didrocks, http://162.213.34.102/job/landing-005-2-publish/lastSuccessfulBuild/artifact/packaging_changes_upstart-app-launch_0.3+14.04.20140206-0ubuntu1.diff please ack
[14:37] <tedg> didrocks, Well, I don't need to base anything, I was more worried about starting to kick off the next silo.
[14:38] <robru> tedg, it's ok, we are publishing it now
[14:44] <robru> tedg, ok, we kicked the publish job. once it hits the archive then thostr_ can do the 'merge and clean' step.
[14:45] <tedg> robru, Great, thanks!
[14:45] <tedg> Filling out line 62 now :-)
[14:45] <plars> didrocks: was there a 20140107.1bad android build?
[14:45] <plars> '20140107.1bad' - exactly that is
[14:46] <Saviq> robru, davmor2, are you looking any more into the unity8 failure, or do we need to take over?
[14:47] <seb128> plars, so the u-s-s issues are between ubuntu-download-service and autopilot
[14:47] <seb128> plars, the service seems to output random chars including non utf8 ones
[14:47] <seb128> plars, and autopilot tries to log the output and doesn't handle the non utf chars
[14:47] <robru> Saviq, well I don't have any ability to check it with emulator crashing. i'm just waiting for davmor2 to have a second run. would appreciate if you could look at it as well
[14:48] <davmor2> Saviq: I'm running the tests again as I got yesterdays error rather than todays, But I've also had the phone lock up on me too
[15:14] <dpm> hi josepht - I've noticed Jenkins is not running on https://code.launchpad.net/~mzanetti/reminders-app/fix-fetching-notes/+merge/205372 , do you have any idea how we can get it to review and land the branch?
[15:14] <josepht> dpm: looking
[15:16] <dpm> cool, thanks
[15:19] <cjohnston> josepht: dpm its currently running
[15:24] <plars> didrocks: so is there another image just about to drop? should we wait before transitioning the ci jobs for that to happen or are we good to go in just a bit here?
[15:24] <didrocks> plars: yeah, it should be nearly built now
[15:24] <didrocks> so maybe wait after that one
[15:24] <plars> didrocks: ok
[15:31] <dpm> josepht, cjohnston, so does that mean that there is nothing else to be done to get the tests run and the autolanding done? Did it not use to run every 15 minutes?
[15:31] <cjohnston> dpm: all depends on the queue
[15:31] <cjohnston> its running
[15:31] <thostr_> robru: could I get another silo for line 62? QA wants to have that ASAP to get app benchmarking
[15:34] <robru> thostr_, checking...
[15:37] <robru> thostr_, just need you to merge and clean silo 5 first.
[15:38] <dpm> thanks cjohnston
[15:39] <plars> didrocks: did you see my earlier question about the android image with 1bad at the end?
[15:39] <plars> didrocks: cjohnston is seeing a strange entry in the dashboard
[15:39] <didrocks> plars: yeah, I have no idea about this though, sorry :/
[15:44] <robru> thostr_, so, I can assign that silo after 'merge and clean' is done, but it will be a little while before we can approve another UAL publish due to the size of this diff and the recent regression (we need to get a green image before we can risk another big UAL regression)
[15:46] <balloons> ping josepht
[15:46] <josepht> balloons: pong
[15:46] <thostr_> robru: just initiated merge and clean
[15:47] <balloons> josepht: it seems like the jenkins output from the merge proposal for this merge doesn't appear on the proposal itself; https://code.launchpad.net/~carla-sella/music-app/fix-test-create-playlist-from-songs-tab/+merge/205261
[15:47] <balloons> you can see it tried to build it here; http://91.189.93.70:8080/job/reminders-app-trusty-amd64-ci/191/
[15:49] <davmor2> robru, Saviq: http://paste.ubuntu.com/6891973/ second result
[15:49] <thostr_> robru: silo is clean... if I can get a new silo than we can start building and testing the new bunch of UAL merges...
[15:50] <robru> thostr_, yep, on it.
[15:50] <robru> thostr_, thanks
[15:50] <robru> davmor2, ok, so that matches today's failure. so on one run you got yesterdays failure and one run you got todays. great ;-)
[15:50] <thostr_> robru: can you also reconfigure silo1? we had a packaging problem which we fixed now..
[15:51] <davmor2> robru: I'm assuming it is down to falky maguro I can run it again if you want and see which pick and mix we get this time :)
[15:51] <josepht> balloons: looking
[15:52] <robru> davmor2, I guess, please try downgrading autopilot to 1.4+14.04.20140123.1-0ubuntu1 and re-running.
[15:53] <robru> thostr_, ok, landing 62 got silo 5
[15:53] <robru> thostr_, sorry, what's wrong with silo 1? you just want all the packages there rebuilt?
[15:53] <thostr_> robru: something with package split or so...
[15:54] <thostr_> robru: or split build rather
[15:54] <robru> thostr_, i don't understand the problem though. is it really necessary to purge the whole ppa and start over completely, or can a rebuild solve the issue?
[15:54] <thostr_> robru: so, added a MP for this...
[15:54] <thostr_> robru: I thought we need to reconfig if a new MP is added, NO?
[15:55] <thostr_> didrocks: ^^^
[15:55] <josepht> balloons: it looks to be related to this http://91.189.93.70:8080/job/generic-mediumtests-trusty/1160/console
[15:55] <robru> thostr_, you're right, I'm still learning ;-)
[15:55] <davmor2> robru: hmmm how and I'll see if I have time?
[15:55] <thostr_> robru: yw
[15:55] <didrocks> thostr_: yeah, robru is handling it, just gave him instructions :)
[15:55] <thostr_> :)
[15:55] <thostr_> just let me know once it's rconfigured
[15:56] <robru> davmor2, well you'd have to go to https://launchpad.net/ubuntu/+source/autopilot/1.4+14.04.20140123.1-0ubuntu1 and download the binary packages for your device
[15:56] <davmor2> didrocks: we looking at promoting anything today it looks like om26er is off as his wife just gave birth
[15:56] <robru> thostr_, ok, so the new MP, is it listed in the landing ask already?
[15:56] <thostr_> robru: yes
[15:56] <robru> thostr_, ok thanks
[15:56] <didrocks> davmor2: yeah, I don't think we will TBH
[15:57] <didrocks> davmor2: but dogfooding on 170 would be appreciated
[15:57] <davmor2> robru: ah right I thought there might of been a magic command that would do it.
[15:58] <davmor2> didrocks: will do need to fresh flash the devices so might be  a while I also need to do some apps from the queue :)
[15:58] <robru> davmor2, unfortunately not. although sometimes I find it easier to downgrade the image and then selectively update packages between images (this way you avoid manual package downloads).
[15:59] <balloons> josepht: yes, it seems to have build issues; I left a note in the MP that there were merge conflicts (though launchpad doesn't seem to think so). Regardless of what the issue is for the build, jenkinsbot should put a comment on the merge proposal saying "needs fixing" with links
[16:00] <josepht> balloons: yes, I'm still investigating the missing comment
[16:01] <robru> thostr_, we're having some trouble with this reconfig, didrocks is looking into it
[16:01] <balloons> josepht: ahh. yes that was my primary concern, though the build failure is a bit odd.. but :-)
[16:01] <thostr_> robru: ok, just let me know once it has been reconfigured
[16:01] <robru> thostr_, will do, thanks for your patience
[16:06] <robru> thostr_, ok, it's reconfigured. please build
[16:06] <didrocks> thostr_: wrong parameters were used, it's fixed now
[16:08] <thostr_> thanks
[16:08] <Saviq> davmor2, elopio, that result http://paste.ubuntu.com/6891973/ suggests there's something wrong with autopilot swipes - both this and the previous test needs to swipe correctly
[16:11] <josepht> balloons: the jenkins jobs are timing out trying to add comments to LP, we're looking into it.
[16:20] <elopio> Saviq: I can think of so many things that can go wrong with drags. I have a branch currently in review that fixes some things with uinput and adds full unit test coverage
[16:20] <elopio> that will help, but for now, davmor2, you are my eyes. Do you have time to debug?
[16:21] <davmor2> elopio: really need to get some apps done, but it is just do this and run this I'm more than happy too as long as I don't have to sit and watch it
[16:23] <elopio> davmor2: yeah, you'll probably have to sit and watch it. Even worst, as the pointer is not visible, you will have to pdb a lot :(
[16:23] <elopio> davmor2: better next week?
[16:23] <josepht> ChrisTownsend: that MP has been merged, thanks to fginther
[16:23] <davmor2> elopio: Monday should be good I'll have the apps queue right down by then so will just need to forward to packagers
[16:24] <ogra_> [16:24] <ogra_> (in case you guys didnt notice)
[16:24] <elopio> davmor2: ok, let me know. In the meantime I'll push autopilots to merge my changes.
[16:26] <popey> \o/
[16:27] <davmor2> popey: stop looking so happy.  If that is what the sun does to you we'll have to lock you away in a darken room in future :P
[16:28] <josepht> balloons: fginther has found and fixed the issue with the CI comment timeouts
[16:28] <popey> ogra_: getting an error updating to 170
[16:28] <popey> one moment
[16:28] <popey> "FileNotFoundError: /var/lib/system-image/blacklist.tar.xz"
[16:29] <ogra_> popey, hmm
[16:29] <ogra_> popey, i guess thats an stgraber thing
[16:30] <ChrisTownsend> josepht: Yeah, I saw that.  Thanks to you and fginther!
[16:30] <popey> fwiw I cleanly flashed this phone today, 169
[16:30] <popey> davmor2: it's raining
[16:30] <davmor2> popey: yeah it was prepping you for arriving home
[16:31] <popey> ogra_: http://popey.com/~alan/phablet/device-2014-02-07-112816.png
[16:31] <popey> want a bug report?
[16:31] <robru> thostr_, merge conflict in silo 5. need to either manually reconcile application-job-to-c or drop that merge from the build
[16:31] <ogra_> popey, yes, against system-image
[16:32] <ogra_> popey, hmm, probably even a barry or mandel thing
[16:32] <popey> ok
[16:32] <ogra_> depends where the upgrade failed exactly
[16:33] <thostr_> robru: how do I do the former?
[16:33] <mandel> popey, hm.. weird, can you grab syslog and paste it so that I can tell you if it was the downloader?
[16:34] <mandel> popey, or email it to me
[16:34] <thostr_> robru: ted is on it
[16:35] <popey> https://bugs.launchpad.net/ubuntu-system-image/+bug/1277589
[16:35] <popey> mandel: sure
[16:36] <robru> thostr_, yeah, ted will need to manually rebase
[16:36] <robru> thostr_, but in the event that the branch author isn't around, the offending MP can be dropped from the landing if the other branches are urgent.
[16:36] <popey> mandel: https://bugs.launchpad.net/ubuntu-system-image/+bug/1277589/+attachment/3972761/+files/syslog
[16:38] <thostr_> robru: ted reordered the MPs so I guess you need to reconfigure again
[16:38] <robru> thostr_, ok, will do
[16:39] <balloons> josepht and fginther ty :-)
[16:40] <robru> thostr_, ok, reconfigged, please build
[16:42] <mandel> popey, added some extra info tou your bug, looks like system-updates never requested that file to udm
[16:43] <mandel> popey, and was therefore not downloaded
[17:05] <didrocks> ogra_: not sure we need to have the meeting right now, thoughts?
[17:05] <ogra_> didrocks, well, plars and i have a nice time in the hangout ... but we can cancel ...
[17:06] <ogra_> the issue popey saw above seems to be a red herring
[17:06] <ogra_> maguro upgraded fine
[17:06] <ogra_> (though i think we found a potential bug, depending if popey manages to get out of this state now)
[17:08] <kgunn> didrocks: hey...is there anyone in US for landing help ?
[17:08] <kgunn> you guys deserve to travel home
[17:08] <kgunn> but was hoping to propose a mir again...and get a silo
[17:08] <kgunn> any chance ?
[17:10] <didrocks> kgunn: if you have no ABI break, that's good, otherwise, there is unity-mir which is locked in a silo
[17:11] <didrocks> kgunn: but there will be no-one today in the US timezone
[17:12] <balloons> cihelp, ping
[17:13] <fginther> balloons, yo
[17:16] <balloons> fginther: so interesting issue I want to ask you about. It seems that as part of the core apps merge process, we assume the priority version to install is the newly built version. However, manual uploads or versioning issues can cause havoc. I believe that's what is happening in the case of this merge: https://code.launchpad.net/~mzanetti/reminders-app/fix-fetching-notes/+merge/205372
[17:16] <balloons> if you look at http://91.189.93.70:8080/job/generic-mediumtests-trusty/1172/console you will see the ppa version is the highest version, and is what is installed. Later on then reminders-app-autopilot fails to meet a dependency
[17:16] <balloons> ultimately then the test fails
[17:18] <balloons>  reminders-app-autopilot : Depends: reminders-app (= 0.2ubuntu1+autopilot0) but 0.3 is to be installed
[17:19] <popey> ogra_: ok, updated fine
[17:19] <ogra_> popey, yay
[17:19] <fginther> balloons, yep, that looks to be the case, we also need to think about what the outcome here is
[17:20] <fginther> balloons, if you want to continue jenkins to make automatic updates to the PPA, the package version needs to be updated
[17:20] <fginther> the dputs will be rejected until that happens'
[17:21] <balloons> fginther, yes I guess pushing the package version higher than what's in the ppa fixes things. However, I think the assumption might be a bit dangerous
[17:21] <fginther> If the package version is updated in this proposal to 0.3, it should allow the tests to work as is, but would also replace what's in the PPA
[17:21] <fginther> balloons, right
[17:21] <fginther> balloons, what's the reason for the manual upload
[17:21] <fginther> ?
[17:22] <balloons> fginther: the manual upload occured because there is also a plugin and I guess it needed to be updated
[17:23] <balloons> I didn't perform it, but that's my understanding :-)
[17:23] <fginther> balloons, I understand... just trying to get more background
[17:24] <fginther> balloons, well, since the 0.3 bump hasn't made it into the source branch yet. I think we need to stop there...
[17:25] <balloons> fginther: what do you mean?
[17:25] <fginther> balloons, lp:reminders-app is still at 0.2ubuntu1
[17:26] <fginther> balloons, I think the bump needs to make it into the source branch, then all that is needed is to rebuild mzanetti's MP to get it to pass
[17:26] <balloons> fginther: right. I'll have them push a higher version number :-) You confused me for a moment like we shouldn't do that
[17:27] <rsalveti> didrocks: what needs to happen to land unity-mir and family, just further testing?
[17:27] <fginther> balloons, I'm starting to think that letting the test fail was the right outcome, although I don't think we can depend on this quirk in the future
[17:27] <balloons> fginther: it's lunchtime here, but i think long term you might want to think about avoiding these kind of pitfalls. I know we removed alot of ppas from the bot; versioning and ppa's can cause issues
[17:27] <rsalveti> didrocks: what is the timeout for a silo?
[17:27] <didrocks> rsalveti: right
[17:27] <didrocks> just the testing part
[17:27] <didrocks> rsalveti: we don't timeout for now
[17:28] <balloons> fginther: yes, the failure was alright.. confusing for them, but easy enough to figure out in the end. I agree we should try and come up with a solution
[17:28] <balloons> I'll leave you to have a think
[17:28] <fginther> :-P I want a solution spoonfed to me (and implemented on my behalf) :-)
[17:29] <rsalveti> didrocks: hm, right
[17:29] <rsalveti> didrocks: that's a bit annoying as we want to move faster as well
[17:30] <rsalveti> and it'd be nice to give a timeout so we don't block stuff
[17:30] <didrocks> rsalveti: we can timeout, not sure if they will like to trash their work though
[17:30] <didrocks> I'm happy to implement that, I think it will need discussion though
[17:30] <rsalveti> right
[17:30] <rsalveti> a timeout would help people working harder to land stuff
[17:30] <didrocks> that's true
[17:32] <didrocks> rsalveti: let's discuss that next week or maybe a week after if we see there are bottlenecks?
[17:32] <rsalveti> didrocks: just because we'll get a ton of stuff to land because of mwc
[17:32] <rsalveti> so sooner might be better
[17:34] <didrocks> rsalveti: ok, let's plan that next week
[17:34] <didrocks> rsalveti: I'm off on Monday and Tuesday FYI
[17:34] <rsalveti> didrocks: thanks
[17:34] <rsalveti> didrocks: who will cover you?
[17:34] <didrocks> so if you want to kick the discussion before, you're welcome
[17:34] <didrocks> sil2100 will
[17:35] <rsalveti> alright, that's just, just to know who to ping next week
[17:35] <rsalveti> *that's fine
[18:28] <balloons> fginther: ping :-)