/srv/irclogs.ubuntu.com/2016/04/20/#ubuntu-ci-eng.txt

=== chihchun_afk is now known as chihchun
=== chihchun is now known as chihchun_afk
Mirvrenatu: still there? did you see questions from allan on silos 064 and 039?05:16
Mirvrenatu: "Is a new calendar app required to see this fix? I'm finding that events (e.g. a breakfast appointment) no longer appear in day view to verify."05:17
=== chihchun_afk is now known as chihchun
kozatrainguards, who could help in understanding/resolving a strange issue with silo 51?07:16
robrukoza: what's the issue? Looks fine to me07:18
kozarobru, it segfaults when installed on the device [latest image] however when compiled on device [using chroot] works fine. Could it be some kind of clash opf gcc versions [on chroot is gcc version 4.9.2 (Ubuntu/Linaro 4.9.2-10ubuntu13)] or mismatch in libs?07:20
robrukoza: oh i have no idea about that. You should talk to the branch author or somebody who knows about the project in question. I just help if the ticket itself has an issue07:21
kozarobru, I see, thanks07:23
robruYou're welcome07:23
Mirvkoza: also 4.9.2-10ubuntu13 was used for the PPA builds as seen in the build logs07:32
Mirvkoza: vivid + stable-overlay don't have toolchain variations, so I can't think of too many things that could be different in PPA builders or on device07:32
Mirvkoza: did you compile with for example 'debuild' on device or more like make / make install? using the packaging via debuild might bring some different compilation options compared to you running compilation manually07:33
Mirvkoza: you can also install gdb and debug symbols on the device to try to get backtrace, although I'm not sure how qtubuntu-media/media-hub should be started in debug mode07:34
kozaMirv, so we have the same gcc version07:34
kozado not know how it was compiled on chroot as jhodapp did it however will check once he is online07:35
Mirvkoza: yeah you'll probably need jhodapp to help in debugging that07:36
kozaMirv, thanks for extra info. we will take it from here and will see how it goes07:38
om26erpopey, Hi!11:02
om26erpopey, I need to land latest dekko, who can I request to create a silo ? I am volunteering to test it.11:03
popeyom26er: it's already in a silo11:12
popeyom26er: https://trello.com/c/3u8N2Xw8/3077-1280-dekko-popey11:12
om26erpopey, great, one question though. how much effort/work will it be to land this change in that silo ? https://git.launchpad.net/~om26er/+git/dekko/commit/?id=81da994204079a620b04372c0be9e38697f1793811:13
om26erJust 4 lines and it will unblock me completely11:13
popeyask Dan11:13
popeytesting has already started so it might have to wait for the next release11:13
jibelom26er, rvr is already testing it11:14
om26erjibel, popey, ok. this current silo has quite a few changes that I wanted for my tests. I will pursue another release once this lands then.11:16
Saviqtrainguards, I just abandoned two silos and still can't assign any, says no silos available - that true?12:00
MirvSaviq: does seem incorrect, there should be 19 free12:04
MirvSaviq: might be a problem with the train then12:04
SaviqMirv, https://ci-train.ubuntu.com/job/prepare-silo/12:04
MirvSaviq: yeah I'm getting the same12:04
Saviqhttps://requests.ci-train.ubuntu.com/#/50012:05
Mirvunless sil2100 knows of any magic knobs we need to wait for robru. I remember in the past there was another situation like this, and back then even freeing up yet another silo did not help anything.12:05
Saviqoh well https://requests.ci-train.ubuntu.com/static/error.gif12:05
Mirvwe can stare at that12:05
* Saviq runs around waving frantically12:05
* Saviq has a feeling robru is our SPOF 12:07
jhodappkoza, Mirv I compiled it on device with "cd build; qmake ..; make -j3" and then copied the resulting .so file into the appropriate place under /usr12:08
sil2100hmmm12:30
* sil2100 takes a look at that12:31
sil2100This will take a bit as I'm no longer up-to-date with the train code12:32
sil2100I htink I see one possible issue12:34
sil2100uuuu, looks like latest change in bileto broke it12:44
sil2100Mirv, Saviq: it looks like the reason this does not work is because robru removed the 'distribution' dropdown from bileto12:47
=== _salem is now known as salem_
sil2100Mirv, Saviq: so now it's not really possible to set the target distribution to 'ubuntu', it's left as '' by default12:47
sil2100Mirv, Saviq: which makes CI Train think there are no silos available for this dest, as it doesn't know silos for the '' distribution12:47
sil2100In other words:12:48
=== sil2100 changed the topic of #ubuntu-ci-eng to: Train trouble? ping trainguards | CI problems? Use JenkaaS: http://bit.ly/jenkins-docs | Train: http://bit.ly/1hGZsfS | QA Signoffs: http://bit.ly/1qMAKYd | Known issues: silo assignment currently broken
sil2100I'll try to work-around it somehow12:48
Saviqack12:48
sil2100I say 'work-around' because I do not know what plans robru had with removing the distribution field12:49
sil2100Saviq: ok, so I assigned your silo by hacking around the javascript - let me now try to get that into production12:56
Saviqsil2100, ack, thanks12:57
robrusil2100: oh god I'm so sorry13:02
sil2100robru: I have a workaround (just re-adding the distribution field) but not sure if that's what you planned having ;)13:03
sil2100btw. wow, isn't it like, super still-dark-outside morning at your place?13:04
robrusil2100: up early instead of up late13:04
robrusil2100: you could have reverted the latest commit and rolled that out13:04
sil2100robru: yeah, well, I just made a 1 line diff for now, can I push it to lp:bileto or you prefer to fix it more properly? I wouldn't want you to work when you have a free day ;)13:06
sil2100(or a revert, if that's safe to do)13:06
robrusil2100: just push it to trunk, it's my fault, once I'm more awake (in some hours) I'll fix it better13:07
robrusil2100: glad you figured it out13:07
sil2100robru: ok! Yeah, the workaround should just work for now, go back to sleep or get some coffee ;)13:09
robrusil2100: once it's on trunk just get webops to run a configger as per the wiki, should be smooth sailing13:09
robrusil2100: thanks yeah, I'll go back to sleep ;-)13:09
sil2100robru, Mirv, Saviq: the 'fix' will be deployed by webops in the nearest moments13:20
Mirvsil2100: thanks a lot!13:36
=== fginther` is now known as fginther
sil2100Mirv, Saviq: fix deployed! Please be sure to edit your requests and set the distribution field13:42
=== sil2100 changed the topic of #ubuntu-ci-eng to: Train trouble? ping trainguards | CI problems? Use JenkaaS: http://bit.ly/jenkins-docs | Train: http://bit.ly/1hGZsfS | QA Signoffs: http://bit.ly/1qMAKYd | Known issues: if you have issues assigning silos, edit request and re-set the distribution field
sil2100I suppose CI Train should just default to 'ubuntu' if distribution is '', but yeah, robru will decide on the final fix13:44
Saviqack13:53
Saviqrobru, hey, I just realized... what are you using to push to lp:~ci-train-bot/ branches?15:18
robruSaviq: the train is self hosting but I often just push to trunk if it's a simple fix15:19
Saviqrobru, I meant to the project branches15:20
* Saviq has a feeling that leaves borked tags when it --overwrites15:20
Saviqbecause the train tagged the previous version, pushed that to LP and then overwrites when it gets rebuilt15:21
Saviqso the tags remain on the LP branch forever...15:21
robruSaviq: oh that's possible15:21
Saviqgotta love bzr15:22
robruSaviq: so what are you wanting? dangling tags to be cleared?15:22
robruSaviq: yeah it just tags the release commit and then 'bzr push lp:~ci-train-bot/project/.... --overwrite'15:23
Saviqrobru, by now - not really, since everyone has them already ;)15:23
* Saviq almost gave up on bzr tags15:23
robruSaviq: what are you trying to use tags for and how is it not working? eg if you're looking at version numbers in debian/changelog those should all correspond to bzr tags (at least in xenial, the vivid half of a dual silo wouldn't)15:24
robruSaviq: also it should be easy to ignore dangling tags eg if you're trying to parse the output of 'bzr tags' because it just lists the tag without any revid.15:24
Saviqrobru, sure, /me just dies a little every time I see them :P15:25
robruSaviq: write a script to delete them yourself ;-)15:25
Saviqrobru, http://people.canonical.com/~msawicz/unity8/15:25
Saviqcheck out the date :P15:25
robruSaviq: so this was a problem 1.5 years ago and you're only just telling me now? :-P15:26
Saviqrobru, no, back then it was us inheriting lp:unity tags15:26
Saviqrobru, because we were hosting at lp:unity/8.015:27
robruah15:27
robruSaviq: file a bug I guess but it'll be quite some time until I get around to it, I'm off for the rest of the month15:27
Saviqrobru, and we *almost just* got rid of them, but every now and again someone pops up with an old checkout in an MP and EVERYTHING has them again15:28
Saviqrobru, yeah, I don't care any more really... looking forward to git ;P15:28
robruSaviq: yeah me too, once the parallelization/ephemeral PPA work is done it should be easy to add git support.15:28
Saviqrobru, any reason why you didn't just land inline gles bits? ;)15:29
Saviqcan we just sneak them in under the train? managing any silo while those are not landed is just meh15:29
robruSaviq: what do you mean? you want me to push my branches to trunks?15:29
Saviqrobru, yeah ;P15:29
robruSaviq: because it was the last couple days before OTA10 was released and I didn't want to invalidate any silos by having unbuilt trunk commits in case there was a silo already in QA or something.15:30
robruSaviq: are they not all landed yet? the branches should be in every silo15:30
Saviqrobru, yeah, problem arises as soon as any of the branches touches debian/control15:30
Saviqthen you have to rebase on that15:30
Saviqrobru, </complaining>, I'll manage15:31
robruSaviq: right. so I made a silo with my own branches but it never landed...15:31
robruSaviq: this is the future you chose, you have to rebase the patch every time you touch control file anyway ;-)15:32
Saviqrobru, that's fine when it's in trunk15:32
Saviqbut until then it's meh15:32
Saviqrobru, really, our fault, I'll manage15:33
robruSaviq: https://requests.ci-train.ubuntu.com/#/ticket/1221 buh I forgot to signoff after the most recent rebuild. want me to submit it for QA?15:33
robruSaviq: I hadn't anticipated that so many qtmir/qtubuntu silos would just sit around for so long, I assumed you guys were actually landing silos with some frequency.15:34
Saviqrobru, we are, except when there's OTAs, Ubuntu freezes, *things*15:34
Saviqrobru, no, we've got another silo with this already - you can abandon, really15:35
robruSaviq: ok will do15:35
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
Saviqrobru, hmm, do you know what's with https://ci-train.ubuntu.com/job/ubuntu-landing-069-0-status/7179/console ? did the packages fail to upload, or do you think it's just waiting?17:27
robruSaviq: how long has it been since you ran the build?17:29
Saviqrobru, https://ci-train.ubuntu.com/job/ubuntu-landing-069-1-build/32/ ½h17:31
Saviqand they're still not there17:31
robruSaviq: Hmmmmmmm yeah that's pushing it, they should appear in just a few minutes17:32
Saviqrobru, ok, will get back to you if they don't17:32
Saviqor well, will try another build maybe17:32
robruSaviq: looks like you have one running already17:33
Saviqrobru, different pkg17:33
robruAh17:33
robruSaviq: yeah you should ping Colin if the packages aren't appearing in the PPA, he can dig up the logs17:34
Saviqrobru, kk17:34
=== chihchun is now known as chihchun_afk
salem_jibel, hi, we have a fix for bug 1571094 on silo 55, but looks like it's marked is failed because of a problem with unity8 tests.17:54
ubot5`bug 1571094 in Canonical System Image "/usr/bin/phone-gsettings-migration.py:ValueError:/usr/bin/phone-gsettings-migration.py@27:__call__:call_blocking" [High,In progress] https://launchpad.net/bugs/157109417:54
salem_jibel, I think we had this problem before and you added the silo to the qa queue anyway. Could you do that again?17:55
=== dpm is now known as dpm-mostly-afk
=== blr_ is now known as blr
=== salem_ is now known as _salem

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