/srv/irclogs.ubuntu.com/2014/01/09/#ubuntu-ci-eng.txt

=== fginther changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
=== psivaa changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: psivaa | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
ogra_hmm, unity8 seems crashy in 11909:27
didrockspopey: coming?09:30
didrocksyeah, Saviq, mind having a look: http://ci.ubuntu.com/smokeng/trusty/touch/mako/119:20140109:20140107.1/5957/unity8-autopilot/ ?09:30
popeyya09:31
didrocksasac: FYI, as told before holidays, I don't want we rerun for flaky tests09:32
didrockseven if we point to the real links of failure, then, they are looking at the dashboard and "why warning? test rate are great"09:32
asacdidrocks: i dont think thats the right way to think about it09:33
asacdidrocks: we need to know whether something is a flaki test09:33
asacor not09:33
didrocksasac: well, that's to upstream to investigate09:33
asacwe dont know without checking if it succeeds09:33
didrocksnot us09:33
asacwe have to make the call09:33
asacif we have a regression09:33
asacor not09:33
didrocksyeah, and we can see that comparing mako and maguro09:34
asacif we know we have a flaki test, we should check if its still a flaki test09:34
didrocksyou are hiding information09:34
didrocksand that's why we have few progress09:34
didrocksso, I disagree with that approach09:34
didrockshence reverting to the previous policy09:34
asacdidrocks: its not the reason why we have few progress09:34
didrocksit's part of the reason09:34
asacdidrocks: you can stop promoting09:34
asacthats the reason'09:34
didrocksanyway, in meeting now09:34
Saviqdidrocks, it's 100%, have I missed something?09:34
asacbut people are on it09:34
didrocksSaviq: look at the crash09:35
ogra_Saviq, .crash files09:35
Saviqdidrocks, ah09:35
asacdidrocks: what is clearly wrong is to promote because there is a test that we saw somehow failing in a probably similar manner09:35
didrocksasac: we can stop promoting until we are reliably at 100% then09:35
didrocksasac: but you have to explain that to the management chain09:36
asacdidrocks: but our rule is that we dont promote images that have regressions09:36
* didrocks sigh09:36
asacso if a test was flaki09:36
ogra_Saviq, 4 out of the 5 crashers with 119 are unity8 (not sure they are all the same) http://ci.ubuntu.com/smokeng/trusty/touch/09:36
asacwe can release with that flaki09:36
didrocksyou will take care of that then09:36
didrocksI won't09:36
didrocksand you will make the list09:36
didrocksand push people then09:36
asacdidrocks: we have psivaa an plars giving us the list daily09:36
didrocksasac: yeah, and people ignores it09:36
didrocksasac: and I already have a list09:37
didrocksso it's all confusing09:37
Saviqogra_, will have a look, thanks09:37
didrocksyou introduced confusion then09:37
asacand i am pushing yes. but i increase pressure/priority continuously09:37
asacdidrocks: if you say they ignore i will talk to them09:37
asacdidrocks: you stated in your summary that folks are looking09:37
didrocksasac: yeah, see how much feedback/progress09:37
asacdidrocks: so for flaki tests i want to give them time. for test that hard fail i will create a massive firedrill09:38
asaci dont want to do that priority for flaki tests... those should be prioritized with diligently increasing priority.09:39
didrocksasac: it's been weeks…09:39
asacwe have made progress09:39
didrocksso you either take care of that yourself09:39
asacwe do it step by step09:39
didrocksor you follow my rule09:39
didrocksasac: I'm quite unhappy that you changed the rule and you force it over me09:40
didrockswhile I'm still having to do the push09:41
didrocksso either I'm control and I continue09:41
didrockseither you want to force you rules, but in that case, you handle it09:41
didrocksseems fair to me09:41
didrocksplars: psivaa: ok, seems no answer, so please, stop rerunning09:45
didrocks(apart if we have infra issues, of course)09:45
psivaadidrocks: asac: ack09:46
Saviqdidrocks, ogra_, would it be possible that those .crash files would get uploaded to errors.u.c?09:46
didrocksSaviq: I guess that's a question for ev ^09:47
didrocksSaviq: keep us posted on this crash, it can be linked to latest Mir and seems to happen quite often (so potentially blocking promotion)09:49
Saviqdidrocks, the one in unity8 suite doesn't retrace09:51
Saviqdidrocks, checking out the other ones09:51
didrocksok09:51
Saviqdidrocks, the one in http://ci.ubuntu.com/smokeng/trusty/touch/mako/119:20140109:20140107.1/5957/default/ is:09:53
Saviqterminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::runtime_error> >'09:53
Saviq  what():  could not activate surface with eglMakeCurrent09:53
ogra_Saviq, what didrocks said .... ev-country09:53
Saviqusually happens when screen goes blank - bug #123652509:53
ubot5bug 1236525 in unity-mir "unity8 killed/crash then restart can result in mir unable "could not unblank display"" [Medium,Triaged] https://launchpad.net/bugs/123652509:53
ogra_yeah09:53
Saviqor at least it did until now09:53
ogra_the boost msg definitely rings a bell09:54
didrocksSaviq: ok, keep us posted if there is no new crash for you (that you can retrace)09:54
didrocksogra_: can you dogfood a little bit maguro?09:54
ogra_didrocks, my maguro is currently hacked quite a bit for swap issue tracking09:54
ogra_davmor2_ should get up soon09:55
didrocksogra_: ok ;)09:55
asacdidrocks: its all good and its your call as long as you always know if a test being red is a NEW regression or not. i am sure you undersatnd my way of thinking, so its a matter of taste on how to use the dashboard to do promotion and escalation decisionms09:58
evdidrocks, Saviq: this one? https://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-unity8-autopilot/111/artifact/clientlogs/_usr_bin_unity8.32011.crash/*view*/09:58
asacdidrocks: when you were gone people couldnt say for sure anymore if we just landed a very awful regression side effect09:58
asacor if its a flaki test like we saw before ... hence i required the hard empirical data09:59
asaci find it a bit sad that folks dont prioritize because the dashboard is green, but maybe you are right09:59
evif you look at the stacktrace, it's pointing at a corrupt stack. I suspect the retracers won't be able to do any better :)09:59
asachowever on the maguro once i was continuously increasing priority09:59
asacones09:59
asacbut since i sent the first mail beginning of this week, i thought it was reasonable to not expect big fixes by yesterday ... i planned to talk to folks again today about their cases10:00
alan_gpsivaa: we're seeing CI failures (e.g. https://jenkins.qa.ubuntu.com/job/mir-mediumtests-runner-mako/227/consoleFull) that appear to be the test hardware in a "wrong" state (c.f. bug 1239955). Is there anything you can do to reset it?10:00
didrocksasac: now I'm back, so yeah, I'm tracking all issues. Before promoting, I'm checking again my last (with stack) ;)10:00
ubot5bug 1239955 in Mir "integration-tests hang/fail in AndroidGPUDisplay.gpu_display_ok_with_gles when the display is asleep: what(): error posting with fb device" [Medium,Triaged] https://launchpad.net/bugs/123995510:00
didrocksasac: I understand why you wanted to do that, but I still think that showing issues clearly on the front page is a preferable way of putting social pressure10:00
psivaaalan_g: let me see10:01
didrocksasac: yeah, btw, we have a confirmation that what I was answering to Nicholas yesterday is right: 2 flaky maguro failures showed for the first time on mako today10:01
didrocksasac: so, we really need to clean the maguro as well10:01
asacdidrocks: yeah. well, i thought about it and i really believe we want to somehow do both: a) retry and b) visualize flakit tests in orange10:02
asacbut i dont want to put that organ for flaki test on the CI team10:02
asacso lets continue as you say10:02
asacdidrocks: i think we should shift from "clean maguro" to "clean emulator" :)10:02
asacbut not today10:02
didrocksasac: do you think the emulator is so slower that maguro?10:02
asacdidrocks: yes. it will reveal those timing issues even better10:03
didrocksthan*10:03
asacdidrocks: xnox sent around how to do that10:03
didrocksyeah, making sense10:03
asacdidrocks: at least we can tell people that say they dont have a maguro that they should see if it works on emulator10:03
asacand if not debug there10:03
Saviqev, ok, I'm not really asking about this particular one10:03
didrocksasac: +100 :)10:03
evSaviq: ah, context please :)10:03
asacxnox: is it super easy to run APs on the emulator locally?10:03
asacxnox: did your mail include instructions?10:03
Saviqev, I just wonder if it would  be possible to upload stuff from the test runs automagically to errors.u.c?10:04
evyes - the problem at the moment though is that we don't have armhf retracers. I've asked bdmurray to pick up the work on that (https://rt.admin.canonical.com//Ticket/Display.html?id=58019)10:04
psivaaalan_g: if you mean to reboot the device, i think the job does that already before running the tests.10:11
psivaaalan_g: also when you run the job for the second time, it's not guaranteed that the job will pick up the same mako10:11
psivaaalan_g: in any case, i've rebooted that particular device. so if you'd like to give it a go10:12
alan_gpsivaa: we've seen it several times today - not sure if it was all on the same device. Will give it a go.10:13
psivaaalan_g: just checked the other failed builds and they are in different devices. so it may not be the hardware that's at fault10:17
alan_gpsivaa: thanks. Do you know of any change? E.g. is there a image today?10:18
psivaaalan_g: yes todays tests are using trusty-proposed 11910:18
alan_gpsivaa: I'll try that locally. Maybe we have a new failure mode. Thanks for your help.10:19
psivaaalan_g: yw :)10:20
asacdidrocks: barry mentioned that system-image has debian/ dir outside their trunk? did they even use CI before?10:24
didrocksasac: no, they never used it10:24
asacright10:24
asacwow ... i got flooded with old email today :/10:30
Saviqdidrocks, no new crashes that I could retrace10:30
didrocksSaviq: ok, great! :)10:31
Saviqdidrocks, two of them were the eglMakeCurrent thing, which actually sounds concerning if powerd-cli holds the display on10:31
didrocksok, let's see what results popey and davmor2_ will get on dogfooding :)10:33
popeydidrocks: 119 is good here10:35
didrocksgreat ;)10:38
alan_gpsivaa: trying it locally I find that the test fails intermittently unless I first stop unity8 ("sudo -u phablet -i stop unity8"). Does the test initialization do this?10:56
psivaaalan_g: let me check10:57
psivaaalan_g: i see this:10:58
psivaainfinity: Turning on the display10:58
psivaainfinity: stopping unity810:58
psivaaunity8 stop/waiting10:58
alan_gpsivaa: Oh well, it was a nice theory10:59
psivaa:)11:00
=== davmor2_ is now known as davmor2
Mirvpsivaa/cihelp: "Could not resolve 'archive.ubuntu.com'" on autopilot-nvidia11:36
Mirvhttp://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty-daily_release/label=autopilot-nvidia/ all of today's11:37
psivaaMirv: i'll take a look11:37
Mirvdidrocks: packaging ack http://q-jenkins.ubuntu-ci:8080/view/cu2d/view/Head/view/Apps/job/cu2d-apps-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_gallery-app_0.0.67+14.04.20140108.2-0ubuntu1.diff11:38
didrocksMirv: +1 :)11:39
Mirvthanks, both :)11:39
psivaaMirv: strange. I was able to resolve archive.ubuntu.com from the command line. but i have now rebooted the machine.12:05
psivaaMirv: would you like to try it again please12:05
didrocksdavmor2: hey, awaken? ;)12:35
davmor2didrocks: what's up?12:36
davmor2didrocks: haptic on 119 is weird12:36
didrocksdavmor2: just to tell that we want to promote 119, so if you can test it throughfully :)12:37
didrocksdavmor2: for haptic, you can ping tvoss :)12:37
davmor2didrocks: currently fresh installing to get rid of the swap off from yesterday12:37
didrocksok ;)12:38
=== cjohnston changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cjohnston | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
cjohnstonMirv: did you retry whatever failed to reach archive.ubuntu.com?13:06
=== alan_g is now known as alan_g|lunch
asaccjwatson: would we have enough builders to enable arm64 and ppc64el in daily-build ppa? if not, do we have plans to expand the pool of builders on those archs?13:20
asacanything i can do?13:20
Mirvpsivaa: cjohnston: hi, trying now13:20
psivaaMirv: ack, thanks13:21
cjwatsonasac: infinity would be best to answer that.  For arm64 the answer is probably still no; there simply isn't enough hardware in existence, and we're expanding as fast as our partner/sponsor can manage.  For ppc64el maybe, it's a bit easier to spin up more VMs there13:21
asaccjwatson: from what i understand we wouldnt use them much as most packages we carea bout are dep-wait, but it would help us reduce time to archive if we had everything that can be build already build before copying things to proposed.13:21
cjwatsonasac: With Qt 5.2 most packages you care about will be fixed, I suspect13:22
cjwatsonasac: Since v8 goes away13:22
asachmm. guess that might increase importance of this topic even further13:22
asacthanks. will talk to infinity13:22
cjwatson(Plus various random dh-autoreconf conversions and the like, but nothing else major AFAIK)13:22
Mirvpsivaa: this happened after your reboot: http://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty-daily_release/1069/label=autopilot-nvidia/console13:29
Mirvie 20 minutes ago UTC time13:29
psivaacjohnston: would you mind taking on this please ^?13:30
cjohnstonlooking13:34
cjohnstonis appears to still be having issues getting to archive.ubuntu.com13:37
cjohnstonbeyond that, if psivaa doesn't have any ideas, we will have to wait for fginther13:38
cjohnstonMirv: ^13:39
psivaacjohnston: strangely enough archive.ubuntu.com resolves OK from that machine. so i am at a loss13:39
cjwatsonLooking at performance in the test rebuild, ppc64el might be safe enough to enable now, maybe.  Though of course some of that is just because failures are on average quicker than successes13:43
fginthermorning13:49
fginthercjohnston, psivaa looking13:49
=== dobey_ is now known as dobey
=== alan_g|lunch is now known as alan_g
davmor2didrocks: 119 is looking pretty good I don't see any issues that weren't there before which I think popey can confirm on mako too14:19
popeyalready did14:19
popeyits groovy14:19
didrocksexcellent14:19
didrockslet's promote it then :)14:20
didrocksogra_: when you read this ^14:20
* ogra_ sees issues ... that darn thing vibrates every time i start an app :P14:22
ogra_didrocks, will do :)14:22
didrocksogra_: open a bug! :)14:23
didrocks"can you please break haptic feedback?"14:23
ogra_heh14:23
popeydidrocks: can we please get https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1240505 qtorganiser5-eds fix from renato in landing asks?14:45
ubot5Ubuntu bug 1240505 in Ubuntu Calendar App "There is no way to delete an event" [Critical,In progress]14:45
didrockspopey: sure, can you file it? I see that calender-app change is not merge yet though14:47
popeyok14:48
cyphermoxdidrocks: webbrowser looks good to me14:58
cyphermoxMirv: have you tested webbrowser too?14:59
didrockscyphermox: it wasn't on the landing ask, did upstream tell you finally to release it?14:59
didrocks(so to answer, I think Mirv didn't test it)14:59
cyphermoxno, you never mentioned upstream asking to release it :)14:59
cyphermoxwell, anyway, looks fine to me atm, we'll just wait then15:00
popeydidrocks: will add after calendar dev has tested further.15:03
didrockspopey: ok ;)15:03
didrockscyphermox: that's what I told yesterday in the meeting, that upstream may add it :)15:04
cyphermoxI misheard then15:04
didrockscyphermox: I think continuing cleaning the prepare job will be of value (in case they are not all good)15:05
cyphermoxI'm going to need more context, my head is full of bluez state right now15:08
didrockscyphermox: what we discussed yesterday, some prepare job in cu2d were yellow because of some direct uploads to distro during the holidays15:08
cyphermoxright15:11
* cyphermox takes bamf15:12
didrocksboumf! ;)15:14
ogra_do you eat, smoke or sniff it ?15:15
cyphermoxomg, YUCK.15:15
* ogra_ grins15:15
cyphermoxhttps://launchpad.net/ubuntu/+source/bamf/0.5.1+14.04.20131125-0ubuntu215:15
cyphermoxno, yuck this ^15:15
* ogra_ only takes aspirine at times 15:15
ogra_heh, lovely15:16
cyphermoxhttps://code.launchpad.net/~mathieu-tl/bamf/14.04.20131125-0ubuntu2/+merge/20102515:22
cyphermoxdidrocks: ^15:22
didrockscyphermox: yeah, seems some people aren't wanting to play nicely! This diff is so easier though! Thanks :)15:23
cyphermoxthe old diff had unapplied stuff in it..15:24
didrockscyphermox: yeah, I saw that *sigh* :(15:25
cyphermoxbrb15:28
kenvandinecyphermox, didrocks: i had merges for all the direct uploads, most have merged15:33
didrockskenvandine: excellent! so if we rerun, we should have no yellow prepare anymore?15:34
kenvandinehttps://code.launchpad.net/~ken-vandine/bamf/0.5.1+14.04.20131125-0ubuntu2/+merge/20072315:34
kenvandinebamf is failing15:34
didrocksah, I guess cyphermox had a bamf merge as well15:35
* didrocks reboots15:35
didrocksbrb15:35
kenvandinedidrocks, cyphermox: my branch has a fix to the gcov.m4 file that fixes a FTBFS, but tests still fail15:37
kenvandineseveral of the packages needed updates to that15:37
didrockskenvandine: the other works, but only bamf doesnt'?15:37
kenvandinebamf is the only one not merged yet15:37
kenvandineyeah15:37
kenvandinewell15:38
kenvandineit fixed the build15:38
kenvandinebut now tests fail :)15:38
didrockskenvandine: ah, can you get bregma on board? :)15:38
kenvandinebregma, ^^15:38
kenvandinehttps://code.launchpad.net/~ken-vandine/bamf/0.5.1+14.04.20131125-0ubuntu2/+merge/20072315:39
dobeydidrocks: replied on https://code.launchpad.net/~dobey/cupstream2distro/native-versions/+merge/20073615:39
didrocksdobey: ok, just be aware that if someone bumps the version in your native project with removing the +, you will end up in a broken situion15:41
dobeydidrocks: yeah, but i can a) needs-fixing on reviews that have that, and b) yell at people that commit it as such anyway :)15:42
didrocksdobey: I'm happy with this. I would prefer put that into production in my morning if possible, do you mind? (I can push and it should be safe, but not sure if anyone else will get issues meanwhile, who will debug it)15:44
dobeydidrocks: i'd like to get it merged/deployed asap, so i can start using it15:46
ogra_=== image 119 promoted to trusty ===15:46
dobeydidrocks: i know our TZ difference sucks in that regard though15:46
didrocksogra_: thanks!15:46
popeywoop woop15:46
didrocksdobey: yeah, I prefer to be safe than sorry :)15:46
dobeydidrocks: you are not the only one who can deploy it into jenkins are you?15:47
didrocksdobey: no, but I'm the only one really knowing the code15:47
=== alan_g is now known as alan_g|tea
dobeydidrocks: well, the code isn't that hard to understand. i think we can debug it if there is a problem :)15:48
didrocksdobey: I still prefer to be safe. I'm happy to compromise on native vs non native and not handling the automatic fallback for native when the version is wrong. I don't want to put production at risk though :)15:49
=== gatox is now known as gatox_lunch
dobeydidrocks: if you've already made up your mind about not merging/deploying it today, why ask if i mind?15:51
didrocksdobey: just trying to assess if there is a real need of urgency to put production at risk for it15:51
didrockslike you have some uploads that are critical for today that can't wait15:52
dobeywell, we need to get a release of ubuntu-purchase-service built, and a unity-scope-click that depends on it. wanted to have it done 2 days ago, but i wasn't aware that changes were made to the u-p-s trunk without review at the time, or that these native versions just flat out didn't work. :-/15:53
didrockswell, it's a choice as well to want to keep native versions, you blocked on it (contrary to than 200+ projects we have)15:54
didrocksanyway, no need to loose time in that debate again15:55
dobeydidrocks: right, but from our previous chat about it, it seemed as if it would work as expected. i wasn't aware that it didn't (if i'd known 2 months ago it didn't work, i would have made this branch then)15:56
dobeybut there's nothing we can do about that 2 months ago :)15:56
didrocksnot sure to understand your point, you knew that we had requirements like split, we chatted about it 2 months ago :)15:56
dobeyguidelines. yes we chatted about it, and the implication that native was OK, and that it worked15:57
didrocksnot really what I remember from the discussion15:58
fgintherMirv, autopilot-nvidia should be working now16:00
sergiusensdidrocks, https://code.launchpad.net/~fginther/cupstream2distro-config/add-usensord-and-goget/+merge/20093216:00
dobeydidrocks: anyway, can we merge/deploy it today, or no?16:01
sergiusensdidrocks, daily release is not enabled since it would need someone to review16:01
didrocksdobey: not today, as told above (and in meetings now until EOD)16:01
didrockssergiusens: ok, will have someone reviewing that16:01
fginthersergiusens, sorry about not merging that through, I'll get that in now16:03
=== greyback is now known as greyback|away
=== cjohnston changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: doanac | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
=== alan_g|tea is now known as alan_g
sergiusensfginther, ah, I thought you were waiting for a reviewer; I was just side pinging didrocks to get the daily release stuff setup as well :-)16:06
cyphermoxkenvandine: I don't see your merges for libdbusmenu and libindicator, did you have one for those?16:49
kenvandinecyphermox, i didn't do those... i don't recall seeing them as yellow16:50
cyphermoxugh, my connection is being pretty unreliable right now16:50
kenvandinemaybe i missed that stack :)16:50
cyphermoxkenvandine: they seem to be here16:50
kenvandinecyphermox, of course... the network guy has networking problems :)16:50
cyphermoxalright, starting with those now, if the interwebs will let me :)16:50
cyphermoxkenvandine: hehe16:50
cyphermoxcould be because I hack at stuff and change my network config16:51
kenvandinei only seem to have network problems when i do google hangouts :)16:51
cyphermoxhehe16:51
kenvandinehangouts hate me... but pretty reliable when i keep video disabled16:51
cyphermoxyeah, just before a hangout all hell breaks loose16:51
cyphermoxyeah16:51
=== gatox_lunch is now known as gatox
didrockskenvandine: cyphermox: coming? :p17:03
=== greyback|away is now known as greyback
robrusergiusens, http://paste.ubuntu.com/6721951/ what should be done with these files from goget-ubuntu-touch?17:36
robrusergiusens, should I create an -examples package for them? or delete them?17:37
cyphermoxkenvandine: robru: https://code.launchpad.net/~mathieu-tl/libdbusmenu/12.10.3+14.04.20131125-0ubuntu2/+merge/20105217:41
kenvandinecyphermox, done17:42
cyphermoxta, yay!17:42
robrukenvandine, cyphermox https://code.launchpad.net/~robru/goget-ubuntu-touch/packaging/+merge/20105017:45
kenvandinecyphermox, mind reviewing that for robru?17:46
cyphermoxI am17:46
kenvandinemy head is deep in the hub atm17:46
cyphermoxhey, could we not fix dh_golang to not do that?17:46
kenvandinethx17:46
cyphermoxrobru: ^ :)17:46
robrucyphermox, no idea, I've never seen dh_golang before17:46
robrucyphermox, might be possible but it's outside the scope of this merge17:47
cyphermoxyeah17:47
=== alan_g is now known as alan_g|EOD
=== plars changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: plars | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -
sergiusensrobru, can't we exclude them?18:35
sergiusensrobru, I'll talk to the maintainer of dh-golang18:35
sergiusenscyphermox, ^^18:36
sergiusensexactly it's the application source; it would need to exclude files if package name == main18:36
cyphermoxwhat ?18:41
sergiusenscyphermox, oh, in ref to reading the backlog and you saying: fix it in dh_golang ;-)18:41
cyphermoxsergiusens: well the right thing to do would be for dh_golang to ignore comments...18:42
cyphermoxthough I guess comments in debian/control aren't exactly kosher18:42
sergiusenscyphermox, I thought you were talking about http://paste.ubuntu.com/6721951/18:43
cyphermoxnah18:45
cyphermoxthose should jsut get rm'ed in debian/rules18:45
sergiusensfginther, hey, is the usensord goget branch deployed to jenkins?18:55
fginthersergiusens, it should be18:57
sergiusensfginther, right, just noticed it! Thanks18:58
sergiusensmight be builder overload18:58
=== josepht_ is now known as josepht
robrusergiusens, cyphermox yep i rm'd those in debian/rules already, but i just wanted sergiusens input to give him a chance to say 'no wait, we need to ship those in package x!'19:20
cjwatsoncyphermox: Comments in debian/control are explicitly permitted by other tools and by the policy manual19:22
cjwatsoncyphermox: http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-controlsyntax19:22
cyphermoxyes19:22
sergiusenscjwatson, I'll log a bug against dh-golang for that19:22
sergiusensrobru, and for that as well ;-)19:23
sergiusensrobru, usr/share/gocode is just for package building19:23
cyphermoxcjwatson: I wasn't saying that it's not permitted, just that it's not quite RFC 2822 or whatever, so people could have cut corners to parse the file19:25
sergiusensrobru, cyphermox how soon do we get daily release for usensord?20:34
cyphermoxlet's complete that now..20:34
cyphermoxwe basically just need to merge my changes (will push in a second) for cupstream2distro-config and set a bootstrap commit in changelog for both20:36
sergiusensChickenCutlass, ^20:47
ChickenCutlasssergiusens: great -- thanks20:47
sergiusensfginther, are there any trusty instances on jenkins that I could use?20:56
fginthersergiusens, there are vms21:00
cyphermoxrobru: kenvandine: https://code.launchpad.net/~mathieu-tl/usensord/bootstrap/+merge/20110121:03
cyphermox^ boostrap commit...21:04
sergiusensfginther, that's fine; are the rather clean?21:05
sergiusensfginther, like the saucy ones is clean enough21:05
fginthersergiusens, they are snapshotted21:05
fginthersergiusens, same setup as the saucy VMs you use for the click packaging21:05
sergiusensfginther, great, it's actually for that :-)21:06
kenvandinecyphermox, done21:14
kenvandineyay... bamf passed ci21:17
cyphermoxyay21:29
kenvandinecyphermox, did you see didrocks gave you ofono on the landing plan?21:46
cyphermoxoops, no I had not seen21:50
cyphermoxI'll take care of it tonight21:50
fginthers-jenkins will brought down in about 30 minutes to fsck a disk21:59
=== plars changed the topic of #ubuntu-ci-eng to: Ubuntu CI Engineering Team | Vanguard: cihelp | Landing instructions: http://paste.ubuntu.com/6292280/ | Known issues: -

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