aleculol at Known Issues on the topic00:14
alecuah, I'm doing it wrong.00:22
* alecu understood a bit better how sync works now00:28
camakotrainguards (or anyone around), silo rtm-20 has landed, and now silo utopic-8 needs to be binary-synced... But how do I initiate this sync?01:19
barrycamako: instructions here: https://wiki.ubuntu.com/citrain/NewbieGuide01:19
camakobarry, thanks...01:20
camakoUrsinha ^^01:20
Ursinhacool :) solved then01:20
camakobarry, the doc says "now every time someone clicks 'Build' on the sync silo, it will try performing a binary copy of all packages in the source silo PPA", but it seems to be building from source :01:27
camakoo ok never mind, I think it's doing the binary copy..01:40
imgbot=== trainguards: IMAGE 275 building (started: 20141009 02:10) ===02:09
robrucamako: that log definitely shows a binary copy. Don't be fooled by "grabbing code" or whatever crap it says, if it was rebuilding sources there'd be pages and pages of build logs that just aren't there.02:56
* alecu is enjoying the NewbieGuide.03:09
alecuI was not aware that we landers are the ones supposed to click on "Merge and Clean"!03:09
robrualecu: yep. I do it a lot because we're often low, buy the original design was for you to watch the whole process and then click merge when you're ready03:10
alecugreat! I'll do it, no problem. I just didn't want to step on anybody's toes!03:11
rsalvetislangasek: do you know if the issue with image publishing was fixed already?03:27
rsalvetijust wondering if image 275 will show up at some point03:27
tvossgood morning07:35
jibelI'm on rtm 14.09 #4 and cannot install package updates. It's stuck on 'Downloading' and downloads never start. Is it a known issue?07:43
seb128jibel, yes07:44
seb128jibel, you can delete your u1 account and add it back07:44
jibelseb128, what is the bug #?07:44
seb128jibel, it's due to the sso tokens invalidation from this week07:44
seb128jibel, bug #137867807:45
ubot5bug 1378678 in ubuntu-system-settings (Ubuntu) "updates panel doesn't deal with invalid u1 tokens" [High,New] https://launchpad.net/bugs/137867807:45
jibelseb128, thanks07:45
seb128jibel, you can delete/add it back, the issue is easy to reproduce by going on th website and invalidating a token from there07:46
seb128e.g no need to keep the buggy state07:46
brendandsil2100, so holding calls seems to have broken at some point08:09
davmor2Morning all08:09
sil2100brendand: you testing on the latest image?08:09
brendandsil2100, yeah08:09
ogra_brendand, try entering a url in the browser ...08:11
ogra_is the keyboard always sideways for you too or is that only me08:11
Saviqtrainguards, hey, I can has silo for line 61 please08:12
ogra_Saviq, i see the slide issue mainly with the "my music" scope, and the dash is very crashy08:14
Saviqogra_, you got a lot of music on your phone do you?08:14
ogra_Sa34G on SD card08:14
ogra_Saviq, 34 on SD card08:14
brendandogra_, i think that sometimes just happens08:14
Saviqsounds like  alot08:15
* Saviq needs a large microSD card...08:15
ogra_brendand, it always happens for me ... there is no way for me to open a url currently08:15
ogra_(in portrait ... indeed it works in landscape .. but the kbd is stuck)08:15
ogra_it comes up fine everywhere else, seems to be only the url bar of the browser08:16
sil2100Saviq: sooo, I see someone allocated unity8 in silo 13 already08:16
sil2100Saviq: it seems to be ted!08:16
ogra_(even input fields in pages work )08:16
sil2100Saviq: you want an ignore-conflicts here?08:16
Saviqsil2100, "Integration silo right now, should not block other silos or conflict"08:16
ogra_sil2100, image builds seems to still be broken08:17
sil2100ogra_: oh, slangasek mentioned it was fixed...08:17
ogra_well, he managed to publish the last two that were stuck08:17
ogra_but there are no new images08:17
sil2100Ah right, noticed that too, since I noticed we're still on 274 in utopic08:18
ogra_(neither utopic, nor rtm)08:18
sil2100But I actually thought it was because of my commitlog scripts b0rking08:18
sil2100Good to know08:19
ogra_93 is the last rtm one08:19
Mirvnothing new in the morning :(08:19
sil2100ogra_: stgraber still on holidays?08:19
davmor2brendand: hmm there are 3 I just moved the other with the first 2 are those the ones you want me to take08:20
ogra_i see we have a fresh rootfs though08:20
brendanddavmor2, no never mind about 15, that just came up08:20
ogra_running import-images manually for system-image at least spills aa new error now08:21
ogra_this is what i get from import-images08:23
ogra_the code change slangasek did is tiny ... i suspect there are other bits that need to be ported to python3 https://code.launchpad.net/~vorlon/ubuntu-system-image/server-python308:26
ogra_"heeey macarena !"08:29
Saviqogra_, btw, is your MTP locked on connection if your lockscreen is protected?08:34
ogra_Saviq, havewnt tested that in a while, but that is how it should be08:34
* Saviq is sometimes getting access to the files without unlocking08:34
ogra_it should only block on connect ... if you have it locked afterwards it shouldnt care08:35
Saviqogra_, btw, can you access the SD card over MTP?08:41
Saviqogra_, and have you had luck with any music management apps? banshee can't transfer music onto the phone for me08:42
ogra_oh, i never tried that08:42
ogra_i only copy via nautilus (if at all, my USB 3.0 SD card reader is way faster)08:42
Saviqogra_, could you please record a video of the slowness you're seeing in the dash?08:43
ogra_Saviq, will try, i have some more pressing issues (we dont have images, builds dont work)08:43
Saviqogra_, yeah, sure08:43
ogra_Saviq, and the constantly crashing dash is also worse than the slowness08:44
Saviqogra_, can you check if that's not OOM killing the dash?08:44
ogra_Saviq, i'd expect it does, but yeah, i only noticed it last night and havent had time to check logs yet08:46
Saviqogra_, so yeah, this is all about you having too much music on your device :P08:46
Saviqogra_, when you have time, please file a bug with any details you think it's worth08:46
ogra_Saviq, we are just going through the (very few) smoke test results from last night and see scoperunner crashing a lot there too08:46
ogra_http://dashboard.ubuntu-ci:8080/smokeng/utopic/touch_stable/krillin/93:20141008.2:20141008-8ea26ef/544/unity8/ for example08:47
ogra_(scroll down)08:47
Saviqogra_, and this would be a bug against unity8 and unity-scope-mediascanner, as it should limit the number of results08:47
brendandWellark, your silo will get looked at today - guess you already know about the Trello board?08:48
Saviqogra_, there was a release of scopes api yesterday08:48
ogra_Saviq, there also was unity-plugin-scopes yesterday morning08:49
ogra_(landed in image 90)08:49
Saviqogra_, yeah, wouldn't cause scoperunner to crash, though08:49
Saviqor at least should not be able to08:49
Saviqif plugin-scopes crashed, unity8 would, not scoperunner08:49
ogra_what i see is a black screen saying "Scopes" when it restarts ...08:49
ogra_is that scope runner ?08:50
brendandhmm, so there might not be a general problem with holding calls08:50
brendandmaybe it's this sim card08:50
Saviqogra_, no, that's dash restarting08:50
Saviqogra_, but what *you* see is different from what causes the smoketests problems08:50
Wellarkbrendand: what is Trello board?08:54
ogra_Wellark, read the spreadsheet ;)08:54
ogra_link is there at the top somewhere08:54
brendandWellark, http://bit.ly/1qMAKYd08:55
Wellarkwhat spreadsheet?08:55
WellarkI have so many08:55
ogra_Wellark, the one you put your landings on08:55
Wellarkbrendand: looks cool08:57
Wellarkbrendand: where is the RSS feed for the thing? :)08:58
brendandWellark, click on the card > subscribe08:59
brendandWellark, it will be by email08:59
popeyogra_: Yo! I hear you like music! http://people.canonical.com/~alan/music_remix/readme.txt - fancy testing out the new music app remix next time you listen to some. Would be very helpful to us.09:22
ogra_popey, oooh, cool !09:47
ogra_running import-images under pdb seems to just work :/10:00
ogra_(we should have 94 soon, but i still cant find the error)10:01
cjwatsonogra_: slangasek fixed it last night10:01
ogra_cjwatson, see my mail to ubuntu-phone ...10:01
ogra_cjwatson, it worked for images that were alkready local ... but it doesnt pull any new ones anymore10:02
sil2100Yay, cjwatson to the rescue ;)10:02
cjwatsonI'm busy :P10:02
ogra_and now i know why it works under pdb10:02
cjwatsonpdb3 would be better now that that script is running under python310:02
ogra_cjwatson, exactly ...10:02
ogra_it works fine like that: python -m pdb /srv/system-image.ubuntu.com/bin/import-images10:03
ogra_with which i'm obviously pushin it back to py210:03
ogra_only strikes me now :(10:03
ogra_but at least we'll get tonights image10:03
ogra_(if it actually finishes)10:04
cjwatsonwell it's possible that it will work with python 2 again now that it's processed the non-ASCII removed files10:05
cjwatsonhttps://docs.python.org/3/whatsnew/3.0.html#ordering-comparisons explains this failure10:06
cjwatsonI've reverted import-images to python210:06
cjwatsonso only to the rescue because I can do it with one character ;-)10:08
ogra_i suspect there is likely even more porting needed before we can make that switch10:09
cjwatsonprobably not too much10:09
cjwatsonI expect that slangasek ran the test suite; this is probably a corner case not covered by it10:09
cjwatsonspecifically the case where 'base' not in image, around the area at the traceback in your paste10:10
cjwatsonand in fact there must be multiple images some which contain 'base' and some which don't10:10
ogra_yeah, there are10:10
cjwatsonI mean that that's a necessary condition for the failure10:11
psivaaMirv: i ran music_app tests to reproduce the qmlscene crash and yet the mediascanner log is not present: http://pastebin.ubuntu.com/8526076/10:12
cjwatsonI've filed https://bugs.launchpad.net/ubuntu-system-image/+bug/1379274 for the above10:19
ubot5Ubuntu bug 1379274 in Ubuntu system image "import-images fails under Python 3 when there are multiple images and at least one lacks a base" [Undecided,New]10:19
Mirvpsivaa: hmm :( can you ping Satoris and ask for ideas?10:21
Mirvhe tends to not be on public irc however unfortunately10:21
imgbot=== trainguards: IMAGE 275 DONE (finished: 20141009 10:25) ===10:24
imgbot=== changelog: http://people.canonical.com/~ogra/touch-image-stats/275.changes ===10:24
ogra_ha !10:25
davmor2ogra_: you fixored it10:25
ogra_davmor2, nope10:25
ogra_i just ran it with the wrong debugger :)10:25
brendandogra_, isn't it better just to do 'import pdb; pdb.set_trace()'?10:26
ogra_brendand, that means i need to do code changes10:26
brendandogra_, ah you're touching the live system?10:27
ogra_brendand, right ... i was trying to get proper debug output from the broken live system10:27
ogra_but clever as i am i didnt run the py3 version :P10:27
sil2100ogra_: so, you think it will work from now on?10:29
sil2100Since cjwatson re-enabled python2 again10:29
ogra_sil2100, with cjwatson's "fix" it will work until any file with non-ascii name gets removed from the image10:30
ogra_then we'd run into the same issue as yesterday10:30
cjwatsonwhich is why I filed a bug10:30
ogra_sil2100, FYI http://people.canonical.com/~ogra/touch-image-stats/rtm/94.changes10:34
ogra_(since the bot got cunfused by starting and failing images)10:35
sil2100ogra_: thanks!10:35
ogra_Saviq, so with 94 the scopes seem to behave a bit better ... i only see the delay between swipe and action when i *leave* the music scope, not in the other scopes anymore (before it was all scopes that seemsd to have a delay between gesture and actual action)10:38
ogra_my browser is still broken though :/10:40
Saviqogra_, glad to hear, we still need to have a look at improving this of course10:41
ogra_Saviq, yeah, but it isnt as bad anymore10:41
ogra_i cant really belive i'm the only one with the keyboard being stuck in landscape when trying to enter something in the browser url bar10:42
Saviqogra_, FWIW there wasn't a unity8 release in that image was there?10:43
ogra_Saviq, nope, click scope though10:43
ogra_and UAL10:43
Saviqogra_, hmm, let us know if the slowness comes back, no scope alone should've caused that...10:44
ogra_might be that due to the crashyness apport ran in bg ... which would have made it additionally slow10:44
Saviqwell, that's assuming it was actually crashing?10:45
ogra_well, it was restarting :)10:46
ogra_(black screen with "scopes" on it and then an empty apps scope that slowly filled over time)10:46
Mirvsil2100: have you ever thought about raising the amount of utopic silo to 35...11:14
sil2100Mirv: ...;p11:14
Mirvbzoltan: is the 1.10. uitk landing going to land in utopic? it's built, not tested, and you have the next landing for rtm already.11:15
Mirv^  no they are not yet...11:17
Mirvsil2100: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-017-2-publish/9/console11:17
MirvI'm trying to publish it, yes, but to my understanding it did not11:18
sil2100Mirv: I ran it already :)11:18
Mirvsil2100: ah! :)11:18
sil2100Mirv: that's why it errors out!11:18
Mirvsil2100: it did not error out, it succeeded with an error :)11:18
sil2100I think it would be anyway better if we fix the messaging in this case ;)11:19
sil2100Since CI Train right now doesn't really handle pressing publish twice, it should basically say: "already publishing" or something11:19
Mirvso many issues on the spreadsheet again11:20
MirvI mean, lines that have something amiss11:21
Mirvtvoss: is "Land Network Manager WiFi timestamp/scan results fix from tvoss to rtm" line irrelevant nowadays, for rtm? I've asked on 20140925 about the line and no answer, but just double checking.11:22
tvossMirv, I will take a look in a few11:23
Mirvtvoss: the latest network-manager upload in rtm is from Sep 30 https://lists.canonical.com/archives/rtm-14.09-changes/2014-September/000549.html11:23
Mirvtvoss: ok, thanks. line 15. I'd just like to remove the line if it's not relevant anymore11:23
tvossMirv, sure, let me double check after I kicked a test11:24
ogra_Saviq, tvoss, so my unity8-dash is crashing simply because it isnt excuded from app lifecycle mgmt at all http://paste.ubuntu.com/8526308/ ... (see the oom_score_adj value of 802 here)11:26
Saviqogra_, s/crashing/being killed/11:27
ogra_the user experience is the same :)11:27
tvossogra_, file a bug against unity811:27
ogra_tvoss, will do11:27
Saviqogra_, and well, I'm not sure that's totally wrong, if your foreground app uses all the memory, shouldn't the dash be killed?11:28
Saviqogra_, granted, it should only resume after you focus it again11:28
ogra_Saviq, everything but the dash imho11:28
ogra_i have like 20 apps open, not all of them have been killed if the dash dies11:28
ogra_it should definitely always stay at a lower value than normal apps11:29
Saviqyeah that I agree with, between normal apps and foreground app11:29
ogra_so that ... *if* killed at all, it should be the last thing11:29
Saviqogra_, and yeah, we need to reduce mem usage in a case like yours11:29
Saviqogra_, unity8 and qtmir please11:29
Saviqsil2100, hmm https://ci-train.ubuntu.com/job/ubuntu-landing-019-0-reconfigure/15/console says "Removing unity-notifications from silo.", but then https://ci-train.ubuntu.com/job/ubuntu-landing-019-1-build/69/console :|11:31
Mirvted: landing-017 for your utopic misc fixes. I've force Merge & Clean for indicator-sound (001) so that the trunk is up-to-date, but please follow manually if release team has something against it or will allow it to pass before trying to publish this new silo.11:33
Saviqtrainguards, can you please drop unity-notifications from utopic silo 19, reconfiguration doesn't seem to have done it, even though it said it did11:35
MirvSaviq: grudgingly doing so. grumpiness related to CI train.11:35
ogra_Saviq, tvoss bug 137929611:36
ubot5bug 1379296 in unity8 (Ubuntu) "unity8-dash should be excluded from app lifecycle management" [Undecided,New] https://launchpad.net/bugs/137929611:36
Mirvsil2100: better to ask though - I guess we don't have any "prepare" link anywhere, so for real reconfigs one needs to fill in all the fields in prepare-silo job manually? or are some of them optional? nowadays one has fields for lander, MP:s, additional source packages... not just the request id etc11:36
oSoMoNtrainguards: can you please publish RTM silo 17 ?11:37
MirvoSoMoN: already done, sorry, I'll m&c it manually in a minute11:37
Mirvmy mistake11:37
Mirvdbarth: your "webapps fixes" line lacks target distro11:38
Mirvtvoss: same for your "Fix #1373281 & #1367244"11:38
oSoMoNMirv, awesome, thanks11:39
SaviqMirv, hmm still there https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-019/+packages ?11:40
SaviqMirv, or did you not remove it yet?11:40
MirvSaviq: not yet, I was first waiting for sil2100 to answer my question, then handling other train stuff and now doing it the manual route11:41
SaviqMirv, ok sorry for pushing :)11:42
MirvSaviq: now done :)11:43
SaviqMirv, thank youse11:43
sil2100Mirv: what I do usually is go to the spreadsheet and do the 'Assign silo' button again11:45
sil2100Mirv: it worked so far11:45
sil2100Mirv: so you go to the row of interest, click as if you assign a silo but just do a reconfigure instead11:46
Mirvsil2100: there's no option to reconfig there11:47
Mirvsil2100: oh, correction11:47
Mirvit's a "reconfigure" dialog11:47
Mirvand then it calls prepare-silo!11:47
Mirvoh joy!11:47
Mirvsil2100: thanks!!11:48
MirvoSoMoN: considering webbrowser-app landed from the 017 as a sync from utopic, is line 36 and its assigned 019 silo a thing of the past?11:48
sil2100Yeah :)11:49
* sil2100 goes prepare lunch11:49
MirvoSoMoN: and to answer to myself, I believe it's still needed as much has happened since 1006 release :) https://code.launchpad.net/~phablet-team/webbrowser-app/trunk11:50
oSoMoNMirv, yes indeed, I think it’s still needed11:50
* Mirv is momentarily satisfied with the spreadsheet11:54
WellarkMirv: sync silo for line 78 please :)12:02
MirvWellark: done, but can't allocate rtm silo yet since the previous landing is still ongoing12:07
Mirvor well, that's a sync silo too so I guess I could (trunk already updated)12:07
WellarkMirv: <312:11
WellarkMirv: any idea what this is: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-006-1-build/27/console ?12:18
WellarkMirv: and why is this failing: https://ci-train.ubuntu.com/job/ubuntu-landing-020-1-build/61/console12:19
sil2100Wellark: the ubuntu-rtm is a known thing - did you re-sync just now for the second time?12:20
Wellarksil2100: haven't touched it12:20
Wellarkjust tried to rebuild12:20
Wellarkand the utopic silo fails to build arm64 package because:12:21
Wellarkdpkg-buildpackage: host architecture arm6412:21
Wellarkdpkg-checkbuilddeps: Unmet build dependencies: gdb:any12:21
Wellarkdpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting12:21
Wellarkdpkg-buildpackage: warning: (Use -d flag to override.)12:21
sil2100Ah, ok, so don't worry with the ubuntu-rtm error... once the binary copy gets published this will go away12:21
sil2100Not sure about the ubuntu one, didn't look yet12:21
sil2100The ubuntu one looks like a toolchain issue12:23
Wellarkor somebody deteled gdb12:23
Laneyshould be fixed now12:24
Laneyah, still in proposed12:24
Laneyshould be fixed *soon* :)12:25
sil2100The PPA builds with proposed so we should be good ;)12:25
Wellarksil2100: can I trigger a rebuild on arm64 on the ppa straight or must I go through silo dashboard and rebuild on all architectures?12:29
sil2100Wellark: we need to do it from the PPA12:33
sil2100Wellark: we have the power, so let me do that12:33
LaneyIt's not finished building on arm64 yet12:33
ogra_see #ubuntu-touch12:33
LaneyYou need rmadison -s utopic-proposed -a arm64 gdb to show you ubuntu412:33
sil2100Ah! Ok, I thought that it's build in proposed already12:35
sil2100Wellark: silo 20 will still fail, but I'll re-build it again once it's finished ^12:36
cjwatsonyeah, requires Adam to manually kill test processes to let the build complete :-/12:37
cjwatsonwaiting for him to show up12:37
cjwatsonWellark: going through the dashboard will just waste a load of build time on all architectures and not fix this anyway, so don't do that12:38
Wellarkcjwatson: ack. that's why I asked :)12:46
sergiusenssil2100: I need to reconfig ubuntu-rtm&q=landing-008 (I know it has conflicts with other silos, so will rebuild/reconfigure once it's all good and lined up and lockable)12:56
sil2100sergiusens: ok, doing12:59
sergiusenssil2100: iirc, the only conflict is the webbrowser12:59
sil2100It's reconfiguring, let's see how it goes13:01
sil2100Yeah, webbrowser is the only one, but I ignored conflicts13:01
alecutrainguards, ping about ubuntu/landing-03013:06
=== barry changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards, barry | Need help with something else? Ping vanguard: cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: robru is on vacation
sil2100alecu: oh! Looking13:08
alecutrainguards: I jumbled a bit with ubuntu/landing-030, and got that error message, but I tested packages in the ppa and they seem to be the right version, so I think the sync worked after all13:08
sil2100alecu: yeah, it's a specific citrain issue... usually when you see this just wait some time and re-run, it'll fix itself13:09
alecusil2100: also, I followed the test plan, and it passed ok, so I wonder what needs to be done to land it.13:09
sil2100Let me re-run13:09
sil2100alecu: ok, the packages are correct, I just need to do a watch_only build now13:09
sil2100So, it's on my radar, but due to the lack of time it's actually pushed back...13:09
alecusil2100: no hurries, thanks!13:10
sil2100psivaa: we have full results from smoketesting, right?13:41
loolthanks for putting https://wiki.ubuntu.com/citrain/LandingProcess together13:44
loolit would be nice to link it from http://people.canonical.com/~platform/citrain_dashboard/13:44
loolso that I can find it again  :-)13:45
sil2100lool: yw! I'll try adding that later today :) There are still things that I need to put inside there though13:47
sil2100brendand was the person doing the QA sign-off part13:47
camakosil2100, is everything ok with the rtm silo 20 migration?13:48
ogra_sil2100, 93 looks pretty complete to me13:48
ogra_hmm, i thought filemanager was fixed13:49
ogra_and calculator lately has issues it didnt have in the last images13:49
ogra_(in rtm)13:49
ogra_music and gallery too :(13:50
kgunncjwatson: rtm silo20 was released by qa y'day ~ 5pm my time...~16hrs ago....but dash board showing it's still in migration13:50
ogra_looks liek something migrated that broke them (i know we had this in utopic but never in rtm)13:50
kgunnany thots ?13:50
sil2100camako: let me take a look13:58
kgunnsil2100: thanks...it's been like 16hrs13:59
camakosil2100, also during sync of rtm silo 20 to utopic silo 8, unsupported architectures make the build fail, but packages for supported apps are in the ppa, so it's ok to ignore this error, I think? Just thought I'd report it as a good samaritan..14:01
thostr_davmor2: just wanted to verify that rtm silo 18 is indeed next on your sign-off list?14:01
camakosil2100, s/supported apps/supported arches14:02
cjwatsonkgunn: seems to make ubuntu-touch uninstallable14:02
cjwatson(just the bit at the end)14:02
davmor2thostr_: yeap whatever is at the top is always next14:02
sil2100cjwatson: but it actually tries installing qtmir and qtmir-gles at once, while qtmir-gles I guess is not touch specific, right?14:03
cjwatsonsil2100: no that's not quite what that means14:03
cjwatsonit's effectively test-upgrading the archive and checking for resulting new uninstallable packages14:03
cjwatsonit does not mean it's trying to coinstall all binaries from all the listed sources14:03
thostr_davmor2: thanks14:04
sil2100Ah, ok14:04
cjwatsonnot yet quite sure what the problem is though14:04
cjwatsonprobably NBS somewhere14:05
kgunnNBS ?14:05
davmor2thostr_: when that will be is another matter altogether but it will be next ;)14:05
camakocjwatson, there was a similar problem during QA testing... where ci-train-upgrade didn't work because it pulled in only mesa libs14:06
cjwatsonnot built from source14:06
cjwatsonubuntu-touch depends: libmirclientplatform-android, libmirplatformgraphics-android14:06
cjwatsonneither of which is in the new version of mir14:06
camakocjwatson, yes that...14:06
cjwatsonhas this change also landed in utopic?14:07
camakocjwatson, but it worked when the relevant packages were installed14:07
camakocjwatson, no14:07
kgunnlanding in reverse14:07
cjwatsoncamako: yes because nothing forces the old binaries out, but proposed-migration checks for this14:07
cjwatsonit would be a lot easier to get this into utopic and then we can update ubuntu-touch-meta in the usual way14:07
kgunnso i wonder, is landing in reverse just not a good method for core components ?14:08
camakocjwatson, it's in silo 8 for utopic..14:08
cjwatsonkgunn: depends on the changes14:08
cjwatsonif we have to do it this way round then I'm going to have to temporarily branch ubuntu-touch-meta in rtm14:08
camakocjwatson, so can we hold this off, and finish testing the sync silo 8 on utopic first, and then rtm? testing on silo 8 is abt done.14:09
cjwatsonkgunn: major package restructurings are going to be a little problematic that way round14:10
camakocjwatson, rtm testing is done already (using the apt-get install method, not train-upgrade).14:10
cjwatsonok I don't need to know :)14:10
cjwatsonI think you have what you need now?14:10
camakook I'm not saying :-)14:10
camakocjwatson, yep14:11
cjwatsonsomebody will just have to bump the ubuntu-touch seeds once this is landed in utopic14:11
cjwatsonand upload ubuntu-touch-meta14:11
camakosil2100 ^^14:11
cjwatsonthen we binary-copy ubuntu-touch-meta to rtm14:11
cjwatson(once it's built)14:11
sil2100camako, cjwatson: ok, thanks! So, let's get it tested for utopic and ready to release14:13
sil2100Then we can ask for instance ogra_ to update the seed14:13
camakosil2100, sounds good14:14
ogra_jdstrand, i see a lot of apparmor denials in image 93 ... for gallery and calculator tests14:14
ogra_jdstrand, http://dev-jenkins.ubuntu-ci:8080/job/utopic-touch_stable-krillin-smoke-daily/313/artifact/clientlogs/ubuntu_calculator_app/syslog/*view*/ and http://dev-jenkins.ubuntu-ci:8080/job/utopic-touch_stable-krillin-smoke-daily/311/artifact/clientlogs/gallery_app/syslog/*view*/14:15
ogra_and music suddenly cant read its gsettings schemas anymore (it could in 88 )14:16
ogra_ted, did you test your XDG changes with rtm under pahblet-test-run ?14:17
ogra_88+ has a lot of new errors we never had before ... partially gsettings related14:17
tedogra_, No, I didn't test with phablet-test-run, I used adb shell.14:18
ogra_you should have used phablet-test-run14:18
tedogra_, Is that before or after the xdg changes landed?14:18
ogra_which is what we use in testing everywhere14:18
* alecu merges and cleans14:19
ogra_ted, http://people.canonical.com/~ogra/touch-image-stats/rtm/89.changes ... 88 was all fine ...14:19
ogra_since 89 we have issues it seems14:19
psivaasil2100: ugh, with rtm 94 both devices had flashing issues, i'm running it again14:19
ogra_ted, though i dont think it is the XDG change but rather UAL (which landed in the same image)14:20
tedogra_, Yes, I think UAL caused it. But that image doesn't have the XDG fix.14:21
tedogra_, That's in the next touch-session update14:21
tedogra_, https://code.launchpad.net/~phablet-team/ubuntu-touch-session/trunk14:21
tedogra_, Not until 100714:21
ogra_ted, there is no "next" one in rtm14:21
ogra_ted, note that phablet-test-run (or any other non interactive tool) will not treat adb shell as login shell14:21
bzoltan1davmor2:  I see you have started to validate the uitk. Is there anything I can help you?14:22
tedogra_, Wait, I'm confused. So which revision of ubuntu-touch-session do you think rtm89 has?14:22
ogra_your "fix" will only affect any interactiver shells anyway14:22
ogra_which we use nowhere14:23
ogra_0.108+14.10.20141006.1-0ubuntu1 ...14:23
ogra_oh, indeed, that doesnt have yur hack14:23
sergiusenssil2100: can I get a new reconfig for rtm silo 8?14:24
tedThe hack fixed the utopic results.14:24
sil2100sergiusens: ACK14:24
davmor2bzoltan: no thanks bud, I'm marching through it14:24
ogra_ted, http://ci.ubuntu.com/smokeng/utopic/touch/mako/274:20141008.1:20140929.1/10857/14:24
ogra_ted, doesnt look like it did (would also be surpising ... since as i said, you only change interactive shell behavior)14:24
tedogra_, http://ci.ubuntu.com/smokeng/utopic/touch/mako/273:20141008:20140929.1/10844/ubuntu_clock_app/14:25
ogra_ted, see gallery and calculator14:25
tedogra_, Clock app went from 50% to 100%14:25
sil2100sergiusens: ok, indicator-transfer is already allocated by silo 21 as well - I reconfigured, but please make sure it's coordinated14:26
ogra_ted, hmm, so that was a clock only fix ?14:26
tedogra_, I don't think so, but looking at the 274 gallery results14:27
tedogra_, Where do you see the gsettings failure there?14:27
ogra_yeah, gallery is probably a bad example as it has apparmor issues14:27
ogra_calculator has the gsettings messages in its log14:27
ogra_gallery http://dev-jenkins.ubuntu-ci:8080/job/utopic-touch_stable-krillin-smoke-daily/311/artifact/clientlogs/gallery_app/application-click-com.ubuntu.gallery_gallery_2.9.1.1084.log/*view*/ has only a few gsettings messages14:29
tedogra_, Those are dconf not being able to read the file, that's not the same.14:29
tedogra_, The clock one was segfaulting14:29
ogra_(but ignore that we should get apparmor fixed there first)14:29
tedI'm pretty sure we don't want apps reading that file.14:29
ogra_ted, i'm just worried because we didnt have any issues with either app before image 8914:29
ogra_(in RTM that is)14:29
jdstrandogra_: the fakeenv policy needs to be updated for the calculator14:30
ogra_jdstrand, ah14:30
ogra_jdstrand, what about gallery ?14:30
jdstrandballoons: ^14:30
jdstrandballoons: representative denial: apparmor="DENIED" operation="mkdir" profile="com.ubuntu.calculator_calculator_1.3.329" name="/home/phablet/autopilot/fakeenv/tmpqn1fqd0e/.cache/QML/" pid=NNN comm="qmlscene" requested_mask="c" denied_mask="c" fsuid=32011 ouid=3201114:31
ogra_i didnt notice the path14:31
ogra_thats ricmm land :)14:31
tedogra_, I agree, I think the UAL landing broke them. And I think the ubuntu-touch-session fixes them. Which is why I was so hot to get it in :-)14:31
jdstrandogra_: leaf-net is 1378805. networkmanager is 137640814:32
jdstrandogra_: /usr/bbc/ is wrong :)14:32
balloonsjdstrand, hmm.. it's inside fakeenv, why the sudden denial?14:32
jdstrandballoons: I'd have to look at the policy again, but .cache/QML/ is a new path for the precompiled qml work from ricmm14:33
jdstrandballoons: can you point me at the policy and I can give you a rule to add?14:33
ogra_ted, so land it already 11!!14:33
ogra_(i still doubt .profile helps with non.interactive shells though, but happy to be proven wrong)14:34
jdstrandogra_: yelp is 137641614:34
jdstrandogra_: /home/phablet/.local/share/applications/ is 137881714:35
ogra_you know your bug list very well it seems :)14:35
jdstrandogra_: /usr/share/applications/ is also 137881714:35
jdstrandI am getting daily pings14:36
ogra_heh. sorry14:36
jdstrandno worries14:36
jdstrandthe QML one is legit-- needs to be fixed14:36
ogra_just an oversight14:36
jdstrandwell, they all need to be fixed, but the QML one is new :)14:36
balloonsjdstrand, ahh.. Well, the policy stuff is all in aa-click. Perhaps it's solvable by us creating the dir and not changing the policy14:36
jdstrandit isn't in click-apparmor, I remember it is in autopilot14:37
jdstrandlet me look at it14:37
balloonsyep, you are correct. We do create quite a nest of directories during the test setup as well14:38
ogra_jdstrand, now the million dollar question ... if apparmor doesnt allow my app to write to that precompiled QML dir ... why is it actually working in real life ?14:38
jdstrandballoons: ok, so, yes, you need to create the directory, but /usr/share/autopilot-touch/apparmor/click.rules needs this rule:14:38
ogra_i would expect AA also blocks in real usage too ?14:39
jdstrandno, I fixed that already14:39
ogra_if we dont have the dir14:39
ogra_ah !14:39
jdstrandoh, yes14:39
jdstrandapps can't create that dir14:39
jdstrandbut, they can create their application-specific dir under it14:39
jdstrandsomeone should make sure that dir exists14:40
jdstrandotherwise we will have reports where it sometimes works and sometimes doesn't14:40
ogra_well, something creates it14:41
ogra_i know i didnt create it manually14:41
jdstrand(eg, launch messaging app first (unconfined), all is ok. launch weather app first (confined), it won't work right)14:41
ogra_ricmm, what creates the ~/.cache/QML dir ?14:41
jdstrandI'm making some assumptions here that it isn't happening14:41
jdstrandhappening outside of the app that is14:42
* ogra_ thought thats UAL14:42
jdstrandif UAL is doing it, then shouldn't be an issue14:42
jdstrandjust so long as the app isn't doing it14:42
jdstrandballoons: so, the dir to create is @{HOME}/autopilot/fakeenv/*/.cache/QML/Apps/14:44
jdstrandballoons: and the rule to add to autopilot rules is:14:44
jdstrandowner @{HOME}/autopilot/fakeenv/*/.cache/QML/Apps/@{APP_PKGNAME}_@{APP_APPNAME}_@{APP_VERSION}/** mrwkl,14:44
jdstrandballoons: once both of those is done, the calculator should start working again14:45
john-mcaleelyis it possible to know where ubuntu/landing-003 is in the queue for signoff/landing in image?14:48
john-mcaleelyI need to do a device tarball update after it...14:49
john-mcaleelycihelp ^14:49
sil2100john-mcaleely: ubuntu landing 003?14:50
sil2100john-mcaleely: it didn't get tested by the lander yet14:50
Ursinhajohn-mcaleely: that is a question for trainguards, but I'd guess QA signoff dashboard14:50
=== Ursinha changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards, barry | Need help with something else? Ping vanguard: Ursinha | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: robru is on vacation
john-mcaleelysil2100, aha, ok14:51
john-mcaleelyUrsinha, thanks! will cruise those links14:51
barryjohn-mcaleely: the dashboard is your friend: http://people.canonical.com/~platform/citrain_dashboard//#?distro=ubuntu&q=14:52
Ursinhajohn-mcaleely: no problem :)14:52
john-mcaleelybarry, thank you. looking now.14:52
=== oSoMoN_ is now known as oSoMoN
balloonsjdstrand, thank you. I'll make those tweaks15:02
MirvSaviq: not approved https://code.launchpad.net/~aacid/unity8/noDashContentScale/+merge/23762615:10
SaviqMirv, oups, sorries15:10
SaviqMirv, done15:12
dbarthhey, i have a dependency problem in a silo15:12
dbarth ubuntu-system-settings-online-accounts : Depends: libmirclient8 (>= 0.8.0+14.10.20141005) but 0.7.3+14.10.20140918.1-0ubuntu1 is to be installed15:12
dbarthit's an rtm silo15:13
dbarthdoes that sound normal?15:13
dbarththe same silo build yesterday was installing ok15:13
Saviqdbarth, there's an issue with Mir landing from rtm silo 2015:13
Saviqdbarth, i.e. things are stuck in propose15:13
dbarthSaviq: ah, but so i can take silo 20 on top, and that should work15:14
dbarthSaviq: thanks; i will try15:14
Saviqdbarth, yeah15:15
jdstrandogra_: oh, music-app and gsettings. apps are not allowed to use gsettings (they never have). I added some explicit denies for dconf to the ubuntu-sdk template, but that doesn't change anything: a) they were denied before and b) music-app uses the unconfined template (which can use gsettings, but shouldn't if it is ever going to be confined)15:19
brendandoSoMoN, your webbrowser-app silo is 4th in our queue. it should get tested later today or early tomorrow. see the trello board for status: https://trello.com/b/AE3swczu15:19
ogra_jdstrand, hmm15:20
jdstrandie, it shouldn't have anything to do with apparmor15:20
oSoMoNbrendand, thanks for the update, I’ll be watching the trello board15:20
=== gatox is now known as gatox_lunch
Mirvyeah EOD is overrated15:45
bfillerMirv: just had a problem with a silo landing on rtm, and then ubuntu but it never merged the changes to trunk15:47
bfillerMirv: any ideas why?15:47
bfillerwas silo 21 on ubuntu and was silo 3 earlier today on rtm15:47
bfillertelepathy-ofono never got merged back to trunk15:47
bfillerMirv, sil2100: ouch, none of the MR's on those silos got merged back15:48
jfunkpsivaa: hey :) I think asac was asking you to help jibel & rhuddie with test plans on the promoted images, not with silo testing, asac correct me if I am wrong15:49
jfunkbrendand: ^15:49
Mirvbfiller: sil2100: I'm not sure what happened here https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-003-3-merge-clean/25/console15:50
bfillersil2100, Mirv: line 15 and 16 on the sheet15:50
ogra_Mirv, whats that EOD thing ? "exhaust or die" ?15:50
Mirvbfiller: sil2100: oh, that one only was content-hub silo, are you sure the rtm was 003?15:51
bfillerMirv: trying to remember the silo..15:51
Mirvbfiller: sil2100: ok, this was the problematic m&c https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-003-3-merge-clean/24/console15:51
Mirvogra_: something like that15:51
bfillerMirv: hmn, how can we fix? we did a rebuild after rsalveti landed another version of telepathy-ofono should that should have been ok15:53
brendandogra_, EOD is what you call 'going to sleep'15:53
Mirvbfiller: by merging manually form https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-003-2-publish/25/console15:53
rsalvetibfiller: it seems for some reason we got a version clash on tp-ofono15:53
Mirvbfiller: telephony-service should be fixed15:53
ogra_brendand, oh, you mean FhK !15:54
ogra_(Forehead hits Keyboard)15:54
rsalvetibfiller: Mirv: should I just merge tp-ofono by hand?15:54
rsalvetilet me get some food first15:55
Mirvrsalveti: bfiller telepathy-ofono also now merged manually, but please check the result15:55
sil2100I wonder why CI Train was unable to auto-merge that15:55
brendandogra_, mind your language15:56
Mirvsil2100: could it be changed it wouldn't be "success" m&c if there's an error?15:57
sil2100I guess this might be some problem caused by Robert's refactoring, since I'm pretty sure in the past it wasn't succeeding15:57
Mirvsil2100: I worry if we have missed other similar cases15:58
Mirvbfiller: messaging-app, history-service and dialer-app also now pushed15:59
sil2100Mirv: thanks for doing it manually!15:59
bfillerMirv: thank you!15:59
=== pstolowski is now known as bbl
=== bbl is now known as pstolowski|bbl
bfillerMirv: is ok that the rev that got merged shows only 1 merged branch even though there were multiple branches that were merged? the diff looks correct.. see https://code.launchpad.net/~phablet-team/messaging-app/trunk latest rev16:01
Mirvbfiller: it's the ci train's combined branch, which is always pushed when publishing: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-003-2-publish/25/console - so it _should_ be ok16:02
* sil2100 will look to fix the 'succeeding' problem16:02
Mirvbfiller: that's funny thought that it marks it like that while in reality I merged that ~ps-jenkins branch16:02
Mirvbut it's probably a LP limitation when making such a manual merge16:03
=== Ursinha changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards, barry | Need help with something else? Ping vanguard: cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: robru is on vacation
=== gatox_lunch is now known as gatox
psivaajfunk: i'll double check about that16:22
=== karni is now known as karni-afk
davmor2popey, brendand, ogra_, sil2100: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1379296 steps added can you all confirm16:40
ubot5Ubuntu bug 1379296 in unity8 (Ubuntu) "unity8-dash should be excluded from app lifecycle management" [High,Triaged]16:40
davmor2Saviq: ^ it's all your fault ;)  should be easily reproducible now too hopefully16:41
ogra_(well, not in the bug status since it is already trigaed)16:42
Saviqdavmor2, but it scrolls faster now!16:42
davmor2Saviq: but oom score kills dash possibly the last thing that should ever die ;)16:43
Saviqdavmor2, no, the shell is the last thing that should ever die ;P16:43
davmor2Saviq: apps open quicker too16:43
Saviqand the foreground app should die after dash16:43
davmor2Saviq: technically upstart is the last thing that should ever die :P16:44
Saviqdavmor2, Debian disagrees :P16:44
davmor2Saviq: hahaha16:45
davmor2Saviq: there are at least nice reproducible steps now :)16:46
=== karni-afk is now known as karni
popeyogra_: https://bugs.launchpad.net/five-letters :D16:51
dbarthSaviq: did the mir situation improve btw? installing silo 20 didn't work so well on my krillin16:52
camakosil2100, testing is done successfully... please publish utopic silo 8, then rtm silo 20..16:56
camakocjwatson ^^16:57
sil2100camako: hmm16:57
sil2100camako: did you notice that the arm64 builds failed for mir?16:58
camakosil2100, that's an unsupported platform..16:58
camakosil2100, I think it's a sync bug16:58
sil2100It was supported earlier I think, since the utopic archive has arm64 binaries of it16:59
dbarthline 82 actually16:59
sil2100Let me rebuild the package in the PPA, it seems to be an unit test failure16:59
camakosil2100, I only see amd64, armhf, and i386 on the RTM silo for mir17:01
sil2100camako: yeah, but I'm talking about utopic17:01
sil2100camako: silo 008 ;)17:01
sil2100camako: utopic has arm64 and we need to make sure that all platforms are buildable that were buildable before17:01
camakosil2100, do we build a different set of archs in utopic vs rtm?17:01
sil2100camako: yeah, RTM has less architectures17:02
camakosil2100, gotcha17:02
sil2100Otherwise it would get blocked in proposed17:02
camakosil2100, ok I see, the unit test failure is a known intermittent failure that we have a bug for..17:03
=== alan_g is now known as alan_g|EOD
barrydbarth: please confirm the dupes: https://ci-train.ubuntu.com/job/prepare-silo/2683/console17:04
sil2100Ok, so a rebuild of the arch might help then :)17:04
psivaajfunk: so that's test plan work with jibel17:04
camakoyea I'm hoping17:04
bzoltan2ogra_: rsalveti: That phablet-tools and SDK PPA issue could be easily solved. Just ping me when you release an update for Trusty in the phablet-tools PPA and I will take that package into my testing/releasing queue.17:05
jfunkpsivaa: yes, that's what I siscussed with asac17:05
psivaajfunk: ack17:05
bzoltan2ogra_: rsalveti: The automatic/brainless regular copy would be only viable if all package in that PPA would be released after testing them with the SDK.17:06
dbarthtrainguards: o/ can i get that silo on line 82 please?17:07
sil2100dbarth: I think barry was handling that ^17:08
sil2100dbarth: I think he wanted to confirm from you something17:08
barrydbarth: you need to confirm that the collisions with the other silo are okay17:08
barrydbarth: https://ci-train.ubuntu.com/job/prepare-silo/2683/console17:08
asacjfunk: psivaa: jibel: plars: can we arrange a briefing call on the testing?17:09
barrydbarth: otherwise you could overwrite the changes in that other silo17:09
asaci think everyone who is in that testing effort should be there17:09
asacso details how things are arranged, managed etc. are clear17:09
psivaaasac: +117:09
ricmmogra_: jdstrand ah good point17:09
ricmmits the app actually17:09
ricmmtechnically unity8 creates it first17:10
ricmmas it is the first QML app to launch17:10
plarsasac: I'd like that, I caught a bit of an earlier conversation that makes it sound as if I was asked to do one thing but the expectation is another. So I'd like some clarification17:10
ricmmso it will be ok17:10
jfunkasac: iahmad will be the one taking over from jibel17:10
cwaynehi, why is rtm silo 10 not on the trello board?17:15
cwayneit looks as though it's been signed off as tested...17:15
kenvandinethostr_, did you publish rtm silo 6?17:16
kenvandinebarry, someone published rtm silo 6, it wasn't tested or ready to publish17:18
barrykenvandine: hmm.  looks like it can't publish it anyway, right?  i hope it wasn't me, but i only push the button when i see all blue in the dashboard17:21
kenvandinebarry, yeah, it wasn't checked as tested17:22
kenvandinebut it uploaded17:22
kenvandineand it really isn't ready :)17:22
kenvandinenot even sure why it was built in an rtm silo, the comment said not to allocate until it landed in utopic17:23
taiebotAre the images broken i am asked to upgrade to 275? but i have already upgraded. Done it twice today but it still looks like i am on r274 (on the abot page)17:23
dbarthbarry: ack; cause we need to get started testing; howver is there a lock to prevent us to land a silo that would ne rebuilding after a previous one landed?17:24
barrykenvandine: i wonder if it was somehow mistakenly blue in the dashboard.  either mistakenly marked as tested or no q/a signoff needed.   i don't remember pushing that publish, but maybe i was a bad monkey17:24
kenvandinebarry, but if it wasn't checked as tested, it shouldn't even let you17:24
kenvandinebugs in the tools ?17:24
barrythat's possible i 'spose17:24
kenvandineit's in proposed17:25
kenvandinecan we kill it quickly?17:25
kenvandinebefore it goes to release17:25
barrydbarth: mark it as qa testing needed and then it should not get published until qa signs off, unless of course kenvandine's gremlins bites you too :/17:25
barrykenvandine: tell them in #ubuntu-release.  they should be able to kill it17:25
dbarthugh, i hope they won't bite me ;)17:26
kenvandinebarry, ok, i made my plea17:28
kenvandinei hope someone sees it quick enough17:29
barrykenvandine: ping infinity17:29
kenvandinepromotions in rtm seem to happen quickly17:29
cwaynesil2100: any idea why rtm silo 10 isn't in the trello board?17:32
robruMirv: just reading scroll back. You need to use "landing team tools > assign to silo" from the spreadsheet and it will do the reconfigure on steroids. The "reconfigure" link in the individual cells is the unprivileged one that non-train guards can use.17:33
kenvandinebarry, if we can get testing verified on my new rtm silo 23, could we just force an upload which doesn't include the bad upload?17:38
kenvandineor i guess maybe a manual upload to squash it17:38
camakosil2100, it failed again in the same test... We don't have a convenient way of developing/fixing on arm64 _and_ verifying that what we did actually works.. Who do we talk to to exclude it from the list of supported archs?17:40
camakocjwatson ^^17:43
robrubarry: kenvandine: there's no check in the tools to prevent publishing a silo that isn't marked as tested. The only thing I'd that the dashboard doesn't say "you can publish" until it's marked as tested. The train will allow publishing anything in state "packages built"17:45
kenvandinebfiller, did you forget to add an rtm line to the spreadsheet for content-hub?  the utopic landing has a comment "sync to rtm"17:45
kenvandinerobru, bummer... i thought you'd have to add some flag or something to ignore it17:45
barryrobru: right.  i never publish anything that isn't blue and says "tested, you can publish"17:46
kenvandinerobru, what's the preferred method of reverting?17:46
barryrobru, kenvandine but it's entirely possible my evil monkey twin (of which i have 12) did it behind my back17:46
robrukenvandine: nah because that info is only in the spreadsheet, and the train doesn't read anything from the spreadsheet, ever. Only the dashboard does that.17:46
robrukenvandine: for a revert I'd say do a manually upload with a higher version like "foo.is.bar" with the contents of the lower version17:47
barryrobru: concur17:47
barrykenvandine: apologies for the derailment17:47
camakokgunn ^^ see my last comment to sil17:48
robrukenvandine: if you branch lp:cupstream2distro, there's a script called citrain/reverter.py but i never used it, can't speak to it's efficacy17:48
kenvandinebarry, would you mind doing the revert?  i'm in the middle of testing several things for people17:48
kenvandinenow i need to get my head back on straight... and start breathing :)17:49
barrykenvandine: please remind me of the source packages to revert?17:51
kenvandineubuntu-system-settings :)17:51
barrykenvandine: also, be aware, i am leaving for a drs appointment in a few minutes.  slangasek will cover for me, so he'll have to babysit it17:51
kenvandinebarry, thx17:51
kenvandinethankfully i don't think we're in the middle of an rtm image build :)17:52
barrykenvandine: ubuntu-rtm only, right?17:52
kenvandineutopic is cool17:52
* barry runs the script...17:52
barrykenvandine: IndexError :(17:53
barrykenvandine: what version should we downgrade to?17:53
* barry tries again17:54
=== barry changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards | Need help with something else? Ping vanguard: cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: robru is on vacation
barrykenvandine: the script didn't fail, but it also hasn't completed yet.  i am out of time.  please coordinate with slangasek in my absence17:58
=== slangasek changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards, slangasek | Need help with something else? Ping vanguard: cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: robru is on vacation
slangasekkenvandine: ok, so we still want a revert of ubuntu-system-settings to 0.3+14.10.20141007-0ubuntu1, which is the version in utopic at the moment?18:13
slangasekkenvandine: is there a bug to reference or anything?18:13
kenvandineslangasek, nope18:13
slangasek"or anything" :-)18:14
slangasekI'm not uploading a revert without knowing why ;-)18:14
kenvandinethere is a newer version in utopic-proposed right now18:14
kenvandineslangasek, it wasn't meant to be published18:14
kenvandinenever marked as tested18:14
slangasekoh, so all you need is ubuntu-system-settings 0.3+14.10.20141009-0ubuntu1 not in utopic-proposed?18:14
kenvandinebarry published the silo18:14
kenvandineslangasek, no... not that18:14
kenvandinewe need 0.3+14.10.20141007-0ubuntu1 in 14.0918:15
slangasekcurrently 14.09 has 0.3+14.10.20141007.2-0ubuntu118:15
kenvandinei was just mentioning there is a new version close to promotion for utopic18:15
kenvandineyeah, that's what we are reverting18:15
slangasekso what does the utopic-proposed have to do with it?18:15
kenvandinei was just mentioning there is a new version close to promotion for utopic, making sure you didn't grab that :)18:16
brendandogra_, ricmm - didn't anyone run the autopilot tests with silo 19??18:16
davmor2sil2100: brendand: tomorrow morning we might be without electric for the first 3 hours while the sparkies run second fix, so I might not make the morning meeting just a heads up on that18:16
slangasekkenvandine: mmk.  So what you *do* want is ubuntu-rtm/14.09 reverted to 0.3+14.10.20141007-0ubuntu1 ?18:16
brendandogra_, ricmm - i mean QA should no way have to do that for sign-offs18:16
kenvandineslangasek, yes please18:16
slangasekkenvandine: I need some explanation of "why" to put in the changelog18:16
kenvandineok, reverting an unintended upload?18:17
slangasekkenvandine: ok.  So it hasn't specifically shown any bugs, we just want to revert it quickly before they have a chance to be found the hard way? :)18:19
kenvandineslangasek, yeah, that silo was not ready to be uploaded, and we actually know it doesn't work18:19
kgunnslangasek: hey, so camako and i are scratching heads, we're trying to approve and land a mir silo...that for some reason is failing on arm6418:20
kenvandinei don't even know why a rtm silo was created for it... the utopic silo was just experimental with a comment to that affect18:20
kgunnbut slangasek we're not sure why it's building for arm64 all of the sudden18:20
AlbertAtrainguards: can I get a silo for line 85?18:20
kenvandineslangasek, which might explain my panic here when i saw it got published to rtm :)18:20
slangasekkgunn: mir has successfully built on arm64 before18:21
kgunnslangasek: so did something under our feet change? b/c this same code was18:21
asackenvandine: hmm. why do you need an experimental silo?18:21
camakoslangasek, it's a new test that was added18:21
asacthat has no landing intend?18:21
kgunnjust built y;day in an rtm silo18:21
kgunnqa approved and in package migration18:21
camakokgunn, rtm doesn't have this arch18:21
kenvandineasac, thostr_ had created it for experimenting with the apneditor18:21
kgunn....we're landing in reverse18:21
kenvandineasac, which we think is close to being ready18:22
* asac wonders if experimental silos are standing practice18:22
asackenvandine: and that silo got accidentially synched to rtm?18:22
slangasekkgunn: arm64 is not enabled for rtm and is enabled for utopic18:22
kenvandineasac, yes... and published18:22
kenvandinebut not to utopic18:22
kenvandinejust to rtm18:22
sil2100Well, if it got published, it had to be marked as tested18:22
kenvandineasac, without being marked as tested18:22
kenvandineunless someone changed it twice :)18:22
sil2100kenvandine: which silo was that?18:22
asacsil2100: slangasek: so i am not sure, but i feel just using comments to mark something taht shouldnt go in might be a bit error prone18:22
kenvandineit's also marked as requires QA18:23
asacwonder if we can do something different18:23
asaciirc we talked once to create a separate ppa tool for experimental silos etc.18:23
kenvandinesilo 20 for utopic18:23
kenvandinewas silo 6 for rtm18:23
asacnot sure18:23
kgunnslangasek: so question, this is backing us up...long story, it won't land in rtm, stuck in proposed, until it lands in utopic18:23
kenvandinei don't even know why someone created an rtm silo18:23
asaci know we discussed, but that was long ago18:23
kgunnis there any way around ?18:23
kgunnand if not,18:23
asaclike a cisandtrain :)18:23
kgunnhow do we test/verify quickly on arm64 ?18:23
* kgunn notes another reason not to land in reverse18:24
sil2100kenvandine: was that ubuntu-system-settings?18:24
kenvandinesil2100, yes, apneditor18:24
sil2100kenvandine: I see barry published thatm, maybe he got struck by the dashboard having a glitch ;/18:25
slangasekkgunn: sorry, give me one second, still working on this revert for kenvandine - I can explain the "why's it like that" with half a brain, but need my whole brain to answer "how do we fix it" :-)18:25
kenvandinehe said he didn't publish anything that wasn't blue on the dashboard18:25
sil2100I noticed that sometimes the dashboard doesn't instantly indicate the status of the silo and a refresh ir required18:25
sil2100And has some broken lefrover states on it...18:25
kenvandinesil2100, yeah... sometimes18:25
sil2100Anyway, ouch...18:25
kenvandineslangasek, thx for helping, i really need to focus on other stuff atm18:26
slangaseksil2100: is this a dashboard glitch that will be fixed when we move off the spreadsheet?18:26
Ursinhaslangasek: the dashboard fetches the information from spreadsheet/jenkins json, maybe it's something that needs to be revisited in the dashboard side when changing it to talk to ticket system18:29
slangasekkgunn: so I haven't quite worked it out yet from the history, but I clearly see that someone explicitly included arm64 in the list of targets for mir to build on18:29
kgunnslangasek: right, my bad...i just looked in rtm ppa's and made a bad conclusion18:30
kgunnslangasek: but we landed in reverse, e.g. rtm first...then copied to utopic18:30
Ursinhasil2100: hey, is https://code.launchpad.net/~sil2100/cupstream2distro/cu2d-duallanding-new/+merge/237131 ready for review or I should consider the description that says it's not? :)18:30
kgunnsince that was being advertised to us as a way to get to rtm faster18:30
kgunnbut now we're here....so lots of days have gone by now :)18:31
kgunnslangasek: anyway...what are our options18:31
slangasekkgunn: apparently arm64 was listed in the architecture list of the mir package from the beginning... so it doesn't seem to be an accident.  Shouldn't you just be fixing whatever's causing the test to fail on arm64?18:31
camakoslangasek, our devs don't have arm64 hw, how do we fix errors on arm64? some chroot/emulator thing?18:31
slangasekkgunn: who was advertising this as an option?  the rtm and utopic builds should at most be happening in parallel18:31
kgunnslangasek: asac18:32
kgunnand others18:32
sil2100Ursinha: just wanted the CI to kick in and make sure all is ok ;)18:32
slangasekcamako: well, I have an RT open for porter-arm64.canonical.com which is supposed to be happening RSN, but that doesn't help you today. :/  if it's urgent, talk to dannf about getting hardware access18:32
asacslangasek: check with sil2100; we had a pilot18:32
asacwith phonedations18:32
slangasekasac: but kgunn isn't phonedations, so this seems to have progressed beyond the pilot :)18:33
Ursinhasil2100: okay :) let me know when that's up for review then :)18:33
camakoslangasek, since we don't have a way to verify the code/fixes, should we be supporting this arch?18:33
kgunnolli_: ^18:33
sil2100Ursinha: so, most of the pieces there are ready for review more or less - there might be some changes still, but I guess most of it is ready18:33
asacslangasek: yeah, he had troubles and i suggested he might wanted to check if with LT if thats ok to try18:33
asacslangasek: in general i dont know how the pilot was implemented. i fully agree it should build on bothh targets at tsame time18:34
Ursinhasil2100: got it18:34
asacwhat phonedations i thought is doing is just focus on testing on rtm first18:34
asacand publish rtm first18:34
asacbut sil2100 knows details18:34
slangasekcamako: that's a question for the mir team to decide, not me - I don't know why arm64 was put in the architecture list in the first place18:34
sil2100asac: isn't that what everyone that's landing first in RTM doing?18:34
asacslangasek: ^^ :)18:34
asacseems the pilot was rolled out18:34
asacsil2100: are we doing this everywhere now?18:35
kgunnolli_: so long story made short, i'm concerned about lock-down keeping this mir landing out...we landed in reverse, but the delayed discovering arm64 no workie18:35
* asac doesnt mind if it works and if slangasek is also happy'ish 18:35
camakoslangasek, fair enough... who do we talk to to get arm64 out of the arch list for mir?18:35
asacsil2100: so id dint realize we rolled the pilot out to more teams18:35
kgunnolli_: so i'm gonna ask that altho the mir landing isn't critical, that we have some grace into friday for the lock down, and let us land18:35
asacwould have expected an announce18:35
slangasekcamako: er, the mir team should make that change18:35
asacso we are all on same page18:35
slangasekcamako, kgunn: I'm perfectly happy with the mir team saying that arm64 shouldn't be in the supported architecture list; what I don't want is for this to be a flip-flop18:36
asackgunn: is it built?18:36
slangasekwhere we remove the package one day and re-add it the next18:36
slangasekhowever, there are also reverse-dependencies on mir in the archive that would need to be dealt with18:36
olli_kgunn, I think that's fine18:37
kgunnqtmir, platform-api, unity-sytsem-compositor18:37
jdstrandballoons: fyi, approved the MP18:37
AlbertA2slangasek: can I get a silo for line 85?18:38
camakokgunn, slangasek, qtmir, and papi don't support arm6418:38
camakoonly u-s-c18:38
asacsil2100: so is it still a pilot or is it an option :)?18:38
sil2100asac: we didn't, it happened automatically18:38
asacso you lost control :P18:39
sil2100asac: it just changed into an option, noticed that people started landing this way without any problems so yeah ;)18:39
kgunncamako: xmir ?18:39
camakowhich is another reason to not support arm64... since what do you do with mir if you don't have others in place18:39
kgunnsorry, just being complete18:39
slangasekcamako: the list that needs to be sorted through is here: http://paste.ubuntu.com/8528438/18:39
asacslangasek: so ... guess above is evolution :)18:39
asacnot sure we want to row back?18:39
sil2100asac: as long as changes get synced up to utopic, which is what we're making sure, then we don't care on the process18:39
slangaseksil2100, asac: we need to reel this back in.  No one should be building in rtm first.18:39
camakokgunn, dunno abt xmir18:40
sil2100hm, I guess people that were present on the meeting a few weeks ago misunderstood that, right?18:40
slangaseksil2100: no, this goes to the discussion we had about not having n-way "sync" handling in the citrain18:40
asacso i think its the combo of sync18:40
asacand rtm first18:40
asacthat causes headaches for slangasek18:40
slangaseksyncs should always be built in ubuntu->rtm, not the other way around18:41
slangasekand we should support having these tested in parallel18:41
asacbut shouldnt britney catch it in utopic? isnt rtm first actually safer because we have britney there, but not rtm?18:41
sil2100Ok, anyway this will be invalid tomorrow, as the stuff for the dual-landing as per slangasek recommendations is ready18:41
slangasekasac: we have britney in both, and how would *not* having britney make something safer?18:41
asacslangasek: but in practice utopci to rtm sync is also not aalways true and only proposed migration would catch the casese where a sync isnt right, correct?18:41
sil2100slangasek: as already mentioned during our discussion, during that meeting no one said 'don't build rtm first', so people started doing that18:42
sil2100slangasek: when rsalveti came up with this idea18:42
asacslangasek: yeah i was saying its afer to sync to utopic if rtm doesnt hafve brtney18:42
asacslangasek: instead of synching from utopic into non-britney rtm, but its moot ifthere is britney in both18:42
asacsil2100: note that sync wasnt the default then18:42
asacso uits a mix up18:42
sil2100asac: it wasn't?18:42
sil2100asac: it was18:42
asacwe worked on it18:43
asaci dont think we said we would binary sync his rtm stuff18:43
sil2100asac: no no, it was already there, I remember that because we were discussing with landers about how they like the syncs18:43
asacslangasek: so in general i think its not that risky with same toolchain on both sides, and britney, but i think i even asked you directly in our sync how we can do both directions :)18:43
asacslangasek: guess we misundestood18:43
balloonsogra_, jdstrand where are you seeing the apparmor issues at? And is only calc affected? from the looks I things I assume calendar and a few more that do similar things would also have the same issue18:43
sil2100Then I might have either misunderstand the decisions, same for others18:44
sil2100Anyway, did this cause any issues right now?18:44
asacslangasek: i am in general concerned about syncing tbh18:44
asacreproducibility etc.18:44
asacsil2100: we dont know, but we should imo take a step back and think through exactly what what means18:44
sil2100asac: but is there a problem caused by this right now?18:45
sil2100Or are we discussing this as a principle?18:45
sil2100As I understand that it might be 'not too good' by principle, but I want to know if we noticed a real problem regarding that right now18:45
asacsil2100: right. i personally thinhk we should not judge out of principle what direction works18:46
asacand we shouldnt dismiss rtm to utopic synching18:46
asachowever, i dont think we should do it without thinking hard either18:46
asacalso we shouldnt do it by letting landers just adopt a pilot18:46
asacwithout us not enforcing that its not established procedure18:46
sil2100As I mentioned, we will introduce anyway a new scheme tomorrow that will no longer use this 'broken' approach anyway18:47
slangasekrtm to utopic syncing is a problem because we have a mess of confusing options implemented in spaghetti code on the train to support this18:47
sil2100Since CI Train now will simply build for utopic and publish to both 14.09 and utopic18:47
asacok, if thats the only concern then thats not so worrying. i was more worrida bout archive integrity / bustag etc.18:47
sil2100None issues got reported, but I agree with slangasek that it can lead to potential problems18:47
asacanyway, i dont want to really make a call on this. all i know is that we had a pilot and that pilot not well executed18:48
asacand i dont think thats the way to do it18:48
slangaseksil2100: ok, the above conversation with kgunn is an issue that's being reported18:48
jdstrandballoons: I was only pointed to the calculator. anything that uses fakeenv would be affected (though I don't know what all that was)18:48
sil2100slangasek: the arm64 build failure on utopic?18:48
slangaseksil2100: that they are finding late as a result of trying to sync from rtm to utopic, yes18:48
asaclet me know what you agreed and what the way forward is18:48
balloonsjdstrand, ok. I'm just curious who's trying to land this and be pointed at the results they got. I know more than calc must be affected18:49
asaci dont think there is a big problem besides letting a confineed pilot go loose without making a team decision etc.18:49
asacbut thats a pretty big problem for my hat :)18:49
asacsil2100: the ricmm AP regression ... what packages are affected?18:50
asacseems only balloons  packages are afected?18:50
asacthat feels oddish as above18:50
sil2100I might have not gated that correctly, but as I am no manager I do not know what management decisions have been made18:50
asacsil2100: you have big  authority18:50
sil2100So every landing into RTM first I thought was decision somewhere ;p18:50
sergiusensasac: sil2100 iirc, you asked me how the pilot was going, I said it was going fine, but most of my stuff was golang and then came an announcement email18:50
asaci doubt someone came to you telling you that management decided to land first everywhere18:50
asacsil2100: you are the authority about the landing engine18:51
asacsil2100: noone makes decision about changing this witout talking to you18:51
asacso just reject anyone saying that in futrue18:51
kgunnwhat really hurt us is that our project jenkins doesn't test it, rtm didn't test it, only utopic landing....so we didn't know for a long time18:51
asacor if you feel there might be a decision, thats not the case18:52
asacuntil someone talks to you18:52
asacsil2100: ^^18:52
asachope that helps18:52
asacgiving you backup18:52
sil2100Ok, anyway seems to be my bad then, but there was only a limited number of people landing first to RTM as well18:52
asacsil2100: no its fine18:52
asacsmall bad :)18:52
sil2100And from what I know this did not become a problem in overall, since otherwise we would stop the line18:53
sil2100kgunn's problem is the first we saw18:53
asacjust figure with steve what we do now :)18:53
sil2100And even this doesn't seem to be super bad18:53
asacwithout being unpragmatic i guess18:53
sil2100asac: well, we already have an evil scheme that's just waiting in a branch18:53
asacsil2100: is that agreed?18:53
asacwhat is that scheme?18:53
asacwell, i dont mind18:53
asacas long as your team and steve are aligned and all  the landers are happy with what is coming18:54
asacor at least are not unhappy :)18:54
sil2100asac: it came up with a discussion with slangasek, so yes - it's much safer, much more convinient18:54
sil2100And less resource-usage18:54
sil2100As basically we'll only use utopic silos18:54
sergiusensasac: sil2100 wasn't the rtm image supposed to be our fallback for when the ubuntu archive froze?18:54
sergiusensand avoid the FFe?18:54
slangasekdoes anyone here know how I actually upload to ubuntu-rtm?18:55
asacsil2100: i assum thats only for the sync case?18:55
asacsil2100: i guess for diverged trees it makes sense to use rtm silos18:55
sil2100slangasek: you need to change your dput.cf18:55
asacslangasek: no way, only through silo :)18:55
sergiusensand play nicer with the community18:55
asacsil2100: dont tell :P18:55
slangaseksil2100: yeah, do you have a config for that?18:55
sil2100slangasek: yeah, pastebining int now18:55
sil2100slangasek: http://paste.ubuntu.com/8528507/18:56
rsalvetisil2100: asac: the main issue is that we don't have a clear definition about what people should do :-)18:56
sil2100asac: ;)18:56
rsalvetiso they just assume stuff18:56
rsalvetibut yeah, doing binary copies from rtm to ubuntu is not a great idea18:56
slangaseksil2100: thanks18:56
sil2100rsalveti: yeah, that's why we started working on the LandingProcess document as well18:56
slangasekkenvandine: revert uploading18:56
asacrsalveti: i dont buy that18:56
rsalvetimy idea was landing first in RTM and then landing the src package in utopic18:56
kenvandineslangasek, thanks!18:56
asacrsalveti: folks just tried, LT missed or thought it was ok18:56
sil2100rsalveti: oh, source copy then?18:56
asacand then folks copied that approach18:56
asaclike floodgating18:57
sergiusensI don't like the binary copy fwiw18:57
sergiusensand mentioned it a couple of times18:57
asaceveryone knew that utopic first was the standard18:57
asaci at least talked to everyone twice about that18:57
rsalvetiasac: right, but not having a well defined process makes people to assume stuff18:57
asacbecause they came all to me complaining18:57
rsalvetior copy behavior from others18:57
sil2100Then why did everyone tell me that source copies are bad?!18:57
asaci dont complain18:57
kenvandinecan someone confirm line 86 is an isolated bug fix?18:57
kenvandinediff https://code.launchpad.net/~ken-vandine/content-hub/lp1373086/+merge/23745918:57
slangaseksil2100: because I don't agree with sergiusens ;)18:57
asacsergiusens: no18:58
rsalvetiit all depends on the package18:58
asacsergiusens: we will revisit next week18:58
sergiusenswhat did I say? :-)18:58
slangaseksil2100: I think treating something as a *sync* when it's not binary is bad18:58
slangaseksergiusens: <sergiusens> I don't like the binary copy fwiw18:58
asacsergiusens: will you fallback to rtm when utoic is frozen :)18:58
rsalvetifor sensitive ones (that gets easily affected by gcc and such), it might not always be a good idea to do binary copy18:58
asacanswer is "yes, if its a critical bug approved"18:58
sil2100I... I'm confused, I think that it's time for me to EOD now ;p18:58
sil2100Anyway, tomorrow a new approach will be available in the train which I hope will become the default18:59
sil2100We'll discuss that more tomorrow I guess after it's deployed in production18:59
sergiusensslangasek: oh, right ;-) that's fine to disagree on and I'm not making a fuss :-P18:59
* sil2100 really needs to go now18:59
* sergiusens should of kept his mouth shut or fingers tied :-)18:59
asacimo we just need faster builds18:59
asacthen push it into both18:59
asacoh, but then we have theversion problem18:59
rsalvetino simple solution that works for everyone18:59
asacwe could start using a universal versioning scheme18:59
asacthat encodes package version with the nice archive :P19:00
sergiusensasac: rsalveti only good solution is for everyone to know about packaging and do their own packaging branches ;-)19:00
rsalvetisergiusens: there is still an issue of publishing them into 2 archives19:00
sergiusensbut I think that's what most core devs complained about when using the train19:00
rsalvetithe only sane way is not branching rtm so early in the process19:01
rsalvetiand make it a more 'stable-only' thing19:01
asacrsalveti: right, thats the plan19:01
asacrsalveti: every two weeks product team meets, checks if we are feature ready for another feature release19:01
sergiusensstill, I thought rtm was going to be a fork to make life easier and gain speed, turned to be the other way around19:01
asacif we are, we branch, bug fix only, 2 weeks before market we branch a minibranch for critical only19:01
asacthe stable branch continues so we can feed more stable updates from that19:01
asacuntil w ahve the neds feature wave19:02
asacevery 2-3 month we cut from feature branch; 1 month stabilization 2 weeks productization :)19:02
sergiusensasac: you will only see how painful the train is until you use it ;-)19:02
sergiusensasac: you can be the next lander for mir or dbus-cpp ;-)19:03
asacsergiusens: i dont need to19:03
asaci know the world before the train19:03
Ursinhaasac: I think you do :)19:03
asacvery well19:03
asacand i know the train makes big difference without even trying :P19:03
slangasekcamako, kgunn: ok, dropping mir on arm64 requires sourceful uploads of glmark2, gtk+3.0, trust-store, and ubuntu-system-settings-online-accounts to remove their use of mir on arm64 (i.e., to bring them in line with powerpc, ppc64el architectures); and binary removals from the archive of unity-system-compositor19:03
asacand yes, it would be amazing if its airline19:03
jdstrandslangasek: "I think treating something as a *sync* when it's not binary is bad". I think it depends on your perspective. I thought of the source syncs as akin to Debian syncs, since ubuntu and ubuntu-rtm are different distros. I also can see the counterpoint to that19:04
camako slangasek, ack we will do that19:04
Ursinhasergiusens: we're working on replacing the spreadsheet right now, next step will be probably the dynamic PPA creation and assignment... citrain will become less horrible overtime, until it becomes the airline :)19:04
Ursinhaand I'd love to find another name, I don't like "airline" hehe19:04
AlbertA2Ursinha: "rocketship" to go with the whole space theme we got going in canonical19:05
Ursinhahaha, I kinda like it19:05
asacslangasek: can i in theory land everything too?19:06
asacslangasek: like offer to serve as a slave for kgunn if he pays me to? or do i need special powers?19:06
asacsergiusens: it might actually happen :)19:07
sergiusensasac: lol, acting as a trainguard != lander ;-)19:08
asacsergiusens: that i land stuff ... just need to sleep over the idea :P19:08
asacsergiusens: no, actually landing for folks19:08
Ursinhaasac: the only way to get full access is being a coredev, and you still need a QA person to signoff your changes19:08
Ursinhaas a lander19:08
asacUrsinha: i want to land, not be a trainguard19:09
asacthats fine19:09
Ursinhaasac: as a lander :)19:09
asacjust as lander19:09
asacwonder if the merge back into mir etc. would work19:09
asacbut guess so19:09
Ursinhaasac: you can't cheat the system, try to use it as is :)19:09
Ursinhaasac: https://wiki.ubuntu.com/citrain/NewbieGuide19:10
asaci wouldnt cheat; i would do a challenge and sacrifice my blood for the sake of a much greater goal :P19:10
asacbut i have to check and first learn so i dont risk the mielstones19:10
sergiusenstrain procedures broke again19:11
sergiusensI thought a rebuild was an empty MP19:11
sergiusensnow it's just "nothing to do, goodbye"19:11
asacUrsinha: that newbieguide is for trainguards, right? not landers19:12
asacah yeah it says it right on top19:12
asacis there something similar for landers?19:12
slangasekAlbertA2: silo 006 assigned, sorry for the delay19:13
AlbertA2slangasek: awesome thanks!19:13
slangasekasac: "land everything"? in reference to the mir fix?19:14
Ursinhasergiusens: I'm trying to understand what changed to justify that19:14
slangasekasac: these are mostly source package changes, which could reasonably bypass the silo in favor of direct core-dev uploads (since they're packaging-only changes)19:14
sergiusensUrsinha: I added an "rebuild" debian/changelog to get something going19:14
slangasekAlbertA2: oh, hang on, something failed19:15
asacslangasek: i have nothing specific in mind; just wondering if i could offer folks to land their stuff if they pay me :)19:15
asaci will tell you tomorrow19:15
asachope you talk me out of it :)19:15
sergiusensasac: I'll stop complaining when the creators of process live through it, is that payment enough? :-P19:16
slangasekAlbertA2: sorry, I appear to not know what I'm doing with the train; I thought this was a bit more straightforward than it seems to be19:19
slangasekrobru: sorry, if you're still around, can you lart me in the direction of how to get a request_id for a new silo?19:19
slangasekrobru: n/m, I know what I'm doing now19:19
AlbertA2slangasek: np19:20
Ursinhaslangasek: I think you need to go to the spreadsheet line and choose the option from the menu19:20
Ursinhaoh, you found that already19:20
sergiusensUrsinha: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-008-1-build/48/parameters/19:24
sergiusensUrsinha: force rebuild wasn't necessary before; I guess I could of accomplished the same19:25
Ursinhasergiusens: if that follows logic you shouldn't need that now as you have a small diff19:25
Ursinhasergiusens: can we retry that with debug on?19:26
slangasekAlbertA2: ^^ there, *now* the silo is assigned19:26
AlbertA2slangasek: cool thanks!19:26
sergiusensUrsinha: it's too late, it's no longer an empty commit and building already ;)19:29
Ursinhasergiusens: empty commit?19:30
sergiusensUrsinha: sorry, empty merge19:30
sergiusensUrsinha: no diff MP19:30
Ursinhasergiusens: I thought the MP was this one, https://code.launchpad.net/~sergiusens/unity-scope-click/rebuild/+merge/237838 and when I saw it it already had a diff19:31
Ursinhasergiusens: empty MPs used to work before? that was kind of a bug disguised as a feature hehe19:32
sergiusensUrsinha: yes, but look at the build log when I tried, rev was 284, it's now 285 ;-)19:32
sergiusensUrsinha: well it's the only way to trigger a rebuild on the train and what trainguards recommended19:33
Ursinhasergiusens: if you move too fast while asking for help, people trying to help might get confused :)19:33
sergiusensUrsinha: oh, I said it was broken and on the next line I said I would be circumventing that :-)19:33
Ursinhasergiusens: I'm not really questioning the trainguards recommendation, it's that ignoring empty MPs is kinda "expected" hence my comment :) I'll talk to lukasz once he's back to understand what changed there19:36
camakoslangasek, I'll have to start over. Can you please help me abandon the utopic silo 8 and rtm silo 20 please?19:45
slangasekcamako: why start over, vs. pushing an additional commit to drop arm64 from the arch list?19:45
slangasekcamako: (forgive me if this is a stupid question - but it doesn't seem to me that you should need to reset things)19:46
camakoslangasek, please educate me... this is a sync silo and rtm part is in proposed.. So they won't have the same code...19:46
slangasekright, I don't want to try to disentangle this if it's a sync silo :)19:47
camakoand qtmir, is abt to get another silo, which will probably get ahead19:47
camakoand invalidate our testing anyways19:48
asacUrsinha: sergiusens: so i know from old didrocks times that empty MPs _was_ a bandaid feature in old days to allow self-serviced rebuilds19:49
asacwe were quite happy that it kind of came for free and we had many other issues to solve :P19:49
Ursinhaasac: I thought so, want to know when it got "fixed"19:49
asacnot sure if we have something better19:49
asacif so its surely worth killing :P19:49
Ursinhait's probably fixed by accident19:50
robruUrsinha: empty MP's are the official way to trigger no-change rebuilds in the train, and can also be used to effect a trunk release in the event that somebody pushed to trunk manually without doing a train release19:50
asacUrsinha: i think its a bug if there is no equivalent available to trigger self-serviced rebuilds now19:50
asacits a feature that you can rebuild :)19:50
asacright, so i think its a bug because thought its a fix19:51
Ursinharobru, asac, I'm not disagreeing with you :) I just pointed that it's kind of a bug in essence, but if it's used like that and the "bug got fixed" we need to revert it :)19:51
asacthats the problem with these magic19:51
asacwe should surely bring that or something better back though19:51
asacguess bring back and improve later19:52
asacor right after19:52
Ursinhaasac: +1 on that19:52
Ursinhawe're improving while replacing19:52
asacguess the new frontend will fix this ?19:52
* asac wonders if citrain has a bugtracker :)19:53
Ursinhaasac: I believe that would be cu2d project in launchpad (bugs against that project)19:53
Ursinharobru: I'm afraid of asking questions and engaging you on conversations when you should be somewhere !irc :)19:54
sergiusensUrsinha: I'll wait on this one19:55
sergiusensUrsinha: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-008-1-build/51/console19:55
sergiusensUrsinha: trying to rebuild content-hub fails19:55
sergiusensnot clear why19:55
* asac wonders if the term cu2d will die eventually as new pieces land:)19:55
slangasekcamako: ok, so I can clean these silos; after that, you'll let me know when you need new silos?  Are you going to still do this as a sync from rtm->utopic?19:56
Ursinhaasac: yes, it'll be one of the latest pieces to die but it will19:56
camakoslangasek, sure Ill let you know.. it'll be utopic first this time then rtm19:56
Ursinhasergiusens: I'm looking19:56
sergiusensUrsinha: fwiw, the ppa shows it's building still19:57
camakoslangasek, what's gonna happen to the rtm landing stuck in rtm-proposed?19:57
slangasekcamako: oh. why is it stuck in rtm-proposed?19:57
slangasekcamako: http://people.canonical.com/~ubuntu-archive/proposed-migration/ubuntu-rtm/update_excuses.html says it's a valid candidate19:58
camakobecause of some packaging issue we had. sil2100, and cjwatson were aware..19:58
slangasekcamako: ah.  right, it's stuck because some uninstallable reverse-dependencies.  Well, those packages will still be there19:58
=== barry changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards, slangasek, barry | Need help with something else? Ping vanguard: cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: robru is on vacation
camakoslangasek, the plan was to land utopic and then it would land on rtm19:58
barryhi folks, i'm back19:58
slangasekcamako: I /can/ remove the packages from 14.09-proposed, but there's no need to.19:58
Ursinhasergiusens: failed to build?19:59
camakoslangasek, since we didn't land on utopic, I'd rather remove them19:59
sergiusensUrsinha: no, it's still building in the ppa19:59
sergiusensUrsinha: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-008/+build/644806719:59
sergiusensUrsinha: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-008/+build/644806619:59
slangasekcamako: I'd rather just not worry about them, they aren't harming anything and won't get in anywhere that it affects people until the rest of the packaging is sorted?19:59
barrykenvandine: did things get straightened out with rtm?20:00
barry(fwiw, the script failed again)20:00
kenvandinebarry, yup, slangasek took care of it20:00
camakoslangasek, by the time we are ready to land again, we'll have different code.. don't wanna fork..20:00
barrykenvandine: cool.  thanks slangasek20:01
=== slangasek changed the topic of #ubuntu-ci-eng to: Need a silo? Ping train support: trainguards, barry | Need help with something else? Ping vanguard: cihelp | Train Dashboard: http://bit.ly/1mDv1FS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: robru is on vacation
Ursinhasergiusens: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-008-1-build/51/console , right?20:01
kenvandinebarry, sil2100 suspected you might have been bit by the dashboard getting out of sync20:02
kenvandinesometimes it shows blue when it shouldn't, briefly20:02
barrykenvandine: ah.  okay, that's good to know20:02
* barry will be a mellow monkey not an eager beaver20:02
dbarthguys, is mir landed finally? i have a silo full of fixes stuck on a mir dependency20:03
slangasekcamako: there's no need to fork... I'm saying you can ignore the packages that are in 14.09-proposed and behave as if they didn't happen, unless you think there's a risk that they'll make it into 14.0920:03
dbarth ubuntu-system-settings-online-accounts : Depends: libmirclient8 (>= 0.8.0+14.10.20141005) but 0.7.3+14.10.20140918.1-0ubuntu1 is to be installed20:03
slangasekanyway, if you really need them out of there I'll have a look after lunch20:03
kenvandinebarry, i guess when in doubt, look at the spreadsheet :)20:03
barrykenvandine: now i am full of doubt ;)20:03
camakoslangasek, that's what I'm afraid of.. them getting promoted by mistake.. but if you think it's ok .. it's ok by me.20:04
camakodbarth, long story.... we had to give up both mir silos...20:05
dbarthcamako: so i just need to rebuild mine, rihgt?20:05
camakoyeah.. just base it on 0.7.320:05
sergiusensUrsinha: yes20:06
dbarthcamako: wdym? i just have an otopn to rebuild; do i need to update the packaging in the branches?20:07
dbarthcamako: or something in the silos themeslves?20:07
Ursinhasergiusens: man, this is a mess. some packages failed to build and the build job returned failed, but there are packages still building there, though20:08
camakodbarth, lemme check20:08
dbarthcamako: this is rtm silo 220:08
dbarthcamako: i just triggered a rebuild, but if chceck the ppa, you can't install the ussoa package because of that dep issue20:09
cjwatsoncamako,kgunn,slangasek: I went to some effort to get mir/arm64 building a while back, as part of a general effort to simplify packaging by having our stack building more consistently in more places so that we have fewer manual architecture exclusions littered all over the place20:09
cjwatsonif you need to remove packages temporarily, I would prefer it if we just removed binaries as needed rather than excluding them from the packaging20:09
Ursinhasergiusens: is it expected that unity-scope-click fails to build there?20:09
cjwatsonthen it's easier for a porter to come along later and fix things20:09
sergiusensUrsinha: yes20:09
camakodbarth, I see.. so we gave up our silo... but mir 0.8 is still in proposed... I think it needs to be removed probably20:09
Ursinhasergiusens: okay20:10
camakodbarth, rtm-proposed that is20:10
camakodbarth, and then you just rebuild I guess20:10
dbarthcamako: yes20:10
dbarthcamako: but can mir be removed from proposed?20:10
sergiusensUrsinha: simple rebuild wasn't enough as it seems the download manager is fully mocked there...20:10
cjwatsondbarth: why does it need to be removed?20:10
cjwatsonyou can surely just upload over it later20:11
camakodbarth, yes.. see my convo a few mins back with slangasek20:11
dbarthcjwatson: i have a silo stuck on a dependency that is not available; so the silo does not install20:11
cjwatsonwell aware but why does that need removal?20:11
cjwatsonwe agreed a strategy for that earlier today20:12
dbarthah, not aware sorry20:12
dbarthcamako:  ^^20:12
camakocjwatson, it's picking up mir0.8 which doesn't exist20:12
dbarthso how do i get my silo back to clean state?20:12
cjwatsonwell just wait20:12
camakoor rather, shouldn't any more20:12
cjwatsoncamako: so where's the mir/utopic landing?20:13
camakocjwatson, withdrawn20:13
Ursinhasergiusens: so your problem is that the build script failed? content-hub is still building there, but script failed because of unity-scope-click (it seems)20:13
cjwatsoncamako: yeah, foolish reasons IMO20:14
camakocjwatson, see scrollback20:14
cjwatsonI think we should put it back in, strip arm64 binaries out of the archive as needed, move on20:14
cjwatsonslangasek: ^-20:14
sergiusensUrsinha: but it was told to only build for content-hub in the parameters20:14
camakokgunn ^^20:15
cjwatsondbarth: also there's no reason for this to hard-block your silo; we can have it build against non-proposed20:15
tvosstrainguards, could someone reconfigure rtm silo 520:15
loolhey trainguards, I've updated silo 5 to list a missing package, would you mind reconfiuring it?20:15
loolas to sync the extra package (ubuntu-location-provider-here)20:15
cjwatsondbarth: which silo is this?20:15
dbarthcjwatson: it's rtm-00220:15
barrytvoss: sure thing20:15
dbarthi just took a bad dependency, cause the initial build this morning was fine20:15
tvossbarry, great, thank you20:15
Ursinhasergiusens: hm, okay, one moment20:16
barrytvoss: row 65, right?20:16
cjwatsondbarth: uh it appears to have built?20:16
cjwatsonat least on amd6420:16
sergiusensUrsinha: your explanation can make sense though; but there is no indication (clear one) of that being the reason20:16
dbarthcjwatson: i triggered another rebuild a few minutes ago20:16
tvossAlbertA, ^20:16
cjwatsondbarth: to achieve what?20:16
tvossAlbertA, see barry's question20:16
dbarthcjwatson: try to get rid of the dependency; but that won't work since mir is still in proposed20:17
cjwatsonso hammering on rebuild without understanding20:17
cjwatsonyay citrain :-/20:17
dbarthcjwatson: the silo is yours to reconfigure if you can fix that20:17
barrytvoss, AlbertA: there are silo conflicts.  should we override? https://ci-train.ubuntu.com/job/prepare-silo/2694/console20:17
cjwatsondbarth: the silo is now configured to build not against -proposed.  rebuilding it now should be effective when it wasn't earlier20:18
dbarthcjwatson: was following camako's remarks20:18
Ursinhasergiusens: what I see is that it tried to build unity-scope-click and failed, if expected behavior is to ignore all other packages when you provide specific names then this should be the problem (should rebuild selectively but it's not)20:18
dbarthcjwatson: thank you sir! :)20:18
Ursinhasergiusens: I'm looking at the code here to see if it's a bug or jenkins misbehaving20:18
bfillerbarry: could I have a silo for line 87 please?20:18
sergiusensUrsinha: well, the success value there might indicate everything is good in the big picture20:19
sergiusensUrsinha: so it can make sense; but only if you are very very familiar with the train ;-)20:19
kgunncamako: yeah kind of following...so i think cjwatson and slangasek aren't saying the same thing20:19
cjwatsonwe are not20:19
cjwatsonso we need to have it out :)20:19
AlbertAbarry: yes ignore landing-00120:19
sergiusensUrsinha: so one log line can do worlds there before failing; and it could wait for the build status of content hub to return, as it does in other cases20:19
Ursinhasergiusens: build job #51 failed, where is the success you're seeing?20:19
barrybfiller: yep, after AlbertA & tvoss20:20
barryAlbertA: cool20:20
cjwatsonmy position is that packages should only have explicit architecture limitations when there is no viable alternative, and simple build failures aren't a good enough reason for that awkwardness20:20
bfillerbarry: thanks20:20
sergiusensUrsinha: I said "might"20:20
sergiusensUrsinha: and "could"20:20
cjwatsonand that if a package is long-term failing to build and that we believe it to be an unreasonable cost/benefit trade-off to fix, it's reasonable to remove the outdated binaries from the archive without blacklisting the architecture from the packaging20:20
sergiusensUrsinha: meaning, not talking about the silo itself, but the logic the train might have ;-)20:21
Ursinhasergiusens: haha, okay, sorry :) the problem is probably it's not considering the right list of packages, we could try to rebuild with debug on20:21
cjwatsonbut in general not having the architecture limitation means that the failures are surfaced to porters who may wish to deal with them, rather than artificially hidden20:21
dbarthbarry: it's about that line 82 ;) i'd still like to get a silo for it; if that's cool with kenvandine's other landings20:24
slangasekcjwatson: did you also see the list of a half-dozen reverse-dependencies that need to be fixed to not reference mir on arm64?  I don't think, for an architecture-specific package like mir, upstream should be at the mercy of porters to get their landings done20:26
slangasekcjwatson: also, mir does have an architecture list in debian/control already, it's just that arm64 is in it - when upstream doesn't have any way to support that20:26
barrydbarth: is that a question? :)  does kenvandine need to approve it, or should i go ahead and give you a silo?20:26
slangasekcjwatson: so I think I would be ok with having mir binaries removed, and not dropping arm64 from the list, but then we still need to deal with the revdeps, and I think architecture exclusion is the right way to do that unless upstream is willing to support mir on arm6420:28
dbarthbarry: gimme, i'll make a deal with kenvandine20:28
barrydbarth: okie dokie!20:29
dbarthbarry: i just know i need to rebuild tomorrow morning20:29
cjwatsonslangasek: those revdeps should just build-depend on the appropriate things so that they'll harmlessly dep-wait if mir isn't up and running20:29
cjwatsonslangasek: we can just remove those binaries too for now - we don't need to change the packaging20:29
barrydbarth: i'm going to ignore the conflict on unity-webapps-qml: https://ci-train.ubuntu.com/job/prepare-silo/2697/console20:30
cjwatsonmir has built on arm64, and it was using the mesa frontend so I dispute that it is a fundamentally horribly architecture-dependent thing20:30
cjwatsonslangasek: I'm fairly sure most of those rdeps didn't build at all until I first got mir/arm64 building, but would be happy to be corrected in detail20:30
slangasekcjwatson: the revdeps are things that need to build a subset of functionality on non-mir archs; e.g., we shouldn't not build glmark2-es2 on arm64 due to a lack of mir20:31
camakoproblem is when the developers don't have easy access to this arch to fix bugs, I don't think this should be on the supported list of archs... It's an oversight on our part.20:31
slangasekcjwatson: the list of affected revdeps that I saw was glmark2, gtk+3.0, trust-store, ubuntu-system-settings-online-accounts20:31
cjwatsoncamako: it would have been nice if people had said that when I was apparently wasting my time doing the porting work20:32
cjwatsonI'm quite annoyed by that20:32
dbarthbarry: only webbrowser-app conflicts afaict20:32
barrydbarth: yep, that's it20:32
cjwatsoncamako: given that I was looking ahead to the entirely plausible future involving arm64 phones20:32
camakocjwatson, I see the good intention on your part. Yeah arm64 is pretty close..20:33
cjwatsonslangasek: ok, I can certainly see that those would need to be adjusted; though ideally we might come up with some hack that uses mir if it exists in the archive for a given architecture and not if it doesn't ...20:34
cjwatsonit's pretty terrible to have to go around hardcoding this20:34
cjwatsonSharedLibraryProber, huh?  That test doesn't sound difficult to fix from a porter box20:35
slangasek"From a porter box" - but we don't have one of those today20:36
camakocjwatson, someone is already testing a fix as we speak... that's not the point... It's that we would have to commit the fix and rebuild in a sync silo..20:36
camakowe are doing it in sbuild/emulator20:36
cjwatsoncamako: wouldn't have to sync this to rtm just yet20:36
camakothis was an rtm->utopic sync, so rtm was in proposed20:36
cjwatsoncamako: and I'm afraid I don't see the horribleness of having to upload a fix :)20:36
cjwatsoncamako: so we upload a newer version to utopic20:37
cjwatsonthat is not a big deal20:37
camakocjwatson, that woulda caused a fork on our side which we don't wanna do... mir is changing quite a bit daily20:37
cjwatsonit's not a fork, you're just running utopic a little ahead20:37
cjwatsonI'm sorry but nobody had a problem with this kind of thing before citrain!20:38
camakoplus, since this was a sync silo I don't even know that was possible20:38
cjwatsonall you'd be doing is taking an extra revision on top20:38
cjwatsonyou've already given up the silo20:38
cjwatsonany synciness of the previous silo is no longer relevant20:38
camakocjwatson, so the mir in rtm-proposed can still be promoted?20:39
cjwatsonall we need to do is to get something into utopic that has the new package names20:39
cjwatsonbuild ubuntu-touch-meta20:39
cjwatsonsync it20:39
cjwatsonit is fine if it's a bit ahead of rtm20:39
camakocjwatson, that's what we are gonna do then20:39
cjwatsonslangasek: we had am1 and am2 for ages; not proper porter boxes but often usable as such.  are they perma-dead?20:40
cjwatsondbarth: those builds in rtm silo 2 are looking better20:41
cjwatsondbarth: just give me a shout when you finish with that silo so that I can put it back in its canonical configuration20:41
camakocjwatson, what if someone else builds against mir in rtm silo (like qtmir)? won't they be picking up the rtm-proposed qtmir?20:42
cjwatsoncamako: we can do the same thing for them that I just did for dbarth20:42
camakokgunn ^^20:43
cjwatsonPPAs have a config option for whether they build against -proposed or not20:43
dbarthcjwatson: hopefully yes; alex-abreu is going to test them next this evening; will ping back tomorrow20:43
cjwatsonsilos have it on by default because otherwise library transitions are impossible, but we can switch it off on request20:43
cjwatsoncamako: ok, so I've remembered how to get at real arm64 hardware if you need it20:44
cjwatsoncamako: send me a patch and I can possibly test it faster20:44
Ursinhasergiusens: so the part of citrain that watches the ppa and returns the build script isn't really considering the sources you specified, I wonder if that ever worked without failing20:45
camakocjwatson, there are other things in the silo though (qtmir, u-s-c, papi).. I am just not sure if this won't cause problems..20:45
cjwatsoncamako: they will build against the PPA itself20:45
Ursinhasergiusens: I mean, if that ever worked when there was a package failed to build in the ppa20:45
cjwatsonthat's basically always wanted20:45
camakoI mean in the rtm-proposed..20:45
cjwatsoncamako: I'm sorry but you're going to have to make this concern rather more concrete for me before I can understand it20:46
alex-abreubarry, could you help reconfi silo rtm 009 ?20:46
barryalex-abreu: sure20:47
camakocjwatson, I have 4 packages in rtm-proposed... and I need to get those 4 on a utopic silo... and then land them on utopic... before rtm can be promoted.. In the meantime others may be landing things on those projects.20:47
cjwatsoncamako: they'll build in other silos20:47
cjwatsoncamako: oh you mean inter-silo conflicts in ubuntu?20:48
cjwatsoncamako: we'll just have to get this done first and everyone else will have to rebuild; I don't see a way around that20:48
camakocjwatson, ok we''ll get a utopic silo with a fix and no rtm sync silo this time... and then build and land and then rtm-propsed can get unblocked20:49
cjwatsonsurely this is the inevitable consequence of failing to lock the components for ubuntu first :)20:49
cjwatsoncamako: do let me know if you need me to test this branch.  is it lp:~kdub/mir/fix-1379478 ?20:50
alex-abreubarry, oh I think I managed to do it myself20:50
cjwatsonit's possible sbuild/qemu won't be up to the job20:50
alex-abreuI Haz The power20:50
camakocjwatson will do... lemme check20:50
cjwatsonI have to go for some family time now though20:50
cjwatsonback in an hour or two20:50
camakocjwatson, yep that's it20:51
camakocjwatson, thanks for your insight20:51
Ursinhasergiusens: robru says you should be able to publish even if the build job fails..20:55
robrusergiusens: just need to set ignore-step20:55
Ursinhasergiusens: that's a bug that got exposed by a recent refactoring we're making, should be easy to fix it making the script consider only the requested packages.. while it's not there just ignore_step and carry on21:01
camakocjwatson, this is the branch... You were right, it's failing for us on sbuild/emulator. Could you give it a try please? ---> lp:~kdub/mir/fix-137947821:08
slangasekcjwatson: am1/am2 aren't perma-dead... one of them is in transit to become porter-arm64, the other is still available but horribly manual in its management.  "First get yourself VPN credentials, then talk to this guy in hyperscale" doesn't scale, hyper or otherwise, and I definitely don't think the mir team should be blocked on this21:14
slangasekcjwatson: (but if there's already a fix in flight now, then ignore me)21:15
bfillerbarry: need a silo for line 91 when you can21:16
barrybfiller: ^^ :)21:16
bfilleryou rock21:16
slangasekcamako, cjwatson: grabbing lp:~kdub/mir/fix-1379478 to am221:18
balloonsfginther, will you be able to fix the xserver issue on core apps jenkins today? That calc mp needs to land21:24
fgintherballoons, ack, I'll try to fix it now21:28
cjwatsonslangasek: are you building it now?  I just got back and my chroot's upgraded now21:48
slangasekcjwatson: I'm happy to let you take it from there if you have an up-to-date chroot21:48
cjwatsonI agree we need a porter box, obviously :-/21:48
cjwatson(or better, virt builders)21:49
cjwatsonit's a dirty chroot but it should do the job21:50
loolubuntu-qa, hey, I'm wondering whether you'd have an ETA for testing of rtm landing-005?21:57
ToyKeeperlool: There's a good chance it'll at least get started in the next 8 hours or so, but it's currently #3 in the queue and I'm mostly alone during this time zone.  If things go wrong with the other two, it might take longer (or could go faster).21:59
loolToyKeeper: so ETA for QA pass is at best in my morning then21:59
loolToyKeeper: so I should get to bed and look at the results tomorrow, thanks  :)22:00
* lool waves22:00
ToyKeeperlool: Does it include links/info about the crashes it fixes, and about installing the custom tarball?  At a glance, those seem like the most likely hangups.22:02
ToyKeeperlool: Also, any idea if the trust-store packaging issue is likely to affect OTA updates?  If so, it probably shouldn't land without the packaging fix.22:05
cjwatsoncamako,slangasek: ok, building now22:06
loolToyKeeper: yes22:06
loolToyKeeper: packaging issue wont affect OTA upgrades22:07
loolToyKeeper: only image builds22:07
loolor manual upgrades22:07
veebersbarry: ping, how are you? I'm looking to get autopilot release with a critical fix (<-- balloons)22:12
veeberscihelp; perhaps I should ask you? ^^22:19
Ursinhaveebers: maybe trainguards?22:19
veebersUrsinha: ah right, cheers /me should read the topic better :-)22:21
veeberstrainguards: same question :-) ^^22:21
barryveebers: oops, was getting some dinner.  what can i help you with?22:40
veebershi barry, actually sorry false alarm on my part. Looks like I don't need to release right now :-)22:41
barryveebers: okay!  i'll be here for about another 30m22:41
veebersbarry: ack thanks, sorry for the false alarm22:43
cjwatsoncamako,kgunn,slangasek: that branch builds cleanly on am2 (I also commented on the MP)23:35

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!