/srv/irclogs.ubuntu.com/2014/06/24/#ubuntu-ci-eng.txt

bzoltan1hello zsombi05:29
=== bzoltan1 is now known as bzoltan
zsombibzoltan: hai05:29
bzoltanzsombi:  have you heard anything from elopio or kalikiana about the AP failures I linked yesterday?05:30
zsombibzoltan: nopez05:30
bzoltanzsombi:  it would be cool to get back the 1-2 days release cycle ... but it seems to be impossible05:31
zsombibzoltan: well... and this time I haven't seen any UITK related failures... but aing tot anything confirmed...05:34
elopiobzoltan: I'm sorry, today I was stuck with apps05:39
elopioand tomorrow I'll be on holidays.05:39
elopioI can help on wednesday.05:39
bzoltanelopio:  for me that silo16 with this failures http://pastebin.ubuntu.com/7690500/ seem to be tottaly safe05:49
kalikianabzoltan: I struggled to repro as my phone discharges faster than it can charge07:19
kalikianaas soon as I do so much as enable wireless :-(07:19
sil2100bregma: hi! Once you're around: I have some minor nitpicks about the packaging changes of libgrip in your silo07:59
sil2100ogra_: hey! I would need a core-dev packaging ACK for some of the main package in the blank powerd policy changes silo08:03
ogra_sil2100, why, isnt that landing from rsalveti ?08:04
sil2100ogra_: yeah, but he's not the author of the commits - you think he reviewed all the branches?08:04
sil2100He's just one of the landers08:05
ogra_if he took care of the silo i would expect so ... but let me take a look08:05
sil2100So I don't have certainty that he was the one reviewing08:05
sil2100ogra_: anyway, diffs: https://ci-train.ubuntu.com/job/landing-020-2-publish/lastSuccessfulBuild/artifact/packaging_changes_powerd_0.16+14.10.20140620-0ubuntu1.diff , https://ci-train.ubuntu.com/job/landing-020-2-publish/lastSuccessfulBuild/artifact/packaging_changes_indicator-power_12.10.6+14.10.20140620.1-0ubuntu1.diff08:05
sil2100The universe components had small changes, recommends additions and etc. which I +1'ed08:06
sil2100These look safish as well I guess08:06
ogra_sil2100, looks fine to me, ACK08:08
sil2100\o/08:08
sil2100ogra_: thanks08:08
ogra_sil2100, hmm, btw ... powerd = universe08:09
sil2100Oh, powerd as well?08:09
ogra_you could have acked yourself ;)08:09
sil2100I actually only checked indicator-power and assumed powerd is the same ;)08:09
sil2100Packages with power should be in main, as main has power08:09
ogra_haha08:10
seb128sil2100, ogra_: -1 for indicator-power08:12
ogra_seb128, is it in desktop ?08:13
seb128unity-system-compositor and powerd are in universe and not on all architectures08:13
seb128indicator-power is used on desktop and in main08:13
ogra_dang, we need to get rid of that desktop stuff :P08:13
ogra_sil2100, right, cant do that08:14
sil2100:|08:15
sil2100No worries08:15
sil2100seb128: thanks!08:15
ogra_yeah, i would have forgotten about that08:16
ogra_i guess it wants to become a suggests ... on the phone both packages are seeded anyway08:16
seb128ogra_, sil2100: how can you ack stuff like that? you for sure should know for sure that main can't build-depends on universe08:16
ogra_seb128, its not a build dep08:17
seb128depends sorry08:17
seb128binaries in main can't depends on binaries in universe08:17
seb128but for sure you know that?08:17
ogra_yes08:17
sil2100Yeah... sorry for that, I only took a look at the two other components that were universe-related08:18
sil2100i.e. unity-system-compositor and media-hub changes08:18
Laneysil2100: We've just been talking about this, I'll do one to move those to suggests08:34
Laneyi-power handles the case when they're not present08:34
seb128it's also slightly disturbing that this mp is being landed while not approved yet08:37
seb128rsalveti, kgunn ^ shouldn't the mp be top approved before being put up for landing?08:38
Laneyokay I proposed https://code.launchpad.net/~laney/indicator-power/depends-to-suggests/+merge/224246, please add that if approved08:43
thostr_could anybody configure silo 7 (I cannot as we added a new component)08:43
jibelon http://ci.ubuntu.com/smokeng/utopic/touch/mako/94:20140623:20140530/8685/gallery_app/ why are some tests listed several times? For example test_camera_button_visible appears 3 times08:48
jibelah, nm, it's because the dashboard only shows the name of the test, not the full name with the testsuite08:50
sil2100thostr_: sure08:52
Laney(I added it myself)08:54
jibelbrendand, could you look why TestPhotosView.test_camera_button_visible passed while it's impossible to reveal the toolbar?08:55
jibelbrendand, I think the test should wait until the toolbar autohides, then reveal it and continue.08:56
brendandjibel, probably, yes08:56
brendandsil2100, my morning is packed, so i'll have answers on those failures sometime around lunch08:57
jibelbrendand, gallery app tests should be almost completely red.08:58
brendandjibel, well if that was the test method then yes they would be i guess08:59
brendandjibel, it's only because the test sometimes catches it when it's auto-revealed that any pass09:00
=== vila changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: vila | CI Train Status: #87 promoted | CI Train Sheriff: barry, robru | Known issues: The spreadsheet is extremely slow, http://people.canonical.com/~rbpark/citrain/ knows the statuses before the spreadsheet does.
sil2100brendand: sure :)09:03
sil2100thostr_: reconfigured - when you have some CI train business it's best to say 'trainguards', as all CI Train people will get a ping then ;)09:05
thostr_sil2100: thanks and good to know09:06
sil2100bzoltan: hey! Any possibility we'll have the new UITK sometime soon? The silo is already waiting for a really long time ;)09:06
bzoltansil2100:  the silo16 should be about a day old.09:07
bzoltansil2100:  the previous one landed as far as I know.09:07
sil2100bzoltan: uh, I don't think it landed, we still get the UITK failure as before which was supposed to be fixed with the UITK landing09:08
sil2100Let me check the commit logs09:08
sil2100bzoltan: hm, you might be right, I guess it got landed during my holidays09:09
sil2100Strange that we still get that failure then09:09
sil2100Maybe it's a different one then09:09
sil2100bzoltan: ok, ignore my doubts, it seems it's a new failure... we'll fill in a bug an poke you later ;)09:11
sil2100Sorry for the confusion09:11
sil2100brendand, ogra_: so, it seems we have a new UITK failure09:11
ogra_huh ?09:11
ogra_oh, true !09:12
ogra_woah09:13
ogra_OSError: [Errno 8] Exec format error09:13
ogra_that looks like it tries to exec x86 binaries or some such09:13
t1mpsil2100: this one? https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/133216209:21
ubot5Ubuntu bug 1332162 in Ubuntu UI Toolkit "test_get_unity_top_container failed on mako#89" [Undecided,In progress]09:21
ogra_yeah, looks like it09:23
sil2100Yeah09:33
Laneyfeel free to reconfigure/rebuild silo 20 now, indicator-power's fix got approved09:37
Laneyand the original mp too09:37
alan_gvila: can you help? "cp: error writing 'debian/mir-test-tools//usr/bin/mir_unit_tests': No space left on device" - https://jenkins.qa.ubuntu.com/job/generic-mediumtests-builder-utopic-armhf/1964/console09:41
sil2100Laney: thanks!09:41
Laneynp09:42
vilaalan_g: urgh09:44
vilaalan_g: let me look09:44
vilaalan_g: 400MB only for /tmp that's probably where things break, I'll need retoaded to remaster all cyclops nodes, can you reproduce locally to estimate how much you need ?09:58
alan_gvila: mo...09:59
alan_gvila: it's probably an overestimate (as not all are shipped), but the executables and libraries in my local build add up to 450Mb10:01
vilaalan_g: ack, I'll need to check with fginther and retoaded if bumping the tmpfs to 512MB is reasonable. I'm worried though, those nodes are configured to run up to 2 jobs at the same time so this may not be enough anyway. You may want to investigate if/when you started consuming that much space ?10:05
tvosssil2100, ping10:07
alan_gvila: better estimate (still an upper bound): 327M10:07
vilaalan_g: hold on, I read the wrong line it seems, it's not 400MB, it's 2GB already10:08
* alan_g denies using all that10:09
vilaalan_g: right, it may be more involved than it looks, those 2GB may be shared across several uses10:11
vilaalan_g: rebuild triggered at http://s-jenkins.ubuntu-ci:8080/job/generic-mediumtests-builder-utopic-armhf/1970/console10:11
vilaalan_g: it went on a different node, let see if we can reproduce there10:12
alan_gvila: ack10:12
vilaalan_g: pfew, previous run took ~2h ? Does that match your expectations ?10:13
alan_gvila: sadly, yes10:14
alan_gIf folks must insist on building on feeble kit they could at least use cccache10:17
=== vila changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #87 promoted | CI Train Sheriff: barry, robru | Known issues: The spreadsheet is extremely slow, http://people.canonical.com/~rbpark/citrain/ knows the statuses before the spreadsheet does.
=== psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: psivaa | CI Train Status: #87 promoted | CI Train Sheriff: barry, robru | Known issues: The spreadsheet is extremely slow, http://people.canonical.com/~rbpark/citrain/ knows the statuses before the spreadsheet does.
cjwatsonOur primary builders tend not to benefit much from ccache because they build far too many different things on too many different nodes; I suspect similar is true for Jenkins-based builds10:21
cjwatsonMaybe not to quite the same extent10:22
alan_gcjwatson: I know there are scaling issues (although there are probably solutions). But it can be frustrating waiting five hours to autoland something that just built in CI.10:27
sil2100mandel: hi! Looking at your u-d-m landing now - did you make sure no one uses the common.h include?10:47
=== MacSlow is now known as MacSlow|lunch
mandelsil2100, yes, no one does11:11
mandelsil2100, 100% sure since it is a not exposed header11:11
mandelsil2100, nad I recompiled a couple of project to make sure11:11
sil2100mandel: ok, thanks :)11:14
* sil2100 tries to get his system back to an usable state11:22
=== pete-woods is now known as pete-woods-lunch
=== cprov changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cprov | CI Train Status: #87 promoted | CI Train Sheriff: barry, robru | Known issues: The spreadsheet is extremely slow, http://people.canonical.com/~rbpark/citrain/ knows the statuses before the spreadsheet does.
=== MacSlow|lunch is now known as MacSlow
sil2100ogra_: as most Tuesdays I might not make it for todays evening meeting due to practice12:04
sil2100So could you lead it if I wouldn't be around?12:04
=== alan_g is now known as alan_g|lunch
ogra_sil2100, sure12:11
sergiusensfginther: sil2100 hey guys, gatox is building the first pure click package we ever saw;12:11
sergiusensci is completely busted with this scenario12:12
sergiusensfginther: can you make https://code.launchpad.net/~diegosarmentero/pay-ui/pay-backend/+merge/223642 just build clicks and not debs?12:12
sil2100;)12:14
sil2100sergiusens: ok, that's good to know...12:15
gatoxthis one is the latest: https://code.launchpad.net/~diegosarmentero/pay-ui/pay-backend/+merge/22419612:15
bregmasil2100, I'm back on the internets again, what was your concern with my libgrip packaging?12:17
sil2100bregma: hi! So, first of all most of the concerns are really minor packaging things but would like to get those fixed before publishing: first of all, you removed some comments and trailing commas12:24
sil2100bregma: the other thing is also that there were build dependencies changed but not mentioned in the changelog12:25
sil2100bregma: same for the removal of python-grip binary package - this should be mentioned in the changelog (i.e. in the respective commit message) as otherwise we will not know easily when it has disappeared12:26
bregmasil2100, I'm not aware of any build dependency changes, I simply did a wrap-and-sort so I could more easily diff against the Debian packaging (ci-train is boken when it comes to working as a downstream)12:29
bregmabut I can update the changelog to me more clear about deprecating the python- package12:29
ricmmsil2100: hey, could I get a silo for line 27 ?12:30
sil2100ricmm: sure, am having lunch right now12:35
ricmmalright12:36
seb128ricmm, hey!12:37
seb128ricmm, we need you, see -touch, the qtubuntu-sensors made unity8 desktop unhappy12:38
Chipacagah. where's the new ci-train spreadsheet? I've only got links to the old one12:40
cjwatsonhttps://wiki.ubuntu.com/citrain12:46
Chipacacjwatson: meta-thanks12:47
fginthersergiusens, I have work for that in progress.12:48
sergiusensfginther: I setup something to sync on a hangout for later today12:49
fginthersergiusens, thanks12:49
sergiusensfginther: of interest would be to be able to build fats12:51
sergiusens:-)12:51
sergiusensit's winter here, so fat is good :-P12:51
fginthersergiusens, :-)12:52
=== renato_ is now known as Guest77133
=== barry changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cprov | CI Train Status: #87 promoted | CI Train Sheriff: robru | Known issues: The spreadsheet is extremely slow, http://people.canonical.com/~rbpark/citrain/ knows the statuses before the spreadsheet does.
=== alan_g|lunch is now known as alan_g
tvosssil2100, around?13:06
sil2100tvoss: sure13:06
bregmasil2100, just letting you know I've updated my libgrip d/changelog, I'm going to rebuild silo 006 to pick it up13:07
Chipacahiya peeps. Could I have a silo for row 28 please?13:08
ogra_davmor2, wow ... i know what you meant yesterday with the google logo ... the first boot on 95 takes several centuries ...13:09
ogra_i wonder why13:09
davmor2ogra_: :)13:09
davmor2ogra_: the bit after the google logo took about the same amount of time13:09
davmor2ogra_: It was just the waiting for the google logo to go that took forever13:10
ogra_davmor2, the second boot is fine ... i assume the apparmor profile generation on first boot got slower13:11
ogra_stopwatching the second boot i get 10-12sec with the google logo and 11-13 for the boot animation ... latest after 25 sec i have the UI on screen13:12
ogra_so i guess we can blame apparmor here13:12
davmor2ogra_: :)13:14
ogra_mterry, nice first boot wizard !13:15
mterryogra_, yay!13:15
davmor2mterry: not so nice if you have a different back drop though13:15
mterrydavmor2, backdrop?  You mean if you've changed the greeter wallpaper?13:16
davmor2mterry: Yes if you upgraded to the image and had change the greeter to one that is mostly black and white the text is really hard to see13:17
davmor2change to greeter wallpaper even13:17
mterrydavmor2, ah fair.  That's a temporary issue during upgrades though.  Most users will only see this the first time they boot13:17
ricmmsil2100: hey, any chance to get the silo for27 ?13:18
davmor2mterry: but your assumming that oem's won't change the backdrop though ;)13:18
mterrydavmor2, no, but if they do, they'll see the effect on the wizard13:18
davmor2true13:18
* jdstrand notes that server side generation of profiles on the default image should be landing this week13:18
jdstrand(as I'm told)13:19
sil2100ricmm: let me take a look, one moment13:19
ricmmthank you13:19
ogra_jdstrand, oh, cool !!13:19
kgunnsil2100: hey there, so we tested silo 20 & marked it "Yes" for tested so it would be released...i just checked this morning13:20
sil2100ricmm, tvoss: ok, so both of you have platform-api and qtubuntu-sensors13:20
kgunnand looks like someone marked it "no"13:20
kgunnany ideas?13:21
sil2100kgunn: yeah, so...13:21
sil2100kgunn: I wanted to publish that but then it was -1'ed for release13:21
ricmmsil2100: which line is tvoss'13:21
ricmm?13:21
tvossricmm, 1113:21
sil2100ricmm: silo 11, line 22 - it's a 'test silo', but tvoss mentioned it lanind this week13:21
Chipacarobru: does you being sheriff mean requests for silos go to you?13:21
sil2100kgunn: ok, let me continue my explaination13:21
* kgunn was being patient :)13:22
ricmmtvoss: do you mind letting me through? need to fix a crasher for unity8 on desktop13:22
tvossricmm, fine with me13:22
ogra_Chipaca, it means you can shoot him and make a song about it13:22
ogra_;)13:22
ricmmtvoss: my silo is ready to land as soon as someone helps me test13:22
ricmmtvoss: thanks13:22
ricmmsil2100: ^13:22
sil2100kgunn: so, during packaging ACKing we noticed that some main packages suddenly depended on universe packages13:22
sil2100kgunn: which is trouble13:22
sil2100kgunn: so Laney devised a fix, we reconfigured and rebuilt ;p13:23
sil2100ricmm: ACK13:23
ogra_kgunn, worse was that the MP wasnt top approved yet though ...13:23
ogra_(indicator-power)13:23
ogra_it is all sorted now ... but i guess you want to re-test13:23
sil2100ricmm: assigned!13:24
ogra_sil2100, CI should really refuse to land stuff if there is no top approval13:24
Chipacaogra_: https://www.youtube.com/watch?v=GCY_GKX09AE13:24
kgunnsil2100: ogra_ ok, will retest....and i'll follow up on the mp approval13:24
sil2100ogra_: hmmm... good idea!13:24
ogra_Chipaca, hah13:25
ricmmsil2100: thanks!13:26
sil2100ogra_: will work on that today I guess :)13:26
ricmmsil2100: back to good old silo 5 :)13:26
ogra_sil2100, ++13:26
Chipacasil2100: robru: I'm unsure who i'm supposed to ping to ask for a silo, but i'd like one for row 28, pretty please13:31
sil2100Chipaca: hi! Let me take a look13:31
Chipacasil2100: hi :)13:31
sil2100Chipaca: ah! Ok, so, if you want a silo you need to switch the 'Ready' field to Done13:31
sil2100Otherwise we don't consider a landing ;)13:31
sil2100So it could just sit there forever ;p13:31
Chipacasil2100: done!13:34
Chipacasil2100: I have to ask for it anyway, once it's ready? or does setting it to ready get me a silo automagically?13:34
sil2100Chipaca: we have to give a silo ourselves, but once it's set to ready we either see it ourselves when scouting the spreadsheet or just get pinged by the bot that someone added a ready landing13:35
sil2100So no need to poke, unless there's something important to mention ;)13:35
ChipacaI'll get the hang of it someday13:39
sil2100No worries!13:40
brendandsil2100, i can't reproduce either the weather or filemanager issue13:51
brendandsil2100, i'll file bugs for both of them to keep track13:51
rsalvetikgunn: ogra_: I can help landing 20 as well, not sure if everything got properly reviewed and top approved13:53
rsalvetibut good that it was tested by qa already13:53
ogra_rsalveti, its all fine now13:53
rsalvetiwell, we still need to land it :-)13:53
ogra_yep ... but the other issues are fixed13:54
rsalvetiseb128: it's fine to start a silo with mrs that are not yet top approved13:57
rsalvetiseb128: the only problem is landing such silo in that state13:57
seb128rsalveti, right13:57
seb128rsalveti, well, somebody asked for packaging review on that one, so I assume it was about to land13:58
seb128rsalveti, not to mention that it was adding universe depends to a package in main, and things we don't want on the desktop (like powerd and the system compositor)13:58
seb128rsalveti, anyway, was an easy one, the code handle those not being there, Laney demoted them to suggest, so should be all good ;-)13:59
sil2100brendand: ok, thanks!13:59
rsalvetiseb128: right, but it wasn't ready for landing yet13:59
rsalvetiseb128: the testing flag was set to yes14:00
rsalvetiand that's why I believe sil2100 tried to land it14:00
rsalvetibut not every mr was reviewed/approved yet14:00
seb128k14:00
rsalvetimaybe the issue was that the testing was set to done when the work wasn't really done14:00
seb128yeah14:00
seb128lander assume they can land stuff that are "tested: yes"14:00
seb128they take it as "ready to land"14:00
rsalvetiright14:00
sil2100Right, it was set to tested -> done, as kgunn said he tested it and switched that to yes14:00
rsalvetiright, that was the issue then14:01
sil2100I'm changing CI train to not allow (without an override) to build unapproved branches14:01
rsalvetiright14:02
sil2100bregma: oh my, the changelog looks soo sassy!14:06
=== pete-woods-lunch is now known as pete-woods
=== cprov changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: Ursinha | CI Train Status: #87 promoted | CI Train Sheriff: robru | Known issues: The spreadsheet is extremely slow, http://people.canonical.com/~rbpark/citrain/ knows the statuses before the spreadsheet does.
Chipacasil2100: sassy changelog? do share!14:17
* kgunn wonders if changelogs can be sassy/14:19
kgunnsil2100: can i get a silo for line 29 ? ....all the mp's are approved ;P14:20
sil2100kgunn: hehe ;) Sure, sorry, was inside some packaging work14:21
kgunni'm sorry about that mp slipping thru...14:22
kgunni think it might have been a late add....that was a rather dynamic list of mp's14:22
sil2100kgunn: remember that you have another unity-mir silo assigned for testing of the trusted sessions14:22
kgunnsil2100: yeah, that trusted sessions is only for testing right now...so14:24
tvosssil2100, can I get a silo for line 30?14:24
kgunnthey one i'm asking for is for landing14:24
sil2100tvoss: set it to Ready yes! :) And assigning14:25
davmor2sil2100: I think there is an issue with the osk and scopes on the latest flo I'm going to reboot and see what happens then15:00
sil2100davmor2: what seems to be the problem?15:11
davmor2sil2100: mterry: I think after a boot with the welcome screen the osk is screwed up a bit.  It doesn't appear properly till you reboot the device then it works fine.  I'll do a fresh install to confirm and grab some logs15:12
mterrydavmor2, hrm15:14
Saviqsil2100, hey, could we get a silo for line 4? I promise, we'll land it this time!15:14
mterrydavmor2, thought I tested that -- we should be killing maliit-server when done with wizard15:14
sil2100Saviq: !15:15
davmor2mterry: yeah that might be the issue it isn't coming back up :)15:15
sil2100Saviq: ok, but I already see some of the projects there are locked currently15:15
Saviqsil2100, I'll deal with that as needed15:16
sil2100mterry: shame on youuu! Killing things is a dirty workaround ;)15:16
mterrysil2100, maliit-server is tied to the current MIR_SOCKET server, and we'd be swapping it out on them15:17
sil2100Excuses!15:17
sil2100Saviq: ok, just make sure to coordinate15:18
Saviqsil2100, will do15:18
popeysil2100: dunno if you know this, but on #95 music app is missing and i can't bring up osk in the  app lens15:19
popeyi see davmor2 has confirmed this15:20
ogra_popey, ugh15:20
ogra_popey, we dropped mediascanner 1 last night15:20
popeyright, but music-app is a click15:20
ogra_music-app shouldnt use it anymore though15:21
popeyit doesnt15:21
ogra_phew15:21
davmor2ogra_: popey I see the music app15:21
* ogra_ isnt near his flo atm ... cant check15:21
popeyhm, i see it on my flo15:22
* popey reboots both makos15:23
davmor2popey: I see it on my mako15:23
ogra_we got a new apparmor ... probably it missed to re-create the profile ?15:23
popeyhmmm its on my other mako15:23
popeymaybe yes15:23
* popey reboots15:23
popeynope not showing15:23
* popey gets a cable15:23
sil2100Saviq: uh oh15:24
sil2100Saviq: ok, it took longer since there was an invalid MR in the MR list, fixed that and reassigned15:25
popeyphablet@ubuntu-phablet:~$ click list | grep music15:29
popeycom.ubuntu.music1.3.49615:29
popeyhmm15:29
popeyphablet@black-phablet:~$ click list | grep music15:30
popeyphablet@black-phablet:~$15:30
popeyyeah, it doesn't show up on my other device15:31
ogra_weird15:31
popeyit is in /opt/click.ubuntu.com/com.ubuntu.music tho15:31
popeyI'll uninstall it and see if i can install from store15:31
popeyoh, i cant can I ☻15:31
ogra_you should be able to uninstall from cmdline15:32
popeyhow? click doesn't think i have it15:32
ogra_oh, hmm15:32
ogra_did you search for it ?15:32
popeyyes15:32
ogra_it should offer it in the store if it really thinks that15:32
davmor2mterry: also phone settings on a tablet doesn't sound right for the disabling of error reporting :)15:34
* sil2100 prepares to drive to practice15:35
sil2100o/15:35
mterrydavmor2, that screen/text is going to be changed15:35
davmor2mterry: good to know :)15:36
davmor2mterry: okay I have a keyboard but it took nearly a minute to appear15:41
davmor2mterry: screen had dimmed so is that 45seconds15:41
mterrydavmor2, Bug marked Invalid, user is too impatient  ;)  -- I've marked a note down for that15:44
fginthersergiusens, this is the error I'm currently getting: http://paste.ubuntu.com/7695713/15:56
fginthersergiusens, missing package :-(15:56
sergiusensfginther: I think that's for xnox :-)15:56
xnoxhey.15:57
xnoxfginther: click from utopic is needed. utopic's version is compatible to install on previous releases (e.g. trusty)15:58
fgintherahh15:58
fgintherxnox, thanks15:58
xnoxfginther: and it has been copied from utopic into sdk ppa or some such.15:58
xnoxbzoltan: ^ where did you publish fixed click?15:58
brendandogra_, is there a reason we don't have two builds per day?15:58
sergiusensfginther: oh, click is update in the sdk ppa16:02
sergiusensxnox: should be the sdk ppa16:02
fginthersergiusens, ack16:02
sergiusensfginther: how are you calling click? I want to copy paste :-)16:03
fginthersergiusens, "sudo click chroot -aarmhf -fubuntu-sdk-14.10 create"16:05
Saviqsil2100, ugh, sorry :|16:12
robruChipaca, oops, sorry. I forgot to take myself off the Sheriff topic when I EOD'd last night16:16
robrustgraber, you around? it's your day to be sheriff16:16
stgraberrobru: I'm around, not in the call though due to the TB meeting and my lunch break both happening at the same time :)16:17
robrustgraber, ok, no worries16:18
ogra_we didnt have much to discuss in the call anyway ... you didnt miss anything16:19
=== robru changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: Ursinha | CI Train Status: #87 promoted | CI Train Sheriff: stgraber | Known issues: The spreadsheet is extremely slow, http://people.canonical.com/~rbpark/citrain/ knows the statuses before the spreadsheet does.
=== Ursinha changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #87 promoted | CI Train Sheriff: stgraber | Known issues: The spreadsheet is extremely slow, http://people.canonical.com/~rbpark/citrain/ knows the statuses before the spreadsheet does.
robrustgraber, can you check the packaging in silo 6? big diff there https://ci-train.ubuntu.com/job/landing-006-2-publish/28/artifact/packaging_changes_libgrip_0.3.8+14.10.20140624-0ubuntu1.diff16:25
stgraberrobru: I should be able to look at this in about an hour16:27
robrustgraber, alright, thanks16:28
=== fginther changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: fginther | CI Train Status: #87 promoted | CI Train Sheriff: stgraber | Known issues: The spreadsheet is extremely slow, http://people.canonical.com/~rbpark/citrain/ knows the statuses before the spreadsheet does.
bzoltanxnox: in the SDK PPA16:39
tvosssil2100, silo13 is good to go16:43
robrustgraber, ^16:45
stgraberrobru: sure, will look once I'm back from meetings and lunch.16:46
robrustgraber, thanks16:47
ricmmseb128: hey did you test the silo?16:58
ricmmseb128: because I dont see it crashing, but its aborting somewhere in Mir for me17:02
=== alan_g is now known as alan_g|EOD
ricmmseb128: I no longer see it crashing but its failing to connect to the mir server instance... not sure what could be a cause for that17:24
Saviqrobru, while you're around, seen bug #1333184 ?17:28
ubot5bug 1333184 in phablet-tools (Ubuntu) "`citrain host-upgrade` removes the PPA after installation" [Undecided,New] https://launchpad.net/bugs/133318417:28
robruSaviq, yeah, I put that in on purpose originally, didn't realize it broke ppa-purge. not sure, ppa-purge is weird, sometimes it can remove the ppa and sometimes it can't. haven't figured it out yet17:38
robruSaviq, although I guess it's just one line to drop from citrain tool to stop deleting the ppas after installation17:38
stgraberseb128: I'll assign you a silo for that indicator-network landing, however note that in the future you can also just get one yourselves (as coredevs have the needed Jenkins ACL now)17:50
stgraber*yourself17:50
=== gatox is now known as gatox_lunch
Saviqrobru, it will never be able to remove a ppa that it has no deb line for17:59
Saviqrobru, because it needs to find out which packages are there to be able to know to backport them17:59
robruSaviq, maybe I'm confused but that code was working for me at the time that I wrote it ;-)17:59
Saviqrobru, it could probably read that from dpkg db or something, but obviously it doesn't :)18:00
robruSaviq, yeah, but you tell it what ppa you want to remove, i thought it could query that ppa even if it wasn't currently enabled18:00
Saviqrobru, right, well, it doesn't :)18:00
=== fginther changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #87 promoted | CI Train Sheriff: stgraber | Known issues: The spreadsheet is extremely slow, http://people.canonical.com/~rbpark/citrain/ knows the statuses before the spreadsheet does.
robruSaviq, https://code.launchpad.net/~robru/phablet-tools/dont-delete-silos/+merge/224340 if you want to review18:13
robrusergiusens also if you're around ^18:13
sergiusensrobru: I'm around18:14
=== gatox_lunch is now known as gatox
* sil2100 goes to prepare the e-mail18:38
sil2100ogra_: anyway, I think we can get back to our previous approach of building 2 images a day18:58
ogra_sil2100, yeah18:58
ogra_no issue with that18:59
sil2100ogra_: so, I have a family house-work emergency tomorrow, so I have to drive to my parents place and help out finishing some wall-painting, so sadly I'll be most of the time in and out ;/19:02
sil2100ogra_: could I ask you one last time to help out and take the lead of the meetings for me?19:02
sil2100I promise it'll be the last day like this ;)19:02
sil2100I'll be around on IRC when resting inbetween house-work19:03
Saviqrobru, can you please recon silo 4? I added dialer-app (yes, we know there's a bunch of conflicts, I'll coordinate)19:05
robruSaviq, ok19:06
Saviqrobru, thanks19:09
robruSaviq, you're welcome!19:38
seb128ricmm, sorry, it was not built and then I was away for a while, trying in a bit19:59
seb128stgraber, hey, thanks, I know I can technically assign silos, I just though the CI team was still supposed to do it because they have a better view of the current image status and know if things should flow in or be on hold for a bit20:00
stgraberseb128: nah, so long as we're in regular landings mode, there's no problem with coredevs just doing everything themselves20:06
seb128stgraber, where did you get that? I saw no communication on that20:12
seb128stgraber, even the fact that coredev can assign silo was not communicated, Laney and I learnt it earlier this week by lurking on this channel where you or somebody mentioned it20:13
stgraberseb128: it was one thing we discussed with slangasek and robru when barry and I went through the landing team training20:14
stgraberseb128: basically the landing team is now under foundation and so we're changing a couple of small bits to the process here and there to get things go a bit smoother20:14
slangasekwell20:14
seb128if that's true, could that be communicated out of the foundation team?20:15
slangasekI think it becomes a problem if all coredevs start claiming silos without coordination20:15
seb128right20:15
slangasekI don't think it was ever said that coredevs should just claim their own silos20:15
stgrabertrue, but you need to be more than coredev to have the necessary rights20:15
seb128which is why I was assuming the default was to let the CI lander do the "orchestration"20:15
stgraberyou need coredev+spreadsheet edit rights20:15
seb128well, quite a bunch of us have that20:15
seb128which leads to the same issue20:15
stgraberslangasek: robru did say during that call that he didn't see any problem with coredevs just assigning their own silos20:16
seb128until we run out of available silo20:16
barryright.  if there are not enough silos, then you just have to wait20:16
slangasekstgraber: right, and it's fine that he thinks that, but it's not something I had any intention of socializing more broadly because silos are a limited resource :)20:16
seb128if we do that we should have a proper and documented workflow20:16
stgraberslangasek: sure, which is why I haven't sent an e-mail about it and instead just told people who'd benefit most from it and are known to be reasonable :)20:17
barryseb128: the best we have right now is the FAQ: https://wiki.ubuntu.com/citrain/FAQ20:17
barrywhich of course doesn't cover this particular issue :/20:17
seb128stgraber, well, that was discussed a few times on public channel, it's becoming public knowledge, being announced or not20:18
seb128but since it's not officially documented and has not been announced, it means everyone is just doing guess work20:18
barrythere are a few things that only uber-devs can do (overriding some silo constraints, iirc).  not exactly sure which team controls that though20:18
stgraberbarry: coredev20:18
stgraberbarry: you and I aren't in any special team and we have all the rights we need for landing, so all the Jenkins jobs are now accessible by ubuntu-core-dev20:19
barrystgraber: i thought there were still a few things that core devs couldn't self-service20:19
stgraberbarry: no, there are a couple things landers can't self-service20:19
stgraberbarry: but landers who are also core-dev can self-service everthing20:19
barryalrighty then ;)20:20
stgraberbarry: a lander can edit the spreadsheet, can trigger a build and can do a limited reconfigure (doesn't add packages). Coredev gets you assignment, full reconfigure and publishing on top of that20:20
ricmmseb128: nvm, I found another issue, dealijg with it20:21
seb128ricmm, k20:21
seb128ricmm, I was just installing it ;-)20:22
ricmm:)20:22
robrustgraber, barry, slangasek, seb128: sorry guys I was in a meeting. yes of course if all core devs are constantly assigning silos, that's chaos, and there are a very small number of silos. but on the other hand, since core devs already have the ability to upload direct to ubuntu, it doesn't make much sense to me for them to have to ask for permission to get a silo, that's just slow and inefficient. so I would generally ask core devs20:26
robruto just be reasonable about assigning silos to themselves, don't be greedy if you already have a couple, please don't do SRUs with citrain because those take forever, etc. if you think you just have a small landing that you're going to build & test in a couple hours, go ahead, i don't mind20:26
seb128k20:30
ogra_sil2100, sure, no worries20:44
Chipacarobru: i still don't know what a sheriff is in this context :)22:25
=== stgraber changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | CI Train Status: #87 promoted | CI Train Sheriff: - | Known issues: The spreadsheet is extremely slow, http://people.canonical.com/~rbpark/citrain/ knows the statuses before the spreadsheet does.
robruChipaca, sheriff is the guy you call for help when your train is being hijacked ;-)22:34
robruor something like that. the Sheriff is the guy assigned to help people use the CI Train effectively22:35
Chipacarobru: for ordinary stuff, or for extraordinary stuff?22:35
robruChipaca, both. like if you need a silo assigned, or you're not sure why your build failed, or whatever. if ci train is broke, call the sheriff22:36
Chipacarobru: ah, ok22:36
Chipacarobru: thanks :)22:36
robruChipaca, you're welcome!22:36
ricmmrobru: hey, I made a mistake23:14
robruricmm, what's up?23:14
ricmmaccidentaly tried to build something in silo 3 instead of 5, silo 3 was already checking for propagation23:14
ricmmnow its in an error state23:15
ricmmhorrible misclick, sorry23:15
robruricmm, so silo 3 was already published?23:15
ricmmlooked like it23:15
ricmmnow the msg is an error because it tried to build a pkg not in the silo list23:15
robruricmm, hmmm, doesn't seem so? the publish job on silo 3 hasn't been ran since jun 12th...23:16
robruricmm, oh I see, but the build job before yours was also jun 12th, that's an SRU thats just been sitting for a while23:16
ricmmso my silo is 005, I accidentaly tried to build my pkg in 003 through the jenkins interface23:17
ricmmso what do we do?23:17
ricmmcan it still run merge and clean once the SRU hits release?23:17
ricmmor is it borked23:17
robruricmm, well just do your build in silo 5 as normal23:17
robruricmm, ehhh, I just hit publish in silo 3, lets see what happens... worst case it creates a new sync request for the same package.23:18
ricmmyup, my silo is fine, was just worried that I had damaged silo 323:18
ricmmalright, sorry about that anyways23:18
robruricmm, no worries, thanks for letting me know. should be good now23:18
ricmmkk awesome23:19

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