imgbot=== trainguard: IMAGE 125 building (started: 20140711 02:05) ===02:04
=== alf is now known as 6JTAAQ1J9
=== kgunn is now known as Guest2511
=== Ursinha is now known as Ursinha-afk
bzoltan1robru: good morning, the silo13 is good to go03:19
=== Ursinha-afk is now known as Ursinha
imgbot=== trainguard: IMAGE 125 DONE (finished: 20140711 03:35) ===03:34
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/125.changes ===03:34
ToyKeeper... and a new image, mere seconds after I finished testing the last one.03:35
alecuI'm in the middle of downloading 124... :-)03:37
alecuit takes quite a while to move all those bits down here.03:38
bzoltan1it is good to see that the new UITK did fix couple of  failing tests04:00
bzoltan1is anybody doing the European tz shift?04:37
brendandsil2100, i think we can get our green image today :)06:56
sil2100brendand, ogra_: did you guys see our test results for 125 :D ?06:56
brendandsil2100, yes and we have fixes for both those!06:56
sil2100brendand: yeah, especially that the mediaplayer issue has a branch already, notes should be easy to fix as well06:56
brendandsil2100, land silo005 and popey land my notes app fix06:56
sil2100I... I think I'm going to cry!06:57
brendandsil2100, popey needs to look after https://code.launchpad.net/~brendan-donegan/notes-app/bug1330352/+merge/22614606:57
brendandsil2100, get it merged and updated in the store06:57
* sil2100 looks at popey waiting for him to wake up06:59
=== robru changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #119 promoted | CI Train Sheriff: sil2100 | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
brendandpopey, popey - wake up wake up!07:06
brendandCI christmas is here!07:06
sil2100Anyway, jokes aside, I'm glad that the networking issue got resolved07:06
brendandsil2100, yes. that's good to see07:06
sil2100I'm glad we didn't revert - it seems sometimes it's good to just give upstreams some time for a fix07:07
Mirvindeed, awesome colors this time07:07
brendandsil2100, well yes, but also i would agree that we can't go 2-3 days with no results07:16
brendandsil2100, so reverting might have been necessary in the end07:16
brendandsil2100, but thankfully it wasn't :)07:16
Mirvbrendand: sil2100: who should be pinged about the notes-app branch?07:16
brendandsil2100, 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 breaking07:16
brendandMirv, popey i think takes care of it07:17
brendandMirv, dpm also might be able to do a review07:17
brendandMirv, but popey needs to upload it i think07:17
brendandanyway - bbl for the meeting07:17
Mirvbrendand: I can upload, popey can approve it in the store, but someone needs to get the branch to the trunk07:18
sil2100brendand: yeah, we might try a low velocity approach today, let me talk with cjwatson on the meeting :)07:18
dpmbrendand, I've not had anything to do with notes-app, so I'm not sure I can help07:23
MirvBill top-approved the previous thing that went in to notes-app07:36
sil2100We can't wait that long!07:39
cjwatsonsil2100: shall I take over sheriff?08:27
sil2100cjwatson: morning! Yes please ;) We were just thinking if maybe we could try doing it 'safe' today08:29
=== cjwatson changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #119 promoted | CI Train Sheriff: cjwatson | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
sil2100i.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 right08:30
sil2100But more on the meeting08:30
cjwatsonRight, well, I can't do much in the way of personal testing, not enough bandwidth08:30
cjwatsonSo hopefully that won't be needed ...08:30
cjwatsonOur opinions of riskiness might differ ;-)08:31
psivaasil2100: am i on the wrong hangout... or you are yet to join?08:32
sil2100psivaa: maybe wrong hangout ;)08:32
sil2100We're all here08:32
brendandsil2100, i think everything should be thoroughly tested regardless of whether it's risky08:43
brendandcjwatson, my definition of risky would be packages that have lots of rdeps08:43
cjwatsonremind me what the justification for extra care in this particular instance is?08:44
cjwatson(I see we're low on silos again)08:45
cjwatson(discussing in hangout)08:47
seb128sil2100, do you know what's the status of the qtcompositor work?08:48
seb128sile 00608:48
seb128I wonder if I can hijack it for a settings landing08:48
seb128e.g do a landing and force them to rebuild settings then08:48
Laneyseb128: want to take the activation fixes?08:50
LaneyI don't think we'll get tests for those any time soon08:51
seb128Laney, ok08:51
* Laney files a dbusmock bug as a reminder08:51
sil2100seb128: I would say it's safe to do a landing, didn't hear anything from them about it being ready08:56
seb128sil2100, thanks, I just did that ^08:57
* sil2100 goes back to testing his auto-merge-and-clean functionality08:57
sil2100It's hard to test in a safe environment08:57
cjwatsonWell, can't do much until testing happens, so going back to parted packaging work for a bit09:01
cjwatsonnot assigning that right now as only one silo left09:02
seb128cjwatson, 0 left now09:05
mvo_seb128: that was me :/ sorry09:05
seb128mvo_, no worry ;-)09:06
seb128I still don't get why you assign silos to people who do it themself btw :p09:06
Laneysilo hog!09:06
seb128who *can* do it*09:06
mvo_right, lets make the landings quick so that we can have free silos again :)09:07
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:09
sil2100mvo_: sure, no problem ;)09:15
brendandcjwatson, what about landing silo005? it's been top-approved and tested09:16
sil2100mvo_: all the code is in the google scripts for the spreadsheet09:16
cjwatsonbrendand: oh, spreadsheet says "testing done: no"09:17
cjwatsonbrendand: I thought you said you weren't sure about the testing, earlier09:17
sil2100brendand: let's make sure ricmm +1'es it finally09:18
sil2100ricmm: hi! Did you test everything for silo 005?09:19
brendandsil2100, oh yeah ricmm is here09:19
ricmmsil2100: I'm happy with it, I've tested and so has jim09:20
ricmmpush the buttonz09:20
cjwatsonricmm: will do09:20
sil2100ricmm: thanks o/09:21
cjwatsonI've acked those09:23
popeyMirv: 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:26
bzoltan1ohh, I see we are out of silos09:41
mvo_sil2100: silly question but what is the best way to test my script addition?09:42
bzoltan1zbenjamin:  is it possible to make the main project file open in the editor?09:43
seb128yeah, get mhr3__ or thostr_ to test/land some of their "built" lines maybe09:43
thostr_seb128: I'm properly testing those still09:44
sil2100mvo_: 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 script09:44
seb128thostr_, ok09:44
seb128thostr_, is the transfert indicator used anywhere yet?09:44
mvo_sil2100: ok, I will play around, not a lot that can break I guess09:44
thostr_yes, e.g. when doing "save image as" browser09:44
mvo_sil2100: are the script in some sort of version control inside the google doc?09:45
sil2100mvo_: sadly not...09:45
thostr_and oSoMoN told me two days ago that browser had a landing prepared to fully use it09:45
seb128thostr_, great, thanks09:46
oSoMoNthostr_, "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:47
thostr_oSoMoN: ah, worked earlier this week...09:48
Mirvpopey: weather app done10:05
popeythanks Mirv10:06
sil2100popey, 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 merged10:11
sil2100oSoMoN: ^ 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 components10:11
* oSoMoN reads10:12
sil2100oSoMoN: I'm talking about this merge:10:12
sil2100oSoMoN: https://code.launchpad.net/~brendan-donegan/notes-app/bug1330352/+merge/22614610:12
Saviqseb128, xnox, silo 20 +1 from me re: inheritance and cross-build10:13
sil2100oSoMoN: it's fixing the only test failure we have that appeared after the UITK upload, and Leo from QA +1'ed it already10:13
oSoMoNsil2100, LGTM10:13
cjwatsonsil2100: yeah, let's give that silo 510:14
cjwatsonbefore somebody self-assigns it :)10:14
seb128Saviq, +1 on the gtk 3.12 side10:15
seb128xnox, ^10:15
sil2100Yeah ;) Let me fill in a landing for it maybe10:15
sil2100brendand: I'll set you as a sub-lander for this one10:16
xnoxseb128: let me run ubiquity.10:17
bzoltansil2100: any chance to get a silo for the line 30?10:17
sil2100bzoltan: we're a bit low on silos right now, but we'll have a fast landing soon and you can get that one then10:18
bzoltansil2100: OK, thanks10:18
sil2100cjwatson: I'm assigning a silo for this one10:18
cjwatsonsil2100: for notes-app?10:18
sil2100cjwatson: yes10:19
cjwatsonyes please10:19
brendandsil2100, does it need a silo?10:19
brendandsil2100, i thought it went to the store?10:19
sil2100brendand: yes, it needs one...10:19
cjwatsonbzoltan: (context: notes-app is the last failing test from the most recent mako test run ...)10:19
sil2100brendand: I checked and it seems there is no auto-merger, but merges are done through CI Train10:19
brendandsil2100, ok. but Mirv still needs to upload it to the store right?10:20
sil2100brendand: yes, once this gets merged10:20
cjwatsonnotes is a preinstalled app, so it ends up on images via http://people.canonical.com/~ubuntu-archive/click_packages/10:21
cjwatsonbut that gets it from the store, yes10:21
cjwatsonbzoltan: how long is this going to take to test?10:22
bzoltancjwatson:  I have tested the changes already10:22
cjwatsonbzoltan: to test the built package from the silo10:23
bzoltancjwatson:  the build will take ages10:23
cjwatsonseb128: 20 tested on the phone?10:23
bzoltancjwatson:  few minutes, the change is only text change no binary change10:23
cjwatsonseb128: (just to make sure suru didn't explode)10:24
seb128cjwatson, not by me, I can do that now10:24
seb128let me try10:24
bzoltancjwatson:  but the silo build  took yesterday about 4 hours ...10:24
cjwatsonbzoltan: the last build on record took <30 minutes10:24
popeysil2100:  if it only changes the tests, then it doesn't need pushing to the store, does it? (notes)10:24
popeysil2100: because the phablet test run will pull tests from trunk10:25
bzoltancjwatson:  of course ... each took only half an hour. But queuing for powerpc builder took 3 hours10:25
cjwatsonbzoltan: that won't be a problem10:25
sil2100popey: 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 installed10:25
sil2100popey: so even in this case we'll have to release, as otherwise it will fetch the older one anyway10:26
Mirvif in desperate need of silos, I think line 7 (trusted prompt session) could be temporarily freed. quite light to rebuild.10:26
Mirvsince it's only for testing10:26
sil2100Saviq: how about silo 009? Is it planned to land today or can we flush it?10:27
Saviqsil2100, flush it if you need10:27
popeysil2100: ok, ping once that lands in trunk and we'll get it in the store, Mirv can upload, I'll approve10:27
sil2100popey: thanks, will do o/10:27
sil2100Saviq: thanks10:27
xnoxseb128: all is good on ubiquity side10:28
xnoxand 1px gap is gone between ubiquity fake-panel and opened fake-indicators10:28
* xnox like10:28
xnoxwe should be able to publish & clean 2010:28
brendandsil2100, cjwatson - i'm making myself available for extra testing if needed, so just ask10:28
sil2100cjwatson: 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 00910:28
cjwatsonFYI I have a 1.5 hour meeting shortly10:29
bzoltanMirv: pick me, pick me :)10:29
Saviqxnox, 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 that10:29
cjwatsonI'm just going to assign 18 to bzoltan since we have a couple that will be freeable if it becomes necessary10:30
xnoxSaviq: you mean, cross-building telepathy-service?10:30
bzoltancjwatson: \o/10:30
Saviqxnox, yes10:30
cjwatsonbig "low on silos" warning I see, thanks mvo :)10:30
Saviqxnox, it cross-built fine (with silo 20 + :any for python)10:30
seb128xnox, cjwatson: +1 suru on the device10:30
Saviqxnox, but it ran tests10:30
cjwatsonseb128: thanks, I see it's publishing now10:31
xnoxSaviq: what's the source package name? "E: Unable to find a source package for telepathy-service"10:31
cjwatsonbzoltan: go ahead and build now, I will poke builders as needed (but doesn't look like it should be)10:32
bzoltancjwatson: OK, thanks10:32
xnoxSaviq: i guess telephony-service, not telepathy ;-)10:34
xnoxSaviq: yeah, the dh_auto_test is wrong.10:35
Saviqxnox, did I write telepathy? sorry10:36
Saviqxnox, yes, telephony10:36
Mirvbzoltan: :)10:44
xnoxSaviq: http://paste.ubuntu.com/7779678/10:54
Saviqxnox, yup, thought something like that would work, thanks!10:56
Mirvhmm, why does publish for notes say the last step wouldn't have been completed11:10
cjwatsonMirv: probably because it hasn't finished migrating yet11:10
brendandcjwatson, Silos: landing-005 (sil2100, brendand) Can't publish: wrong status or parameters for job. (notes-app)11:11
brendandcjwatson, i didn't see that before11:11
cjwatsonbrendand: probably because it hasn't finished migrating yet11:11
cjwatsonmerge-and-clean normally wants the changes to be at least pending in the release pocket first11:12
Mirvcjwatson: migrating where? it has built and I'm trying to publish it11:12
Mirvlukasz was faster :D11:12
sil2100brendand, Mirv: well, I pressed publish and then Mirv pressed it again11:12
cjwatsonmaybe two of you tried at the same time?11:12
sil2100So don't worry about it11:12
* sil2100 goes for lunch11:12
Mirvno problem then, nice11:12
Mirvsomehow I missed that last job's timestamp or maybe my page wasn't refreshed11:13
=== MacSlow is now known as MacSlow|lunch
bzoltancjwatson: the QtC plugin from the silo18 is good to go11:19
xnox!ci-help I've tried to run "merge & clean" on silo 20, yet it fails.11:22
ubot5xnox: I am only a bot, please don't think I'm intelligent :)11:22
xnoxSaviq: seb128: any clue why merge&clean does not work against silo 20?11:24
Mirvxnox: Saviq ran it before you11:26
xnoxMirv: ah.11:26
Saviqcould probably use better error messaging ;)11:27
=== MacSlow|lunch is now known as MacSlow
bzoltanMirv:  is there anything I could do to speed up the landing of the Silo18 landing?11:34
Mirvbzoltan: published11:37
bzoltanMirv: thank you11:39
popeyMirv: 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:43
Mirvpopey: done11:47
cjwatsonbzoltan: (sorry, on a call)11:52
bzoltancjwatson: all fine now, the silo will be cleaned soon11:53
brendandMirv, so is notes app uploaded?11:56
Mirvbrendand: yep, not yet merged to trunk11:57
Mirvok, now in release pocket 1 min ago11:57
cjwatsonany objection to me building another image once notes-app is published?12:00
brendandcjwatson, i was just about to ask you to build one :)12:00
Mirvcjwatson: no objections, but we need to wait for the click one12:00
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.click12:01
cjwatsonis it that?12:01
brendandcjwatson, but yeah - popey needs to approve notes-app in the store12:01
cjwatsonthat'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:01
popeybrendand: someone needs to upload it first12:02
cjwatsonmvo_: not at all, it'll be yet another "source won't unpack" problem12:03
Mirvcjwatson: 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 again12:03
cjwatsonmvo_: 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
brendandpopey, Mirv  is meant to be doing that12:03
mvo_cjwatson: thanks, that is very helpful!12:04
popeybrendand: ping me when done, not before ☻12:04
cjwatsonah, yeah, that's revno 269, can't be right, we're expecting revno >=27412:05
cjwatsonindicator-transfer isn't on any images, so I'll publish it12:08
=== alan_g is now known as alan_g|lunch
Mirvbrendand: popey: http://s-jenkins.ubuntu-ci:8080/job/notes-app-click/74/artifact/out/com.ubuntu.notes_1.4.275_armhf.click12:09
Mirvshall I just upload that, or do you want to test it first?12:10
popeynope, just upload it, its been through CI/Jenkins/QA right? ☻12:10
brendandMirv, no it's alright just upload it12:12
brendand(famous last words)12:12
Mirvbrendand: popey: done12:12
brendandpopey, ping :)12:13
brendandpopey, so cjwatson can kick a build?12:14
brendandpopey, or do we need to wait for the process to filter through?12:14
cjwatsonbrendand: I can12:14
* cjwatson forces a click-sync12:15
brendandcjwatson, i meant, if you kick a build now will we be guaranteed to get the new version of the click package?12:15
cjwatsonbrendand: I'm making sure of that first12:15
brendandcjwatson, i guess the answer is yes12:15
cjwatsonubuntu-archive@snakefruit:~$ grep notes public_html/click_packages/click_list12:15
cjwatson(the cron job runs at :11 and :41; I ran it by hand)12:16
brendandlet's do this build12:21
cjwatsonalready queued12:22
cjwatsonrunning in fact; no doubt some bot will notice at some point12:22
imgbot=== trainguard: IMAGE 126 building (started: 20140711 12:25) ===12:24
brendandcjwatson, :)12:24
cjwatsonstgraber: is it possible for queuebot to tell us about ubuntu-touch image builds?  seems like it should be able to manage lower latency12:26
ogra_cjwatson, do you have an idea why sudo -s would behave different to bash -c when executed via a forked execl ?12:29
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 ls12:30
ogra_/bin/bash: sudo ls: command not found12:30
ogra_ogra@anubis:~/image-stuff$ adb shell12:30
ogra_while when using bash -c for the shell command the same code works just fine and takes the last arg as command with options12:31
cjwatsonsigh, things that take a command and don't act in a sensible adverbial fashion are the devil incarnate12:32
ogra_well, i dont get why sudo behaves different here ...12:33
cjwatsonno doubt it's overquoting somewhere12:33
cjwatsonsudo -u$USER sudo ls12:34
cjwatsonsudo -u$USER "sudo ls"12:34
cjwatsonapparently your code is doing something analogous to the second one12:34
cjwatsonthe first one is actually a much better design for commands that take other commands12:34
cjwatsonbut you may need to adjust for it12:34
ogra_well it simply hands it over to execl12:34
ogra_there is no mangling of "arg2" anywhere12:34
jdstrandoSoMoN: fyi, that issue should be fixed now in apparmor-easyporf-ubuntu 1.2.9, which was in utopic last night12:34
cjwatsonsounds like this is terrible design of adb12:35
ogra_it is12:35
cjwatsonI 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 calls12:35
cjwatsonso you need to either separate them again, or (perhaps simpler) use sudo -u$USER -s bash -c12:36
ogra_cmd being sudo ... arg0 being -uphablet ... arg1 being -s12:36
cjwatsonthen the subsidiary shell will word-split the string for you12:36
ogra_isnt -s actually executing bash -c ?12:36
cjwatsonnot with the same quoting12:36
ogra_ah ...12:36
* ogra_ tries12:36
cjwatsonyou are expected to pass command and arguments as separate arguments12:36
cjwatsonwhereas bash -c takes a single string12:37
cjwatsonactually you should probably drop the -s, then12:37
cjwatsonsudo -u$USER bash -c12:37
cjwatsonotherwise you'll have an unnecessary shell in the process tree12:37
cjwatsonand yeah, kick whoever misdesigned adb shell :P12:38
* ogra_ kicks google12:38
=== psivaa is now known as psivaa-lunch
davmor2oh new scopes12:46
ogra_cjwatson, thanks ... that works !!12:46
davmor2ogra_: does this release have the deadlock fix?12:46
ogra_davmor2, i dont think it does ... sil2100 might know though12:47
ogra_bah ...12:48
ogra_but now something like: "adb shell sudo ls" echos the password to the screen :(12:49
ogra_seems stdin/out are not right12:49
cjwatsonogra_: cool12:55
cjwatsonogra_: that sounds like an incorrect $TERM setting, at a guess12:55
cjwatsonogra_: I see much strace in your future12:56
cjwatsonogra_: or, yeah, I guess it could be stdin not wired up quite right12:56
sil2100oh, it seems I got disconnected13:06
ogra_so you did13:07
ogra_sil2100, davmor2 asked where we stand with the lockup fix ... do you know ?13:07
davmor2sil2100: 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 unbearable13:08
sil2100davmor2, ogra_: sadly, from what I know there have been some things they still wanted to work on, the fixes aren't complete13:09
sil2100I need to poke Kevin some more today13:09
sil2100Anyway, I would not expect any promotion today anyway13:09
davmor2sil2100: that sounds so wrong13:09
davmor2sil2100: :(13:11
sil2100davmor2: 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 issues13:11
sil2100The other branches are still on hold13:12
* davmor2 sees his dream of popey in a green t-shirt slowly dirft away :)13:13
sil2100Hey! It's possible! We only need all tests passing ;)13:14
sil2100We don't need a promotion!13:14
=== alan_g|lunch is now known as alan_g
sil2100And/or working tablet images13:15
sil2100ogra_: so 126 is still building, right?13:20
sil2100davmor2: anyway, as per discussion with kgunn, we migh have a final fix for this later today13:24
cjwatsonmhr3: just checking because apparently we're being extra-careful today, what testing did you (or whoever?) do on silo 14?13:24
sil2100So no worries13:24
mhr3dobey, ^^13:24
davmor2sil2100: \o/ :) that makes me happier13:24
seb128sil2100, who has access to the landing functions of the google doc?13:26
stgrabercjwatson: 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
dobeycjwatson: tested the click scope and deleted/re-added the account13:26
seb128sil2100, can we get kenvandine added to whatever group that is?13:26
imgbot=== trainguard: IMAGE 126 DONE (finished: 20140711 13:50) ===13:49
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/126.changes ===13:49
plarsxnox: did you see my email about the utopic install problems?13:49
=== Ursinha is now known as Ursinha-afk
plarsooo, Will the new notes app make us even more green?13:50
ogra_plars, yeah13:52
ogra_plars, well, i guess popey broke the facebook app to compensate for this13:53
popeyalso sudoku13:53
plarsogra_: 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:53
plarspopey: at least on 125, sudoku passed I thought13:54
ogra_plars, if we are sure autoremove really removes everything13:54
ogra_phablet@ubuntu-phablet:~$ ./get-deps.sh 12613:54
ogra_New packages: liburcu213:54
ogra_src: ust, bin: liblttng-ust-ctl2 depends on liburcu213:54
ogra_src: ust, bin: liblttng-ust0 depends on liburcu213:54
ogra_ust depends on liburcu213:54
* ogra_ hugs his new dependency checker script 13:55
ogra_no more new packages that we dont know where they come from :)13:55
popeyplars: new one in 126 ☻13:55
plarsogra_: I'm still unclear on why it didn't remove it before13:55
plarspopey: yes, but sudoku worked, I like to see changes to packages that weren't fully green :)13:56
plarsogra_: I can do a test run without it that doesn't go to the dashboard and see if there are any weird results13: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 autoremove13:57
ogra_(run autoremove still, to get rid of additional deps)13:57
ogra_plars, yeah, do that and see13:57
sil2100Just please don't do that yet for run 126 ;)14:02
=== Ursinha-afk is now known as Ursinha
=== psivaa-lunch is now known as psivaa
xnoxplars: 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:16
plarsxnox: 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 image14:17
plarsxnox: 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 though14:18
brendandsil2100, agh - mediaplayer-app did get the failure :/14:21
brendandsil2100, looks like my concern was right14:21
sil2100Sadly, no 100% green image today it seems14:22
seb128sil2100, 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
sil2100seb128: I can add him if needed, no problem14:22
ogra_(remember that failing test is supposed to be skipped)14:22
sil2100ogra_: it was supposed to remove the media-hub crash14:22
seb128sil2100, that would be nice14:22
ogra_sil2100, oh, the crash14:23
sil2100ogra_: and it's the media-hub crash that caused the test not to be skipped...14:23
ogra_sil2100, ah14:23
sil2100At least that was my understanding14:23
sil2100But it seems something else is crashing now or such14:23
sil2100brendand: ^14:23
ogra_well, lets see til the crashes get synced14:23
ogra_i only see the non skipped tests atm14:23
sil2100seb128: added14:23
seb128sil2100, thanks14:24
sil2100yw o/14:24
* brendand updates to find out about the mediahub-server crash14:27
sil2100brendand: thanks!14:30
plarsxnox: istr you mentioned there were some pre-existing bugs in ubiquity that you thought could be related to what I described?14:34
brendandsil2100, crazy. the error is the same one that the landing was supposed to fix...14:35
brendandsil2100, did something go wrong?14:35
sil2100brendand: shouldn't have, it seems media-hub landed properly14:36
=== alan_g is now known as alan_g|tea
=== alan_g|tea is now known as alan_g
ogra_hey, but at least notes-app passed fine :)14:49
xnoxplars: all of which have been subsequently fixed by now.14:53
xnoxplars: and none of them were/are present in trusty images, which are now failing.14:53
xnoxplars: including the trusty 14.04.0 image.14:53
xnoxplars: ubiquity issues were introduced in utopic, and fixed in utopic by now.14:54
plarsxnox: 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 utah14:54
xnoxplars: let me redo physical machine testing with ubiquity desktop cd here.14:55
sil2100robru: so, looking at the changes you made, it seems you introduced a security hole in our CI Train ;)14:55
xnoxplars: 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:55
sil2100robru: I think we'll have to revert your recent addition of running jobs easily without an additional button click14:56
xnoxplars: what i need is fsuer / lsof output for /target, before the unmount happens in ubiquity.14:56
xnoxi guess i can put that in ubiquity itself.14:56
sil2100robru: sadly, using the authToken is by-passing the authentication of jenkins itself, which means basically anyone that knows the token can now run the job14:57
plarsxnox: if we can get some sort of debug build, I'd be happy to give it a try here14:57
xnoxplars: cause otherwise, if 14.04.0 fails to install on physical hardware in auto-preseeded mode, we have huge problems.14:57
sil2100robru: which basically means anyone can now assign new silos - and since citrain is being hosted on bzr, basically everyone has the token ;)14:58
xnoxplars: 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.14:59
xnoxplars: and local utah setup that i used to have, is no longer operation and fails starting to provision anything.15:00
plarsxnox: anything I can do from our side to help debug this?15:00
xnoxplars: (a) can i have access to a utah server that can run and provision machines that fail?15:03
xnoxplars: (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:03
xnoxplars: so far, i don't have access to any utah server which exibits the problem seen in the logs.15:04
plarsxnox: 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 late15:06
=== retoaded changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: retoaded | CI Train Status: #119 promoted | CI Train Sheriff: cjwatson | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
sil2100Is it only me or does the spreadsheet look strange?15:09
sil2100cjwatson: do you know why lines 27 and 30 seem to be landed, but the spreadsheet didn't register those?15:09
sil2100cjwatson: was merge and clean ran for those?15:09
sil2100Damn, things really seem to be b0rken15:10
sil2100Let me look into that in a moment...15:11
cjwatsonsil2100: pretty sure both of those were merged and cleaned15:13
sil2100cjwatson: yeah, I saw that they did, somehow CITrain didn't set those to 'Landed'15:14
cjwatson12:22 -queuebot:#ubuntu-ci-eng- Silos: landing-020 (Saviq, seb128) Empty (ubuntu-themes)15:14
cjwatson12:59 -queuebot:#ubuntu-ci-eng- Silos: landing-005 (brendand, sil2100) Empty (notes-app)15:14
sil2100I fixed that in the spreadsheet but I need to fix that15:14
cjwatsonwell that was after merging15:14
cjwatsonbut yeah, those silos are freed15:15
ogra_charles, what about the transfer indicator ... shouldnt we seed it ?15:15
sil2100It 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 scripts15:15
cjwatsonhttps://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/console15:15
cjwatsonI've so far seen Empty after the silo is no longer assigned to anything15:15
sil2100cjwatson: btw. I think we can land things normally now if anything15:16
brendandsil2100, i suppose just 1 failure, which we have a handle on is pretty good :)15:17
brendandnooooo, calculator and calendar - whyyyy!15:24
brendandit's in settle_after???15:24
brendandplars, do you know what settle_after is trying to do?15:25
ogra_brendand, it wants the system to go to 97.5% idle15:25
sil2100It checks if the CPU has settled, or is there something making it not idle enough15:26
plarsbrendand: yes, it's the same thing as settle_before15:26
plarsbrendand: basically making sure we don't have anything lingering after the test that is hogging the cpu15:26
ogra_brendand, we need the topafter.log to see whats the issue15:26
ogra_that is only synced at the end15:26
ogra_brendand, i'd blame our Mir issue though ...15:31
brendandogra_, what's our mir issue? did we land mir in this image?15:33
ogra_brendand, the Mir issue that makes my flo hang for 2min if i start an app etc ... which doesnt manifest that heavily on mako15:35
* cjwatson looks at 1415:43
cjwatsonyeah, that looks OK to me15:44
cjwatsonsil2100: normally> ack15:44
* sil2100 is still looking for the root cause of the spreadsheet behaving strangely15:45
* cjwatson acks 11 too15:47
sil2100hmmm, I think I see the reason for this, there might be a race condition due to google spreadsheet slowness15:49
cjwatsonmhr3: hm, is the connectivity-api/powerpc failure known-flaky?  I guess it must be because it built before15:50
cjwatsonmhr3: you're going to have to rebuild most of silo 11 anyway due to newer versions in utopic15:51
cjwatsonmhr3: and then (IMO) retest15:51
mhr3cjwatson, are you sure you wanted to talk to me?15:51
cjwatsonoh damn sorry15:51
asacsil2100: cjwatson: how is traincon going? do you have enough support from QA?15:51
cjwatsonmandel: ^- above few lines were meant for you15:51
sil2100asac: there was no need for traincon15:51
sil2100asac: as mentioned yesterday, the deal was to enter TRAINCON if the issue is not fixed15:52
asacso we promoted?15:52
sil2100asac: but it got fixed during the night and we had test results throughout all day15:52
sil2100asac: no, but we promoted recently, so no need for traincon ;)15:52
asaci feel i am more than 5 days outdated :)15:52
asacguess i am just impatient15:52
cjwatsonlast promotion was three days ago15:53
sil2100asac: 3 days ago15:53
sil2100So we still have a safe buffer15:53
asacwell, in theory there is a middle stage that we invented to manage to not need to go to expensive TRAINCON-015:53
mandelcjwatson, yes, is flaky15:53
sil2100asac: 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
asacbut well :)15:53
cjwatsonmandel: 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
sil2100asac: but we got down to 1 failure basically in smoketesting ;)15:54
mandelcjwatson, yes please, that would be very welcome15:54
asacTRAINCON-1 tries to give incentive to fix things because it makes landing of affected components more careful15:55
sil2100asac: yeah, we didn't land any Mir landings, so we're proceeding according to the rulse here ;)15:55
asacsil2100: only promotion blocker is Mir?15:55
sil2100As it's Mir that's affected and the root cause of our blocker15:55
sil2100Yes :)15:55
asacso withthat fixed we promote... cool15:55
asacso in theory we are in TRAINCON-1 :)15:55
asacjust that we dont send the QA folks on the MIR folks before doing the landing15:55
asacerr in practice i mean15:56
asacactually it doesnt ask for QA double check15:56
asacjust that landngs get serialized a bit15:56
cjwatsonmandel: trying15:56
asacand that landers get testplans reviewd by QA and that landers have to run extended testplan for affected components15:57
asacanyway tanks15:57
* asac crosses fingers for fix and promotion15:57
sil2100asac: right'o ;) I usually treat TRAINCON-1 as a 'transient state'15:57
asacyeah. i think you do serialization15:57
asacbut not the other two aspects15:57
sil2100asac: 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 smoketesting15:57
asacmaybe rememer and see if thats useful by experimenting15:58
asacthink getting folks to run extended test plan makes sense15:58
asacfor affected components15:58
asacand giving QA a chance to review those test plans also ... as the affected component seem to have slipped something15:58
seb128sil2100, can you assign/start build for l31?15:59
seb128sil2100, I've some auth issues here15:59
cjwatsonseb128,sil2100: I'll do it16:00
seb128cjwatson, thanks16:00
cjwatsongod it's so easy to fumble-finger the damn useless spreadsheet.  what was cell A30 supposed to say?16:00
cjwatsonI hit space by mistake16:00
Laneyyou might be able to click off it and use the undo button16:01
cjwatsonoh, fortunately it didn't actually save16:01
asacif you are lucky16:01
cjwatsonsil2100: remind me, silo 6 is a test silo isn't it?16:02
cjwatson(this conflicts with it)16:02
sil2100cjwatson: yeah, I know it was in the past, but not sure if it's not soon-to-be-landed now16:03
sil2100kgunn: ^ ?16:03
sil2100kgunn: is silo 6 landing soon? Or can we conflict with it?16:03
sil2100robru: piiing, meeting16:03
ogra_jhodapp, we dont have scene selection in the mediaplayer, right ?16:08
ogra_(and wont for RTM)16:08
jhodappogra_: correct...design actually doesn't even have it anymore16:08
ogra_jhodapp, so why do we run the scene selection tests in the mediaplayer test suite ?16:08
jhodappogra_: it just hasn't been updated yet16:09
jhodappogra_: but it's a good point, problem solved then :)16:09
seb128cjwatson, sil2100: just conflict with it, I already did a landing of settings today conflicting, they are going to need to rebaase16:09
jhodappogra_: but I would like to know why that test causes media-hub to crash16:09
cjwatsonseb128: fair point16:09
elopiojhodapp: I'll work a little on the media player suite to make it cleaner, and remove that test.16:13
kgunnsil2100: silo-006 is QtComp...so yeah, its testing, we won't land until next week at the earliest...but since we16:13
elopiothat won't fix anything, but maybe it will make it clear what's crashing.16:13
kgunndid a call for testing please tell us if you rebuild16:13
jhodappelopio: thanks16:13
kgunna package we rely on....16:13
elopioor we will stop seeing the crash. Or we will get a new mysterious crash.16:13
cjwatsonkgunn: as seb128 said, ubuntu-system-settings was already published earlier today and conflicted with that, so you were going to have to rebuild anyway16:13
cjwatsonkgunn: but there's now another one in silo 516:13
kgunncjwatson: thanks for the heads up16:14
Laneyretoaded: 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
Laneycan I see dmesg from a failing run?16:19
retoadedLaney, looking16:20
LaneyI don't quite know how to make it fail locally yet16:22
retoadedLaney, dmesg from the system the test ran on?16:23
Laneywant to see if apparmor is complaining maybe ...16:24
retoadedLaney, will see what I can gather16:24
cjwatsonjdstrand: Did you notice the click-apparmor autopkgtest regression?16:24
retoadedLaney, dmesg output sent via email16:32
Laneyretoaded: do you have any information about how I can reproduce this setup?16:43
cjwatsonmandel: ^- disregard that failure for now; I retried it already and will do a watch-only build if it works16:46
retoadedLaney, I can provide you the hardware specifics and package list16:47
jdstrandcjwatson: yes, I'll look at it. interesting I didn't see it when running that in a schroot16:51
jdstrandthose are the new tests I added'16:54
=== alan_g is now known as alan_g|EOW
davmor2o/ all have a nice week17:08
cjwatsonmandel: can you retest silo 11?  I think that "testing pass" is from the earlier run, so I reset it17:19
=== cjwatson changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: retoaded | CI Train Status: #119 promoted | CI Train Sheriff: trainguards | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
cjwatsonsil2100: (we should sort out a shift plan for next week)17:34
=== ev_ is now known as ev
=== renato is now known as Guest85133
=== ken_ is now known as kenvandine
=== Guest85133 is now known as renato___
pmcgowanrobru, is it ok that system settings is in two silos18:04
pmcgowankenvandine, ?18:04
kenvandineno... it shouldn't be able to be18:04
cjwatsonpmcgowan: see discussion about two hours ago between me, seb128, kgunn18:05
cjwatsonpmcgowan: 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 one18:06
pmcgowancjwatson, got it18:06
kenvandinei'm testing from silo 5 now18:07
kenvandinesilly me... applied an image update after updating settings from the silo ppa18:22
robrupmcgowan, it's "ok", but it requires coordination between the people owning those two silos.18:27
robrupmcgowan, kenvandine: so if you guys want to publish silo 5 soon, we just need to work with kgunn to rebuild system-settings in his silo18:28
kgunnyep...just ping me18:28
kenvandinerobru, almost ready18:28
kenvandineyup... all good18:29
robruoh heh, didn't read all the scrollback, just what was highlighted.18:29
kgunnfwiw, i noted on the call for test QtComp wiki that image125 is last-good-known image.....and if it breaks on latest use that18:29
kgunnso temp break is perfectly ok18:29
kenvandinepmcgowan, i think settings is ready to publish18:32
pmcgowansweet - whats in that18:32
pmcgowanthe 2g thingy, carrier fixes, qofono18:32
pmcgowanphone #18:33
kenvandinepmcgowan, yeah18:33
kenvandineand sim services enabled18:33
robrukenvandine, do you want me to publish silo 5? can you mark it testing:done in the spreadsheet?18:35
kenvandinerobru, done18:36
kenvandinecan i click publish too?18:36
robrukenvandine, thanks18:36
robrukenvandine, nah that's my job18:36
kenvandineit's yelling my name :)18:36
robrukenvandine, oh right, you're a core dev, so actually you can publish if you want to! ;-)18:36
* kenvandine clicks the button18:36
kenvandinei still think dput is easier than clicking the publish button :)18:38
robrukenvandine, well, dput rejects me, so clicking this button is all I got ;-)18:40
=== cprov changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cprov | CI Train Status: #119 promoted | CI Train Sheriff: trainguards | Known issues: Both queuebot and http://bit.ly/1mDv1FS know your silo status before the spreadsheet does.
jdstrandok, click-apparmor 0.2.9 will fix the autopkgtest issue19:31
jdstrandsorry about that19:31
jdstrand(it was a poorly written test)19:33
robrukgunn, you can rebuild system settings now if you're ready19:57
kgunnthanks man19:57
robrukgunn, you're welcome!19:57
alecutrainguards: hi, may I ask for a silo for this MP? https://code.launchpad.net/~alecu/unity-scope-click/merge-devel3/+merge/22653220:35
robrualecu, can you add that to the spreadsheet?20:51
alecurobru: sure20:51
robrualecu, just slip that in row 26 there: https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFVHQ3FuMDJGLUZCamJfSjYzbWh3Wnc#gid=020:51
alecurobru: done. I've filled the columns I knew what to put in20:55
robrualecu, great, just need your irc name in B26 and then when you're ready set I26 to "Yes"20:55
robrualecu, ok, you got silo 5, should show up at http://people.canonical.com/~platform/citrain_dashboard/#?q=alecu shortly20:56
alecurobru: thanks!20:56
robrualecu, you're welcome!20:56
robruthere it is ;-)20:57
alecuI've rode this train a few times, but it's the first time I get to buy the tickets20:58
robrualecu, heheh well I'm here to help if you need. that link I gave has the 'build' link to trigger the build20:58
alecurobru: so, if I need to update the branch with any fix, I would need to check FORCE_REBUILD?20:59
robrualecu, 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 set21:00
alecuyup, after re-reading I understood just that21:00
alecuthanks for the hand-holding.21:01
robrualecu, no worries, I'm in charge of making it run smoothly ;-)21:01
* robru wonders who will be the lucky winner of the 1,000th silo!21:19
alecurobru: I've added two more revs to my branch, but trying to rebuild I got the above ^22:09
robrualecu, ah ok, do the force_rebuild then22:10
robrualecu, ah, also ignore_step ;-)22:11
mhr3line 16?22:16
mhr3that already landed22:16
=== slangase` is now known as slangasek
slangasekSaviq: 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
Saviqslangasek, yeah, already restarted with the correct bits23:19
Saviqslangasek, forgot allow_unapproved23:19
slangasekmm, what does that mean :)23:19
Saviqslangasek, starting like a week ago builds will fail by default if MP is not top-approved23:20
Saviqthis checkbox lets you lift that restriction23:20
slangasekwhy do that, vs. top-approving23:20
Saviqslangasek, for test silos, things that are in-flight23:20
slangasekSaviq: ok; so this is a test silo only?23:21
slangasekSaviq: I'm asking to figure out the status of qtmir23:21
slangasekwhich I guess needs a NEW review at some point23:21
Saviqslangasek, yeah, it's not a purely-test silo any more23:22
Saviqslangasek, it's being dogfooded, and pending reviews will be converted to a real one soon23:22
Saviqslangasek, I was messing with it to include the fix for https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/134100723:23
slangasekok; so I'll wait for that before doing the NEW review23:23
ubot5Ubuntu bug 1341007 in ubuntu-system-settings (Ubuntu) "Welcome wizard only displays a background and bottom toolbar" [Undecided,In progress]23:23
Saviqslangasek, yeah, still a few days away23:23
slangasekpmcgowan: 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 you23:29
slangasekpmcgowan: is anyone still using these?  This is all quantal/raring stuff, way stale23:29
slangasekplars, 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/console23:53
slangasek(instead of, say, upgrading perl-base once for every source package in every silo)23:54
slangasekthe 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 :)23:57
