[02:04] <imgbot> [03:19] <bzoltan1> robru: good morning, the silo13 is good to go
[03:34] <imgbot> [03:34] <imgbot> [03:35] <ToyKeeper> ... and a new image, mere seconds after I finished testing the last one.
[03:37] <alecu> I'm in the middle of downloading 124... :-)
[03:38] <alecu> it takes quite a while to move all those bits down here.
[04:00] <bzoltan1> it is good to see that the new UITK did fix couple of  failing tests
[04:37] <bzoltan1> is anybody doing the European tz shift?
[06:56] <sil2100> Wow
[06:56] <brendand> sil2100, i think we can get our green image today :)
[06:56] <sil2100> brendand, ogra_: did you guys see our test results for 125 :D ?
[06:56] <brendand> sil2100, yes and we have fixes for both those!
[06:56] <sil2100> brendand: yeah, especially that the mediaplayer issue has a branch already, notes should be easy to fix as well
[06:56] <sil2100> :)
[06:56] <sil2100> \o/
[06:56] <brendand> sil2100, land silo005 and popey land my notes app fix
[06:57] <sil2100> I... I think I'm going to cry!
[06:57] <brendand> sil2100, popey needs to look after https://code.launchpad.net/~brendan-donegan/notes-app/bug1330352/+merge/226146
[06:57] <brendand> sil2100, get it merged and updated in the store
[06:59]  * sil2100 looks at popey waiting for him to wake up
[06:59] <sil2100> @_@
[07:06] <brendand> popey, popey - wake up wake up!
[07:06] <brendand> CI christmas is here!
[07:06] <sil2100> Anyway, jokes aside, I'm glad that the networking issue got resolved
[07:06] <brendand> sil2100, yes. that's good to see
[07:07] <sil2100> I'm glad we didn't revert - it seems sometimes it's good to just give upstreams some time for a fix
[07:07] <Mirv> indeed, awesome colors this time
[07:16] <brendand> sil2100, well yes, but also i would agree that we can't go 2-3 days with no results
[07:16] <brendand> sil2100, so reverting might have been necessary in the end
[07:16] <brendand> sil2100, but thankfully it wasn't :)
[07:16] <Mirv> brendand: sil2100: who should be pinged about the notes-app branch?
[07:16] <brendand> sil2100, so any chance that today we can be a bit conservative about what else we land? make sure it's thoroughly tested and also not world breaking
[07:17] <brendand> Mirv, popey i think takes care of it
[07:17] <Mirv> ok
[07:17] <brendand> Mirv, dpm also might be able to do a review
[07:17] <brendand> Mirv, but popey needs to upload it i think
[07:17] <brendand> anyway - bbl for the meeting
[07:18] <Mirv> brendand: I can upload, popey can approve it in the store, but someone needs to get the branch to the trunk
[07:18] <sil2100> brendand: yeah, we might try a low velocity approach today, let me talk with cjwatson on the meeting :)
[07:23] <dpm> brendand, I've not had anything to do with notes-app, so I'm not sure I can help
[07:36] <Mirv> Bill top-approved the previous thing that went in to notes-app
[07:39] <sil2100> We can't wait that long!
[07:39] <sil2100> ;)
[08:27] <cjwatson> Morning
[08:27] <cjwatson> sil2100: shall I take over sheriff?
[08:29] <sil2100> cjwatson: morning! Yes please ;) We were just thinking if maybe we could try doing it 'safe' today
[08:30] <sil2100> i.e. check each landing if it's risky or not before publishing, if it's risky then pinging the upstream developer to make sure he tested it right
[08:30] <sil2100> But more on the meeting
[08:30] <cjwatson> Right, well, I can't do much in the way of personal testing, not enough bandwidth
[08:30] <cjwatson> So hopefully that won't be needed ...
[08:31] <cjwatson> Our opinions of riskiness might differ ;-)
[08:32] <psivaa> sil2100: am i on the wrong hangout... or you are yet to join?
[08:32] <sil2100> psivaa: maybe wrong hangout ;)
[08:32] <sil2100> We're all here
[08:43] <brendand> sil2100, i think everything should be thoroughly tested regardless of whether it's risky
[08:43] <brendand> cjwatson, my definition of risky would be packages that have lots of rdeps
[08:44] <cjwatson> remind me what the justification for extra care in this particular instance is?
[08:45] <cjwatson> (I see we're low on silos again)
[08:47] <cjwatson> (discussing in hangout)
[08:48] <seb128> sil2100, do you know what's the status of the qtcompositor work?
[08:48] <seb128> sile 006
[08:48] <seb128> I wonder if I can hijack it for a settings landing
[08:48] <seb128> e.g do a landing and force them to rebuild settings then
[08:50] <Laney> seb128: want to take the activation fixes?
[08:51] <Laney> I don't think we'll get tests for those any time soon
[08:51] <seb128> Laney, ok
[08:51]  * Laney files a dbusmock bug as a reminder
[08:56] <sil2100> seb128: I would say it's safe to do a landing, didn't hear anything from them about it being ready
[08:57] <seb128> sil2100, thanks, I just did that ^
[08:57] <sil2100> o/
[08:57]  * sil2100 goes back to testing his auto-merge-and-clean functionality
[08:57] <sil2100> It's hard to test in a safe environment
[09:01] <cjwatson> Well, can't do much until testing happens, so going back to parted packaging work for a bit
[09:02] <cjwatson> not assigning that right now as only one silo left
[09:05] <seb128> cjwatson, 0 left now
[09:05] <mvo_> seb128: that was me :/ sorry
[09:06] <seb128> mvo_, no worry ;-)
[09:06] <seb128> I still don't get why you assign silos to people who do it themself btw :p
[09:06] <Laney> silo hog!
[09:06] <seb128> who *can* do it*
[09:07] <mvo_> right, lets make the landings quick so that we can have free silos again :)
[09:09] <mvo_> sil2100: do you mind if I add a warning into the "assign silo" code when there is just one silo left? the code is directly in the speadsheet, right?
[09:15] <sil2100> mvo_: sure, no problem ;)
[09:16] <brendand> cjwatson, what about landing silo005? it's been top-approved and tested
[09:16] <sil2100> mvo_: all the code is in the google scripts for the spreadsheet
[09:17] <cjwatson> brendand: oh, spreadsheet says "testing done: no"
[09:17] <cjwatson> brendand: I thought you said you weren't sure about the testing, earlier
[09:18] <sil2100> brendand: let's make sure ricmm +1'es it finally
[09:19] <sil2100> ricmm: hi! Did you test everything for silo 005?
[09:19] <brendand> sil2100, oh yeah ricmm is here
[09:20] <ricmm> sil2100: I'm happy with it, I've tested and so has jim
[09:20] <ricmm> push the buttonz
[09:20] <cjwatson> ricmm: will do
[09:21] <sil2100> ricmm: thanks o/
[09:23] <cjwatson> I've acked those
[09:26] <popey> Mirv: when you get a moment could you please shove http://s-jenkins.ubuntu-ci:8080/job/weather-app-click/lastSuccessfulBuild/artifact/out/com.ubuntu.weather_1.1.301_all.click into the store?
[09:41] <bzoltan1> ohh, I see we are out of silos
[09:42] <mvo_> sil2100: silly question but what is the best way to test my script addition?
[09:43] <bzoltan1> zbenjamin:  is it possible to make the main project file open in the editor?
[09:43] <seb128> yeah, get mhr3__ or thostr_ to test/land some of their "built" lines maybe
[09:44] <thostr_> seb128: I'm properly testing those still
[09:44] <sil2100> mvo_: in the spreadsheet you mean? ;) Sadly there's not much sandbox possibilities, but I guess you can try mocking a low-silo number (or simply changing your threshold to the current number of silos and just running the script
[09:44] <seb128> thostr_, ok
[09:44] <sil2100> )
[09:44] <seb128> thostr_, is the transfert indicator used anywhere yet?
[09:44] <mvo_> sil2100: ok, I will play around, not a lot that can break I guess
[09:44] <thostr_> yes, e.g. when doing "save image as" browser
[09:45] <mvo_> sil2100: are the script in some sort of version control inside the google doc?
[09:45] <sil2100> mvo_: sadly not...
[09:45] <thostr_> and oSoMoN told me two days ago that browser had a landing prepared to fully use it
[09:46] <seb128> thostr_, great, thanks
[09:47] <oSoMoN> thostr_, "save image as…" is not ready yet (blocked on an oxide bug which is being actively worked on), however downloading an image attachment from gmail works already (in browser that is, the webapp has an apparmor permission issue that I reported this morning)
[09:48] <thostr_> oSoMoN: ah, worked earlier this week...
[10:05] <Mirv> popey: weather app done
[10:06] <popey> thanks Mirv
[10:11] <sil2100> popey, ogra_, brendand: ok, I guess it makes no sense to wait for Bill regarding this test-fix merge - since Leo gave it a +1 and it only changes the test code, I would top-approve it myself and get it merged
[10:11] <sil2100> oSoMoN: ^ what do you think about the above? It's regarding notes-app, so not your territory but I know you were acting as a lander for most of the components
[10:12]  * oSoMoN reads
[10:12] <sil2100> oSoMoN: I'm talking about this merge:
[10:12] <sil2100> oSoMoN: https://code.launchpad.net/~brendan-donegan/notes-app/bug1330352/+merge/226146
[10:13] <Saviq> seb128, xnox, silo 20 +1 from me re: inheritance and cross-build
[10:13] <sil2100> oSoMoN: it's fixing the only test failure we have that appeared after the UITK upload, and Leo from QA +1'ed it already
[10:13] <oSoMoN> sil2100, LGTM
[10:14] <cjwatson> sil2100: yeah, let's give that silo 5
[10:14] <cjwatson> before somebody self-assigns it :)
[10:15] <seb128> Saviq, +1 on the gtk 3.12 side
[10:15] <seb128> xnox, ^
[10:15] <sil2100> Yeah ;) Let me fill in a landing for it maybe
[10:16] <sil2100> brendand: I'll set you as a sub-lander for this one
[10:17] <xnox> seb128: let me run ubiquity.
[10:17] <bzoltan> sil2100: any chance to get a silo for the line 30?
[10:18] <sil2100> bzoltan: we're a bit low on silos right now, but we'll have a fast landing soon and you can get that one then
[10:18] <bzoltan> sil2100: OK, thanks
[10:18] <sil2100> cjwatson: I'm assigning a silo for this one
[10:18] <cjwatson> sil2100: for notes-app?
[10:19] <sil2100> cjwatson: yes
[10:19] <cjwatson> yes please
[10:19] <brendand> sil2100, does it need a silo?
[10:19] <brendand> sil2100, i thought it went to the store?
[10:19] <sil2100> brendand: yes, it needs one...
[10:19] <cjwatson> bzoltan: (context: notes-app is the last failing test from the most recent mako test run ...)
[10:19] <sil2100> brendand: I checked and it seems there is no auto-merger, but merges are done through CI Train
[10:20] <sil2100> hmmm
[10:20] <brendand> sil2100, ok. but Mirv still needs to upload it to the store right?
[10:20] <sil2100> brendand: yes, once this gets merged
[10:21] <cjwatson> notes is a preinstalled app, so it ends up on images via http://people.canonical.com/~ubuntu-archive/click_packages/
[10:21] <cjwatson> but that gets it from the store, yes
[10:22] <cjwatson> bzoltan: how long is this going to take to test?
[10:22] <bzoltan> cjwatson:  I have tested the changes already
[10:23] <cjwatson> bzoltan: to test the built package from the silo
[10:23] <bzoltan> cjwatson:  the build will take ages
[10:23] <cjwatson> seb128: 20 tested on the phone?
[10:23] <bzoltan> cjwatson:  few minutes, the change is only text change no binary change
[10:24] <cjwatson> seb128: (just to make sure suru didn't explode)
[10:24] <seb128> cjwatson, not by me, I can do that now
[10:24] <seb128> let me try
[10:24] <bzoltan> cjwatson:  but the silo build  took yesterday about 4 hours ...
[10:24] <cjwatson> bzoltan: the last build on record took <30 minutes
[10:24] <popey> sil2100:  if it only changes the tests, then it doesn't need pushing to the store, does it? (notes)
[10:25] <popey> sil2100: because the phablet test run will pull tests from trunk
[10:25] <bzoltan> cjwatson:  of course ... each took only half an hour. But queuing for powerpc builder took 3 hours
[10:25] <cjwatson> bzoltan: that won't be a problem
[10:25] <sil2100> popey: I once thought so, but then someone explained to me that the infra actually fetches the revision associated with the currently available version that's installed
[10:26] <sil2100> popey: so even in this case we'll have to release, as otherwise it will fetch the older one anyway
[10:26] <Mirv> if in desperate need of silos, I think line 7 (trusted prompt session) could be temporarily freed. quite light to rebuild.
[10:26] <Mirv> since it's only for testing
[10:27] <sil2100> Saviq: how about silo 009? Is it planned to land today or can we flush it?
[10:27] <Saviq> sil2100, flush it if you need
[10:27] <popey> sil2100: ok, ping once that lands in trunk and we'll get it in the store, Mirv can upload, I'll approve
[10:27] <sil2100> popey: thanks, will do o/
[10:27] <sil2100> Saviq: thanks
[10:28] <xnox> seb128: all is good on ubiquity side
[10:28] <xnox> and 1px gap is gone between ubiquity fake-panel and opened fake-indicators
[10:28]  * xnox like
[10:28] <xnox> we should be able to publish & clean 20
[10:28] <brendand> sil2100, cjwatson - i'm making myself available for extra testing if needed, so just ask
[10:28] <sil2100> cjwatson: ok, so I guess we might have some free silos soon from what I hear, but in case a silo is badly needed we have permission to clean out 009
[10:29] <cjwatson> FYI I have a 1.5 hour meeting shortly
[10:29] <bzoltan> Mirv: pick me, pick me :)
[10:29] <Saviq> xnox, can you have a look at telepathy-service please, with silo 20 and :any added it built fine, but it's still running tests, not sure if the override in rules causes that
[10:30] <cjwatson> I'm just going to assign 18 to bzoltan since we have a couple that will be freeable if it becomes necessary
[10:30] <xnox> Saviq: you mean, cross-building telepathy-service?
[10:30] <bzoltan> cjwatson: \o/
[10:30] <Saviq> xnox, yes
[10:30] <cjwatson> big "low on silos" warning I see, thanks mvo :)
[10:30] <Saviq> xnox, it cross-built fine (with silo 20 + :any for python)
[10:30] <seb128> xnox, cjwatson: +1 suru on the device
[10:30] <Saviq> xnox, but it ran tests
[10:31] <cjwatson> seb128: thanks, I see it's publishing now
[10:31] <xnox> Saviq: what's the source package name? "E: Unable to find a source package for telepathy-service"
[10:32] <cjwatson> bzoltan: go ahead and build now, I will poke builders as needed (but doesn't look like it should be)
[10:32] <bzoltan> cjwatson: OK, thanks
[10:34] <xnox> Saviq: i guess telephony-service, not telepathy ;-)
[10:35] <xnox> Saviq: yeah, the dh_auto_test is wrong.
[10:36] <Saviq> xnox, did I write telepathy? sorry
[10:36] <Saviq> xnox, yes, telephony
[10:44] <Mirv> bzoltan: :)
[10:54] <xnox> Saviq: http://paste.ubuntu.com/7779678/
[10:56] <Saviq> xnox, yup, thought something like that would work, thanks!
[11:10] <Mirv> hmm, why does publish for notes say the last step wouldn't have been completed
[11:10] <cjwatson> Mirv: probably because it hasn't finished migrating yet
[11:11] <brendand> cjwatson, Silos: landing-005 (sil2100, brendand) Can't publish: wrong status or parameters for job. (notes-app)
[11:11] <brendand> cjwatson, i didn't see that before
[11:11] <cjwatson> brendand: probably because it hasn't finished migrating yet
[11:11] <sil2100> hmmm
[11:12] <cjwatson> merge-and-clean normally wants the changes to be at least pending in the release pocket first
[11:12] <Mirv> cjwatson: migrating where? it has built and I'm trying to publish it
[11:12] <Mirv> oh...
[11:12] <Mirv> lukasz was faster :D
[11:12] <sil2100> brendand, Mirv: well, I pressed publish and then Mirv pressed it again
[11:12] <cjwatson> maybe two of you tried at the same time?
[11:12] <cjwatson> right
[11:12] <sil2100> So don't worry about it
[11:12]  * sil2100 goes for lunch
[11:12] <Mirv> no problem then, nice
[11:13] <Mirv> somehow I missed that last job's timestamp or maybe my page wasn't refreshed
[11:13] <sil2100> o/
[11:19] <bzoltan> cjwatson: the QtC plugin from the silo18 is good to go
[11:22] <xnox> !ci-help I've tried to run "merge & clean" on silo 20, yet it fails.
[11:24] <xnox> Saviq: seb128: any clue why merge&clean does not work against silo 20?
[11:26] <Mirv> xnox: Saviq ran it before you
[11:26] <Mirv> https://ci-train.ubuntu.com/job/landing-020-3-merge-clean/25/
[11:26] <xnox> Mirv: ah.
[11:27] <Saviq> could probably use better error messaging ;)
[11:34] <bzoltan> Mirv:  is there anything I could do to speed up the landing of the Silo18 landing?
[11:37] <Mirv> bzoltan: published
[11:39] <bzoltan> Mirv: thank you
[11:43] <popey> Mirv: could you please push http://s-jenkins.ubuntu-ci:8080/job/sudoku-app-click/lastSuccessfulBuild/artifact/com.ubuntu.sudoku_1.1.226_all.click to the store?
[11:47] <Mirv> popey: done
[11:49] <popey> thanks
[11:52] <cjwatson> bzoltan: (sorry, on a call)
[11:53] <bzoltan> cjwatson: all fine now, the silo will be cleaned soon
[11:56] <brendand> Mirv, so is notes app uploaded?
[11:57] <Mirv> brendand: yep, not yet merged to trunk
[11:57] <Mirv> ok, now in release pocket 1 min ago
[12:00] <cjwatson> any objection to me building another image once notes-app is published?
[12:00] <brendand> cjwatson, i was just about to ask you to build one :)
[12:00] <Mirv> cjwatson: no objections, but we need to wait for the click one
[12:01] <cjwatson> -rw-rw-r-- 1 ubuntu-archive ubuntu-archive  83580 Jul 11 11:41 public_html/click_packages/com.ubuntu.notes_1.4.269_armhf.click
[12:01] <cjwatson> is it that?
[12:01] <brendand> cjwatson, but yeah - popey needs to approve notes-app in the store
[12:01] <cjwatson> that's 20 minutes old ...
[12:01] <mvo_> cjwatson: do you mind if I look at merges.ubuntu.com and try to figure out why it appeared to stop updating?
[12:02] <popey> brendand: someone needs to upload it first
[12:03] <cjwatson> mvo_: not at all, it'll be yet another "source won't unpack" problem
[12:03] <Mirv> cjwatson: not really sure, I just kicked a new build at http://s-jenkins.ubuntu-ci:8080/job/notes-app-click/
[12:03] <mvo_> cjwatson: great, I check it out once #is grants me access again
[12:03] <cjwatson> mvo_: info in /var/mail/merge, basically make sure that the next version along actually unpacks properly and remove the busted ones from /srv/patches.ubuntu.com/pool/{debian,ubuntu}/whatever/
[12:03] <brendand> popey, Mirv  is meant to be doing that
[12:04] <mvo_> cjwatson: thanks, that is very helpful!
[12:04] <popey> brendand: ping me when done, not before ☻
[12:05] <cjwatson> ah, yeah, that's revno 269, can't be right, we're expecting revno >=274
[12:08] <cjwatson> indicator-transfer isn't on any images, so I'll publish it
[12:09] <Mirv> brendand: popey: http://s-jenkins.ubuntu-ci:8080/job/notes-app-click/74/artifact/out/com.ubuntu.notes_1.4.275_armhf.click
[12:10] <Mirv> shall I just upload that, or do you want to test it first?
[12:10] <popey> nope, just upload it, its been through CI/Jenkins/QA right? ☻
[12:12] <brendand> Mirv, no it's alright just upload it
[12:12] <brendand> (famous last words)
[12:12] <Mirv> brendand: popey: done
[12:13] <brendand> popey, ping :)
[12:13] <popey> approved
[12:14] <brendand> popey, so cjwatson can kick a build?
[12:14] <brendand> popey, or do we need to wait for the process to filter through?
[12:14] <cjwatson> brendand: I can
[12:15]  * cjwatson forces a click-sync
[12:15] <brendand> cjwatson, i meant, if you kick a build now will we be guaranteed to get the new version of the click package?
[12:15] <cjwatson> brendand: I'm making sure of that first
[12:15] <brendand> cjwatson, i guess the answer is yes
[12:15] <cjwatson> ubuntu-archive@snakefruit:~$ grep notes public_html/click_packages/click_list
[12:16] <cjwatson> com.ubuntu.notes_1.4.275_armhf.click
[12:16] <cjwatson> (the cron job runs at :11 and :41; I ran it by hand)
[12:21] <brendand> let's do this build
[12:22] <cjwatson> already queued
[12:22] <cjwatson> running in fact; no doubt some bot will notice at some point
[12:24] <imgbot> [12:24] <brendand> cjwatson, :)
[12:24] <ogra_> :)
[12:26] <cjwatson> stgraber: is it possible for queuebot to tell us about ubuntu-touch image builds?  seems like it should be able to manage lower latency
[12:29] <ogra_> cjwatson, do you have an idea why sudo -s would behave different to bash -c when executed via a forked execl ?
[12:30] <ogra_> i'm patching adbd to use sudo -u$USER -s over bash -c (so that we get pam processing and a proper env) ... like in http://paste.ubuntu.com/7779944/
[12:30] <ogra_> but i end up with:
[12:30] <ogra_> ogra@anubis:~/image-stuff$ adb shell sudo ls
[12:30] <ogra_> /bin/bash: sudo ls: command not found
[12:30] <ogra_> ogra@anubis:~/image-stuff$ adb shell
[12:30] <ogra_> phablet@ubuntu-phablet:~$
[12:31] <ogra_> while when using bash -c for the shell command the same code works just fine and takes the last arg as command with options
[12:32] <cjwatson> sigh, things that take a command and don't act in a sensible adverbial fashion are the devil incarnate
[12:33] <ogra_> well, i dont get why sudo behaves different here ...
[12:33] <cjwatson> no doubt it's overquoting somewhere
[12:33] <cjwatson> compare:
[12:34] <cjwatson> sudo -u$USER sudo ls
[12:34] <cjwatson> sudo -u$USER "sudo ls"
[12:34] <cjwatson> apparently your code is doing something analogous to the second one
[12:34] <cjwatson> the first one is actually a much better design for commands that take other commands
[12:34] <cjwatson> but you may need to adjust for it
[12:34] <ogra_> well it simply hands it over to execl
[12:34] <ogra_> there is no mangling of "arg2" anywhere
[12:34] <jdstrand> oSoMoN: fyi, that issue should be fixed now in apparmor-easyporf-ubuntu 1.2.9, which was in utopic last night
[12:35] <cjwatson> sounds like this is terrible design of adb
[12:35] <ogra_> it is
[12:35] <cjwatson> I guess it smashes its args together into one?
[12:35] <ogra_> but i dont want to rewrite the whole block :)
[12:35] <ogra_> execl(cmd, cmd, arg0, arg1, arg2, NULL);
[12:35] <ogra_> thats what it calls
[12:36] <cjwatson> so you need to either separate them again, or (perhaps simpler) use sudo -u$USER -s bash -c
[12:36] <ogra_> cmd being sudo ... arg0 being -uphablet ... arg1 being -s
[12:36] <cjwatson> then the subsidiary shell will word-split the string for you
[12:36] <ogra_> isnt -s actually executing bash -c ?
[12:36] <cjwatson> not with the same quoting
[12:36] <ogra_> ah ...
[12:36]  * ogra_ tries
[12:36] <cjwatson> you are expected to pass command and arguments as separate arguments
[12:37] <cjwatson> whereas bash -c takes a single string
[12:37] <ogra_> right
[12:37] <cjwatson> actually you should probably drop the -s, then
[12:37] <cjwatson> sudo -u$USER bash -c
[12:37] <cjwatson> otherwise you'll have an unnecessary shell in the process tree
[12:38] <cjwatson> and yeah, kick whoever misdesigned adb shell :P
[12:38] <ogra_> hahaha
[12:38]  * ogra_ kicks google
[12:46] <davmor2> oh new scopes
[12:46] <ogra_> cjwatson, thanks ... that works !!
[12:46] <davmor2> ogra_: does this release have the deadlock fix?
[12:47] <ogra_> davmor2, i dont think it does ... sil2100 might know though
[12:48] <ogra_> bah ...
[12:49] <ogra_> but now something like: "adb shell sudo ls" echos the password to the screen :(
[12:49] <ogra_> seems stdin/out are not right
[12:55] <cjwatson> ogra_: cool
[12:55] <cjwatson> ogra_: that sounds like an incorrect $TERM setting, at a guess
[12:56] <cjwatson> ogra_: I see much strace in your future
[12:56] <cjwatson> ogra_: or, yeah, I guess it could be stdin not wired up quite right
[13:06] <sil2100> oh, it seems I got disconnected
[13:07] <ogra_> so you did
[13:07] <ogra_> sil2100, davmor2 asked where we stand with the lockup fix ... do you know ?
[13:08] <davmor2> sil2100: I was asking as a new image was triggered and wanted to know if you needed it testing for promotion cause it was so green it was unbearable
[13:09] <sil2100> davmor2, ogra_: sadly, from what I know there have been some things they still wanted to work on, the fixes aren't complete
[13:09] <ogra_> ok
[13:09] <sil2100> I need to poke Kevin some more today
[13:09] <sil2100> Anyway, I would not expect any promotion today anyway
[13:09] <davmor2> sil2100: that sounds so wrong
[13:11] <davmor2> sil2100: :(
[13:11] <sil2100> davmor2: from what I see in the bug right now.. seems like parts of the issue is fixed now in their development branch, but I think it doesn't fix all the issues
[13:12] <sil2100> The other branches are still on hold
[13:13]  * davmor2 sees his dream of popey in a green t-shirt slowly dirft away :)
[13:14] <sil2100> Hey! It's possible! We only need all tests passing ;)
[13:14] <sil2100> We don't need a promotion!
[13:14] <sil2100> :D
[13:15] <sil2100> And/or working tablet images
[13:20] <sil2100> ogra_: so 126 is still building, right?
[13:20] <ogra_> yep
[13:24] <sil2100> davmor2: anyway, as per discussion with kgunn, we migh have a final fix for this later today
[13:24] <cjwatson> mhr3: just checking because apparently we're being extra-careful today, what testing did you (or whoever?) do on silo 14?
[13:24] <sil2100> So no worries
[13:24] <mhr3> dobey, ^^
[13:24] <davmor2> sil2100: \o/ :) that makes me happier
[13:26] <seb128> sil2100, who has access to the landing functions of the google doc?
[13:26] <stgraber> cjwatson: yes, I was thinking to hook it up to the existing tracker code we've got which will notice any new build within 30s, however that will be the standard plugin that we run on #ubuntu-release with a filter so we won't get the URL to the diff and stuff like that (well, until we get this generalized on cdimage and can print it for everything)
[13:26] <dobey> cjwatson: tested the click scope and deleted/re-added the account
[13:26] <seb128> sil2100, can we get kenvandine added to whatever group that is?
[13:49] <imgbot> [13:49] <imgbot> [13:49] <plars> xnox: did you see my email about the utopic install problems?
[13:50] <plars> ooo, Will the new notes app make us even more green?
[13:52] <ogra_> plars, yeah
[13:53] <ogra_> plars, well, i guess popey broke the facebook app to compensate for this
[13:53] <popey> \o/
[13:53] <popey> also sudoku
[13:53] <plars> ogra_: hey, remember the dbus-x11 forced uninstall we had to put in a while back? Any reason to keep that, or is it safe to kill that in our scripts now?
[13:54] <plars> popey: at least on 125, sudoku passed I thought
[13:54] <ogra_> plars, if we are sure autoremove really removes everything
[13:54] <ogra_> phablet@ubuntu-phablet:~$ ./get-deps.sh 126
[13:54] <ogra_> New packages: liburcu2
[13:54] <ogra_> src: ust, bin: liblttng-ust-ctl2 depends on liburcu2
[13:54] <ogra_> src: ust, bin: liblttng-ust0 depends on liburcu2
[13:54] <ogra_> Summary:
[13:54] <ogra_> ust depends on liburcu2
[13:55]  * ogra_ hugs his new dependency checker script 
[13:55] <ogra_> no more new packages that we dont know where they come from :)
[13:55] <popey> plars: new one in 126 ☻
[13:55] <plars> ogra_: I'm still unclear on why it didn't remove it before
[13:56] <plars> popey: yes, but sudoku worked, I like to see changes to packages that weren't fully green :)
[13:57] <plars> ogra_: I can do a test run without it that doesn't go to the dashboard and see if there are any weird results
[13:57] <ogra_> plars, right, me neither ... i think autoremove might not actually remove everythig cleanly ... i think what we should do is parse the output of a dry run to get a list and apt-get purge that list at the end ... instead of relying on autoremove
[13:57] <ogra_> (run autoremove still, to get rid of additional deps)
[13:57] <ogra_> plars, yeah, do that and see
[14:02] <sil2100> Just please don't do that yet for run 126 ;)
[14:16] <xnox> plars: i've seen the email. but i couldn't work out what is implied as the next steps from that email, and for who.
[14:17] <plars> xnox: so, for physical system installs, I have a workaround but the kernel team is concerned about whether that can be considered to be equivalent to doing the install on a real desktop image
[14:18] <plars> xnox: If there's anything I can do from our side to help debug this, I'm happy to do so. I don't know what's causing it to fail with the desktop image at the moment though
[14:21] <brendand> sil2100, agh - mediaplayer-app did get the failure :/
[14:21] <brendand> sil2100, looks like my concern was right
[14:21] <brendand> shame
[14:21] <sil2100> :<
[14:22] <sil2100> Sadly, no 100% green image today it seems
[14:22] <seb128> sil2100, do you who has access to the landing functions of the google doc? and if we can get kenvandine added/how?
[14:22] <ogra_> brendand, why would it suddenly start to skip the test with that fix ?
[14:22] <sil2100> seb128: I can add him if needed, no problem
[14:22] <ogra_> (remember that failing test is supposed to be skipped)
[14:22] <sil2100> ogra_: it was supposed to remove the media-hub crash
[14:22] <seb128> sil2100, that would be nice
[14:23] <ogra_> sil2100, oh, the crash
[14:23] <sil2100> ogra_: and it's the media-hub crash that caused the test not to be skipped...
[14:23] <ogra_> sil2100, ah
[14:23] <sil2100> At least that was my understanding
[14:23] <sil2100> But it seems something else is crashing now or such
[14:23] <sil2100> brendand: ^
[14:23] <ogra_> well, lets see til the crashes get synced
[14:23] <ogra_> i only see the non skipped tests atm
[14:23] <sil2100> seb128: added
[14:24] <seb128> sil2100, thanks
[14:24] <sil2100> yw o/
[14:27]  * brendand updates to find out about the mediahub-server crash
[14:30] <sil2100> brendand: thanks!
[14:34] <plars> xnox: istr you mentioned there were some pre-existing bugs in ubiquity that you thought could be related to what I described?
[14:35] <brendand> sil2100, crazy. the error is the same one that the landing was supposed to fix...
[14:35] <brendand> sil2100, did something go wrong?
[14:35] <sil2100> hm
[14:36] <sil2100> brendand: shouldn't have, it seems media-hub landed properly
[14:49] <ogra_> hey, but at least notes-app passed fine :)
[14:53] <xnox> plars: all of which have been subsequently fixed by now.
[14:53] <xnox> plars: and none of them were/are present in trusty images, which are now failing.
[14:53] <xnox> plars: including the trusty 14.04.0 image.
[14:54] <xnox> plars: ubiquity issues were introduced in utopic, and fixed in utopic by now.
[14:54] <plars> xnox: the trusty image, I believe is an unrelated problem after all. That's the VM issue I described, and that's something we're going to have to try to work around in utah
[14:55] <xnox> plars: let me redo physical machine testing with ubiquity desktop cd here.
[14:55] <sil2100> robru: so, looking at the changes you made, it seems you introduced a security hole in our CI Train ;)
[14:55] <xnox> plars: as far as i can tell there is nothing in the installer holding up /target, however utah is running a pressed and maybe that is holding up /target in its success/failure commands.
[14:56] <sil2100> robru: I think we'll have to revert your recent addition of running jobs easily without an additional button click
[14:56] <xnox> plars: what i need is fsuer / lsof output for /target, before the unmount happens in ubiquity.
[14:56] <xnox> i guess i can put that in ubiquity itself.
[14:57] <sil2100> robru: sadly, using the authToken is by-passing the authentication of jenkins itself, which means basically anyone that knows the token can now run the job
[14:57] <plars> xnox: if we can get some sort of debug build, I'd be happy to give it a try here
[14:57] <xnox> plars: cause otherwise, if 14.04.0 fails to install on physical hardware in auto-preseeded mode, we have huge problems.
[14:58] <sil2100> robru: which basically means anyone can now assign new silos - and since citrain is being hosted on bzr, basically everyone has the token ;)
[14:59] <xnox> plars: as far as i can tell: trusty 14.04.0, trusty daily, and utopic daily are all operating correct. And have not reproduced "umount /target" hanging, outside of CI's utah setup.
[15:00] <xnox> plars: and local utah setup that i used to have, is no longer operation and fails starting to provision anything.
[15:00] <plars> xnox: anything I can do from our side to help debug this?
[15:03] <xnox> plars: (a) can i have access to a utah server that can run and provision machines that fail?
[15:03] <xnox> plars: (b) failing that, can someone get hands into ubiquity (e.g. terminal, vnc, shell) and check what processes are holding up /target when it was presseeded by utah?
[15:04] <xnox> plars: so far, i don't have access to any utah server which exibits the problem seen in the logs.
[15:06] <plars> xnox: I can set up a copy of the power test job that uses the desktop image again, and we can start there. Let me run that and reproduce the failure, but it might be monday before we can make too much progress. I have something that's going to keep me tied up this afternoon for a few hours and won't be back until pretty late
[15:08] <sil2100> hmmm
[15:09] <sil2100> Is it only me or does the spreadsheet look strange?
[15:09] <sil2100> cjwatson: do you know why lines 27 and 30 seem to be landed, but the spreadsheet didn't register those?
[15:09] <sil2100> cjwatson: was merge and clean ran for those?
[15:10] <sil2100> Damn, things really seem to be b0rken
[15:11] <sil2100> Let me look into that in a moment...
[15:13] <cjwatson> sil2100: pretty sure both of those were merged and cleaned
[15:14] <sil2100> cjwatson: yeah, I saw that they did, somehow CITrain didn't set those to 'Landed'
[15:14] <cjwatson> 12:22 -queuebot:#ubuntu-ci-eng- Silos: landing-020 (Saviq, seb128) Empty (ubuntu-themes)
[15:14] <cjwatson> 12:59 -queuebot:#ubuntu-ci-eng- Silos: landing-005 (brendand, sil2100) Empty (notes-app)
[15:14] <sil2100> I fixed that in the spreadsheet but I need to fix that
[15:14] <sil2100> Oh
[15:14] <sil2100> Empty?
[15:14] <cjwatson> well that was after merging
[15:15] <cjwatson> but yeah, those silos are freed
[15:15] <ogra_> charles, what about the transfer indicator ... shouldnt we seed it ?
[15:15] <sil2100> It shouldn't be empty, should be Landed I guess..? But well, maybe it's just phrasing, but anyway it sets the status of the landing to '' instead to 'Landed'
[15:15]  * sil2100 looks at the scripts
[15:15] <cjwatson> https://ci-train.ubuntu.com/job/landing-020-3-merge-clean/25/console and https://ci-train.ubuntu.com/job/landing-005-3-merge-clean/39/console
[15:15] <cjwatson> I've so far seen Empty after the silo is no longer assigned to anything
[15:16] <sil2100> cjwatson: btw. I think we can land things normally now if anything
[15:17] <brendand> sil2100, i suppose just 1 failure, which we have a handle on is pretty good :)
[15:24] <brendand> nooooo, calculator and calendar - whyyyy!
[15:24] <brendand> it's in settle_after???
[15:25] <sil2100> uh
[15:25] <brendand> plars, do you know what settle_after is trying to do?
[15:25] <ogra_> brendand, it wants the system to go to 97.5% idle
[15:26] <sil2100> It checks if the CPU has settled, or is there something making it not idle enough
[15:26] <plars> brendand: yes, it's the same thing as settle_before
[15:26] <plars> brendand: basically making sure we don't have anything lingering after the test that is hogging the cpu
[15:26] <ogra_> brendand, we need the topafter.log to see whats the issue
[15:26] <ogra_> that is only synced at the end
[15:31] <ogra_> brendand, i'd blame our Mir issue though ...
[15:33] <brendand> ogra_, what's our mir issue? did we land mir in this image?
[15:35] <ogra_> brendand, the Mir issue that makes my flo hang for 2min if i start an app etc ... which doesnt manifest that heavily on mako
[15:43]  * cjwatson looks at 14
[15:44] <cjwatson> yeah, that looks OK to me
[15:44] <cjwatson> sil2100: normally> ack
[15:45] <sil2100> o/
[15:45]  * sil2100 is still looking for the root cause of the spreadsheet behaving strangely
[15:47]  * cjwatson acks 11 too
[15:49] <sil2100> hmmm, I think I see the reason for this, there might be a race condition due to google spreadsheet slowness
[15:50] <cjwatson> mhr3: hm, is the connectivity-api/powerpc failure known-flaky?  I guess it must be because it built before
[15:51] <cjwatson> mhr3: you're going to have to rebuild most of silo 11 anyway due to newer versions in utopic
[15:51] <cjwatson> mhr3: and then (IMO) retest
[15:51] <mhr3> cjwatson, are you sure you wanted to talk to me?
[15:51] <cjwatson> oh damn sorry
[15:51] <asac> sil2100: cjwatson: how is traincon going? do you have enough support from QA?
[15:51] <cjwatson> mandel: ^- above few lines were meant for you
[15:51] <sil2100> asac: there was no need for traincon
[15:52] <asac> ?
[15:52] <sil2100> asac: as mentioned yesterday, the deal was to enter TRAINCON if the issue is not fixed
[15:52] <asac> so we promoted?
[15:52] <sil2100> asac: but it got fixed during the night and we had test results throughout all day
[15:52] <sil2100> asac: no, but we promoted recently, so no need for traincon ;)
[15:52] <asac> when?
[15:52] <asac> i feel i am more than 5 days outdated :)
[15:52] <asac> guess i am just impatient
[15:53] <cjwatson> last promotion was three days ago
[15:53] <sil2100> asac: 3 days ago
[15:53] <cjwatson> 2014-07-08
[15:53] <asac> ack
[15:53] <asac> ok
[15:53] <sil2100> So we still have a safe buffer
[15:53] <asac> well, in theory there is a middle stage that we invented to manage to not need to go to expensive TRAINCON-0
[15:53] <mandel> cjwatson, yes, is flaky
[15:53] <sil2100> asac: no promotion today as the hang-up blocker is still being worked on, but we'll have a fix till end of today (as per kgunn's promise)
[15:53] <asac> but well :)
[15:54] <cjwatson> mandel: it needs to manage to build before we can publish - but as I say we need to rebuild anyway due to newer versions.  do you want me to organise that?
[15:54] <sil2100> asac: but we got down to 1 failure basically in smoketesting ;)
[15:54] <mandel> cjwatson, yes please, that would be very welcome
[15:54] <asac> https://docs.google.com/a/canonical.com/presentation/d/1FOqa6jqGEFPgJ2Ghxgkb7Cqi774IujImPHfYFEYnJgc/edit#slide=id.g2c6354463_028
[15:55] <asac> TRAINCON-1 tries to give incentive to fix things because it makes landing of affected components more careful
[15:55] <sil2100> asac: yeah, we didn't land any Mir landings, so we're proceeding according to the rulse here ;)
[15:55] <sil2100> *rules
[15:55] <asac> sil2100: only promotion blocker is Mir?
[15:55] <sil2100> As it's Mir that's affected and the root cause of our blocker
[15:55] <sil2100> Yes :)
[15:55] <asac> nice
[15:55] <asac> so withthat fixed we promote... cool
[15:55] <asac> so in theory we are in TRAINCON-1 :)
[15:55] <asac> lol
[15:55] <asac> just that we dont send the QA folks on the MIR folks before doing the landing
[15:56] <asac> err in practice i mean
[15:56] <asac> actually it doesnt ask for QA double check
[15:56] <asac> just that landngs get serialized a bit
[15:56] <cjwatson> mandel: trying
[15:57] <asac> and that landers get testplans reviewd by QA and that landers have to run extended testplan for affected components
[15:57] <asac> anyway tanks
[15:57]  * asac crosses fingers for fix and promotion
[15:57] <asac> thanks
[15:57] <sil2100> asac: right'o ;) I usually treat TRAINCON-1 as a 'transient state'
[15:57] <asac> yeah. i think you do serialization
[15:57] <asac> but not the other two aspects
[15:57] <sil2100> asac: we're also waiting for this fix badly, as it's really annoying - and it would be awesome to promote an image that only has 1 failure in smoketesting
[15:58] <asac> maybe rememer and see if thats useful by experimenting
[15:58] <sil2100> Ok
[15:58] <asac> think getting folks to run extended test plan makes sense
[15:58] <asac> for affected components
[15:58] <asac> and giving QA a chance to review those test plans also ... as the affected component seem to have slipped something
[15:59] <seb128> sil2100, can you assign/start build for l31?
[15:59] <seb128> sil2100, I've some auth issues here
[16:00] <cjwatson> seb128,sil2100: I'll do it
[16:00] <seb128> cjwatson, thanks
[16:00] <cjwatson> god it's so easy to fumble-finger the damn useless spreadsheet.  what was cell A30 supposed to say?
[16:00] <cjwatson> I hit space by mistake
[16:01] <asac> ctrl-z
[16:01] <Laney> you might be able to click off it and use the undo button
[16:01] <asac> :)
[16:01] <cjwatson> oh, fortunately it didn't actually save
[16:01] <asac> if you are lucky
[16:02] <cjwatson> sil2100: remind me, silo 6 is a test silo isn't it?
[16:02] <cjwatson> (this conflicts with it)
[16:03] <sil2100> cjwatson: yeah, I know it was in the past, but not sure if it's not soon-to-be-landed now
[16:03] <sil2100> kgunn: ^ ?
[16:03] <sil2100> kgunn: is silo 6 landing soon? Or can we conflict with it?
[16:03] <sil2100> robru: piiing, meeting
[16:08] <ogra_> jhodapp, we dont have scene selection in the mediaplayer, right ?
[16:08] <ogra_> (and wont for RTM)
[16:08] <jhodapp> ogra_: correct...design actually doesn't even have it anymore
[16:08] <ogra_> jhodapp, so why do we run the scene selection tests in the mediaplayer test suite ?
[16:09] <jhodapp> ogra_: it just hasn't been updated yet
[16:09] <jhodapp> ogra_: but it's a good point, problem solved then :)
[16:09] <seb128> cjwatson, sil2100: just conflict with it, I already did a landing of settings today conflicting, they are going to need to rebaase
[16:09] <jhodapp> ogra_: but I would like to know why that test causes media-hub to crash
[16:09] <cjwatson> seb128: fair point
[16:13] <elopio> jhodapp: I'll work a little on the media player suite to make it cleaner, and remove that test.
[16:13] <kgunn> sil2100: silo-006 is QtComp...so yeah, its testing, we won't land until next week at the earliest...but since we
[16:13] <elopio> that won't fix anything, but maybe it will make it clear what's crashing.
[16:13] <kgunn> did a call for testing please tell us if you rebuild
[16:13] <jhodapp> elopio: thanks
[16:13] <kgunn> a package we rely on....
[16:13] <elopio> or we will stop seeing the crash. Or we will get a new mysterious crash.
[16:13] <cjwatson> kgunn: as seb128 said, ubuntu-system-settings was already published earlier today and conflicted with that, so you were going to have to rebuild anyway
[16:13] <ogra_> yay
[16:13] <cjwatson> kgunn: but there's now another one in silo 5
[16:14] <kgunn> cjwatson: thanks for the heads up
[16:19] <Laney> retoaded: hi, can you help with https://jenkins.qa.ubuntu.com/job/autopilot-testrunner-otto-utopic/1299/testReport/junit/ubuntu_system_settings.tests.test_about/AboutTestCase/test_imei_information_is_correct_with_mouse_/ a bit please?
[16:19] <Laney> can I see dmesg from a failing run?
[16:20] <retoaded> Laney, looking
[16:22] <Laney> I don't quite know how to make it fail locally yet
[16:23] <retoaded> Laney, dmesg from the system the test ran on?
[16:23] <Laney> yeah
[16:24] <Laney> want to see if apparmor is complaining maybe ...
[16:24] <retoaded> Laney, will see what I can gather
[16:24] <cjwatson> jdstrand: Did you notice the click-apparmor autopkgtest regression?
[16:32] <retoaded> Laney, dmesg output sent via email
[16:33] <Laney> ty
[16:33] <retoaded> np
[16:43] <Laney> retoaded: do you have any information about how I can reproduce this setup?
[16:46] <cjwatson> mandel: ^- disregard that failure for now; I retried it already and will do a watch-only build if it works
[16:47] <retoaded> Laney, I can provide you the hardware specifics and package list
[16:51] <jdstrand> cjwatson: yes, I'll look at it. interesting I didn't see it when running that in a schroot
[16:54] <jdstrand> those are the new tests I added'
[16:54] <jdstrand> hmm
[17:08] <davmor2> o/ all have a nice week
[17:19] <cjwatson> mandel: can you retest silo 11?  I think that "testing pass" is from the earlier run, so I reset it
[17:34] <cjwatson> sil2100: (we should sort out a shift plan for next week)
[18:04] <pmcgowan> robru, is it ok that system settings is in two silos
[18:04] <pmcgowan> kenvandine, ?
[18:04] <kenvandine> no... it shouldn't be able to be
[18:05] <kenvandine> afaik
[18:05] <cjwatson> pmcgowan: see discussion about two hours ago between me, seb128, kgunn
[18:06] <cjwatson> pmcgowan: silo 6 already needed to be rebuilt due to an ubuntu-system-settings change earlier today, so there was no additional harm to it in doing another one
[18:06] <pmcgowan> cjwatson, got it
[18:07] <kenvandine> cool
[18:07] <kenvandine> i'm testing from silo 5 now
[18:22] <kenvandine> silly me... applied an image update after updating settings from the silo ppa
[18:22] <kenvandine> :)
[18:27] <robru> pmcgowan, it's "ok", but it requires coordination between the people owning those two silos.
[18:28] <robru> pmcgowan, kenvandine: so if you guys want to publish silo 5 soon, we just need to work with kgunn to rebuild system-settings in his silo
[18:28] <kgunn> yep...just ping me
[18:28] <kenvandine> robru, almost ready
[18:29] <kenvandine> yup... all good
[18:29] <robru> oh heh, didn't read all the scrollback, just what was highlighted.
[18:29] <kgunn> fwiw, i noted on the call for test QtComp wiki that image125 is last-good-known image.....and if it breaks on latest use that
[18:29] <kgunn> so temp break is perfectly ok
[18:32] <kenvandine> pmcgowan, i think settings is ready to publish
[18:32] <pmcgowan> sweet - whats in that
[18:32] <pmcgowan> the 2g thingy, carrier fixes, qofono
[18:33] <pmcgowan> phone #
[18:33] <kenvandine> pmcgowan, yeah
[18:33] <pmcgowan> nice
[18:33] <kenvandine> and sim services enabled
[18:35] <robru> kenvandine, do you want me to publish silo 5? can you mark it testing:done in the spreadsheet?
[18:36] <kenvandine> robru, done
[18:36] <kenvandine> can i click publish too?
[18:36] <robru> kenvandine, thanks
[18:36] <robru> kenvandine, nah that's my job
[18:36] <kenvandine> it's yelling my name :)
[18:36] <robru> kenvandine, oh right, you're a core dev, so actually you can publish if you want to! ;-)
[18:36]  * kenvandine clicks the button
[18:38] <kenvandine> i still think dput is easier than clicking the publish button :)
[18:40] <robru> kenvandine, well, dput rejects me, so clicking this button is all I got ;-)
[18:42] <kenvandine> haha
[19:31] <jdstrand> ok, click-apparmor 0.2.9 will fix the autopkgtest issue
[19:31] <jdstrand> sorry about that
[19:33] <jdstrand> (it was a poorly written test)
[19:57] <robru> kgunn, you can rebuild system settings now if you're ready
[19:57] <kgunn> thanks man
[19:57] <robru> kgunn, you're welcome!
[20:35] <alecu> trainguards: hi, may I ask for a silo for this MP? https://code.launchpad.net/~alecu/unity-scope-click/merge-devel3/+merge/226532
[20:51] <robru> alecu, can you add that to the spreadsheet?
[20:51] <alecu> robru: sure
[20:51] <robru> alecu, just slip that in row 26 there: https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFVHQ3FuMDJGLUZCamJfSjYzbWh3Wnc#gid=0
[20:55] <alecu> robru: done. I've filled the columns I knew what to put in
[20:55] <robru> alecu, great, just need your irc name in B26 and then when you're ready set I26 to "Yes"
[20:55] <alecu> done
[20:56] <robru> alecu, ok, you got silo 5, should show up at http://people.canonical.com/~platform/citrain_dashboard/#?q=alecu shortly
[20:56] <alecu> robru: thanks!
[20:56] <robru> alecu, you're welcome!
[20:57] <robru> there it is ;-)
[20:58] <alecu> I've rode this train a few times, but it's the first time I get to buy the tickets
[20:58] <robru> alecu, heheh well I'm here to help if you need. that link I gave has the 'build' link to trigger the build
[20:59] <alecu> robru: so, if I need to update the branch with any fix, I would need to check FORCE_REBUILD?
[21:00] <robru> alecu, hmmmm, that should only be necessary if you're rebuilding with no changes. if there's new commits it should notice and do the build without that flag set
[21:00] <alecu> yup, after re-reading I understood just that
[21:01] <alecu> thanks for the hand-holding.
[21:01] <robru> alecu, no worries, I'm in charge of making it run smoothly ;-)
[21:19]  * robru wonders who will be the lucky winner of the 1,000th silo!
[22:09] <alecu> robru: I've added two more revs to my branch, but trying to rebuild I got the above ^
[22:10] <robru> alecu, ah ok, do the force_rebuild then
[22:10] <alecu> great
[22:11] <robru> alecu, ah, also ignore_step ;-)
[22:16] <mhr3> ehm?
[22:16] <mhr3> line 16?
[22:16] <mhr3> that already landed
[23:12] <alecu> yay
[23:19] <slangasek> Saviq: so, trying to figure out http://people.canonical.com/~platform/citrain_dashboard/#?q=landing-006... which points to https://ci-train.ubuntu.com/job/landing-006-1-build/107/console, which says "Build was aborted // Aborted by Michał Sawicz"
[23:19] <Saviq> slangasek, yeah, already restarted with the correct bits
[23:19] <slangasek> ok
[23:19] <Saviq> slangasek, forgot allow_unapproved
[23:19] <slangasek> mm, what does that mean :)
[23:20] <Saviq> slangasek, starting like a week ago builds will fail by default if MP is not top-approved
[23:20] <Saviq> this checkbox lets you lift that restriction
[23:20] <slangasek> ah
[23:20] <slangasek> why do that, vs. top-approving
[23:20] <Saviq> slangasek, for test silos, things that are in-flight
[23:21] <slangasek> Saviq: ok; so this is a test silo only?
[23:21] <slangasek> Saviq: I'm asking to figure out the status of qtmir
[23:21] <slangasek> which I guess needs a NEW review at some point
[23:22] <Saviq> slangasek, yeah, it's not a purely-test silo any more
[23:22] <Saviq> slangasek, it's being dogfooded, and pending reviews will be converted to a real one soon
[23:23] <Saviq> slangasek, I was messing with it to include the fix for https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1341007
[23:23] <slangasek> ok; so I'll wait for that before doing the NEW review
[23:23] <Saviq> slangasek, yeah, still a few days away
[23:29] <slangasek> pmcgowan: so I asked ogra whether we were ok to cull http://cdimage.ubuntu.com/ubuntu-touch-preview/ from the server, and he directed me to you
[23:29] <slangasek> pmcgowan: is anyone still using these?  This is all quantal/raring stuff, way stale
[23:53] <slangasek> plars, fginther: who maintains the chroots (or whatever environment) jenkins uses for prepping source packages for ppa dput?  working with robru, I've noticed the console log for silo-008 shows it upgrading all kinds of base packages... looks like there ought to be a regular refreshing of the base system? https://ci-train.ubuntu.com/job/landing-008-1-build/124/console
[23:54] <slangasek> (instead of, say, upgrading perl-base once for every source package in every silo)
[23:57] <slangasek> the log shows apt 1.0.2ubuntu2, which was superseded in utopic on June 12... having the chroots a month out of date is probably quite long enough :)