/srv/irclogs.ubuntu.com/2015/12/16/#ubuntu-ci-eng.txt

michirobru: What does “diff missing” mean00:56
michi?00:56
robrumichi: it means the diffs are missing :-P00:57
michiNo kidding! :)00:57
michiWhat diffs? For what?00:58
michiI mean, all I did was hit “Build” after pushing a change.00:58
robrumichi: it's the diffs between what's in the silo and whats in distro.00:58
michiI didn’t see this previously, which is why I’m asking.00:58
michiSo, how does this happen?00:58
michiSorry, this is a bit of a black box to me.00:58
michiJust wondering whether I should worry.00:59
robrumichi: what's happening here is that there's a race condition in the script that updates the silo status. the build job deletes the diffs first then regenerates them at the end. the status update shouldn't be running when the build job is00:59
michiAha.00:59
michiOK, fair enough. I guess it means I can safely ignore that message then.00:59
robrubut the status updater started just before the build did, so it ran and was like "hey the diffs are gone'00:59
robrubut it's ok because the buld job will regenerate them later00:59
michiCool, thanks!00:59
robrumichi: you can ignore it for now. if you hadn't just started a build you'd have to worry about it00:59
michiOK, no prob, thanks!01:00
robrumichi: fixing that race condition is on my to-do list.01:00
robruyw01:00
michiBecause you have hardly anything to do at the moment… :(01:00
michiThanks again for your herculean effort yesterday!01:00
robruoh man, yeah, yesterday was nuts. every possible thing that could go wrong, did.01:14
michiYes, I got that impression.01:14
michiWell, all is well again. The train is ticking over very nicely, and it’s really easy to use.01:14
michiThanks for making a great tool. And one that was actually built with the needs of poor sods like myself in mind!01:15
robrumichi: oh, you like it? thanks. some days I'm like "man this is crap"01:15
robruI guess it beats the spreadsheet ;-)01:15
michiNo. I think this is a great example of how to get it right.01:15
michiI can throw a silo together in two minutes flat and it just works.01:15
michithat’s really nice.01:16
robruwow, cool01:16
michiAnd it’s easy to see what’s going on with the build, and upgrade the phone once things are done.01:16
michiI really like it.01:16
robruthanks dude, that's awesome01:16
michiMy pleasure!01:16
robrujust wait until we get rid of jenkins. then it'll be really streamlined! no more "assigning", you just click build and a PPA will be created automatically. I can't wait for that!01:17
robruthat's a few months out yet though, lots of prerequisites to clean up first01:17
michiWould love to have that.01:17
michiI’m a little concerned about the proposal for us to create our own Jenkins builds.01:17
michithe instructions are awfully complicated.01:17
michiAnd copying and pasting a large script around hundreds of times is probably not a good thing.01:18
robruoh yeah, I was really surprised by that01:18
michiI think if we need to look after our own Jenkins jobs, we’ll need something more like citrain.01:18
robruI was thinking s-jenkins would be around forever.01:18
michiWhere I can fill in a handful of fields and just press “Go".01:18
robrumichi: yeah I'm hoping to make the train faster & easier so you don't need s-jenkins at all01:18
michiWhat we would need is essentially what s-jenkins does for us now though.01:19
michiAutomatic build/test whenever I push a branch.01:19
robruhmmm, yeah auto build when a branch is pushed could be a bit trickier.01:19
michiIf there is a manual step involved (however small) after a push to get the testing happening, the testing won’t happen most of the time.01:19
michiThis is one strength of Jenkins.01:20
michiI just do an MP, and it gets built and tested automatically.01:20
michiI actually don’t mind Jenkins all that much.01:20
michiSure, the UI sucks.01:20
michiAnd when something goes wrong with one of the builders, it’s hell for us.01:20
michiBut, when Jenkins is working, it’s really nice to have.01:20
michiFrom where you sit, it’s an entirely different story, I’m sure.01:21
robrumichi: yeah, I didn't used to mind jenkins, but the longer I am stuck maintaining one the more flaws I find in it and the more powerless I am to do anything about those flaws. train can't continue being a wrapper around jenkins for much longer01:21
michiI believe you.01:21
michiBut, whatever the replacement, it has to be at least as automatic as Jenkins is now.01:21
michiOtherwise we’ll lose.01:21
robrumichi: I think we're talking about two different jenkinses ;-)01:22
michi?01:22
robruyou're talking about s-jenkins which does the auto-testing of your merges01:22
michiYes.01:22
michiOK, so you are using a different instance underneath the train?01:22
robruI'm talking about ci-train.ubuntu.com which is itself a jenkins, which I plan to get rid of and incorporate into bileto01:22
michiAh01:22
michiWell, I don’t really care how the train does its thing, as long as it keeps moving :)01:23
robruyeah, having the train do auto-rebuilds would be a new feature that we could look into doing, but that's separate from what I'm talking about with "replacing jenkins"01:23
michiRight01:23
robrumichi: but yeah, jenkins is holding us back in a lot of ways. for one it's preventing us from having unlimited silos. the main goal of getting rid of jenkins is to have unlimited silos. but it will also clean up a huge amount of smaller bugs that the train has hobbled through for years01:24
michiI didn’t know that it was Jenkins that limited the number of silos.01:25
robrumichi: well, indirectly so01:25
robrumichi: what happened was that the lp people made it possible for us to create ppas dynamically, which is amazing.01:26
robrumichi: but in jenkins we have 4 jobs per ppa("silo") and we don't have a great way of generating those dynamically. basically jenkins needs to be restarted in order to see when new jobs are made. there's kind of a way around that but it's not great and blah blah blah so we're kind of stuck with this.01:26
michiurgh01:27
robruso if we get rid of jenkins, we don't need to "create jenkins jobs" for every new silo, and we gain a ton of flexibility01:27
michiWell, from what I’ve heard, you wouldn’t be the only one to see it go.01:27
michionly one to be happy to see it go.01:28
robruheh, yeah01:28
michitrainguards: Sorry for this...01:47
michiWould it be possible to delete the s390x packages in silo 26 to stop them from getting published?01:47
michiAfter some deliberation, we decided to not try and make the builds/tests succeed for s390x.01:47
robrumichi: uh I'm not able to delete binaries, only sources01:49
michiAargh.01:49
robrumichi: if you're going to change something that prevents s390x from building you'll need to rebuild anyway.01:49
robrumichi: because if you just delete s390x, then all that happens is it'll be rebuilt in proposed01:50
michirobru: After talking with jamesh, he pointed out this: https://lists.launchpad.net/ubuntu-phone/msg17189.html01:50
michithe problem is that we can’t really test with s390x, except in a silo.01:50
jameshrobru: the package has never been built in proposed01:50
michiIf something breaks on us all of a sudden on that arch, we are toast.01:50
jameshrobru: michi had disabled some tests to get s390x to build in the silo, but we think it is better to leave things broken since it won't hide the problems should someone want to get this working on that platform01:51
robrujamesh: michi: right so just re-enable those tests, rebuild, make sure s390x is broken, then you're good to go01:52
michirobru: Cool, about to do that.01:52
jameshrobru: my fear was that there would still be an s390x binary package in the silo from the previous build with the tests disabled01:52
jameshrobru: or does that get ignored during publishing?01:53
robrujamesh: publishing only looks at the most recent silo contents01:53
jameshrobru: great.  That makes things easy01:53
robrujamesh: michi: thumbnailer does not have a s390x binary in xenial so publication will not block on that being failed.01:54
robruok, off to the gym, back in ~2 hours02:24
bzoltan_robru:  is thre a way to just merge the branch and not to release to Xenial? Or how big problem is if the package stucks in the proposed pocket if the next release comes in a day a or two?04:18
robrubzoltan_: yeah having stuff in proposed isn't horrible. you can't just include your s390x fix in the same silo?04:20
bzoltan_robru:  QA does not like rebuilds after QA validation04:33
bzoltan_robru:  but let me try that... maybe QA will not be badly pissed04:33
bzoltan_robru:  I pushed a single line change to the landing branch ... It will take some time to build all arches, but it will be fine after that.04:36
robrubzoltan_: oh I didn't realize it had qa already. ok well if it builds you can publish it after that04:43
bzoltan_robru:  All right then :)04:44
bzoltan_robru:  I will still need a jedi's ack on the debian/ changes I guess04:44
robruright04:45
bzoltan_robru:  all good, but I am not authorized to publish the ubuntu-themes package from that silo6005:42
bzoltan_ERROR Publish failed: bzoltan not authorized to upload ubuntu-themes05:42
Mirvbzoltan_: there's uitk packaging change too so needs coredev06:04
bzoltan_Mirv: Do we have any of the coredevs active in this time?06:16
Mirvbzoltan_: not really, sometimes I've pinged RAOF but sil2100 should be here in 2h or so06:33
Mirvand I'd have the uitk rights if the last meeting had been held, but alas it was not06:34
bzoltan_Mirv:  have you seen sil2100 aready?09:06
sil2100bzoltan_, Mirv: what's up?09:18
bzoltan_sil2100:  I would like to publish the silo60 UITK09:18
bzoltan_sil2100:  and it has debian/ space changes09:18
sil2100Let me look at it between promotion preparations09:19
Mirvbzoltan_: yep, soon there. and btw great that the s390x issue was solved (weird that the same trick that fixed other archs didn't work there)09:20
bzoltan_Mirv:  This fix is a permanent one at least It is a nice and clean landing... I see the chance to spin off one more UITK before the weekend09:21
sil2100Mirv, bzoltan_: looking at the packaging diff now, but we'll need to get an ubuntu archive member reviewing it as well09:22
bzoltan_sil2100:  for me the Overlay PPA and the merge are the most critical09:22
sil2100hmmm09:23
sil2100Mirv: do you remember if anyone of us got 1.3.1742+16.04.20151209-0ubuntu1 reviewed by an archive admin when we landed it overlay-only?09:24
sil2100seb128: hey! Sorry to bother you once again with binNEW reviews - we have 2 packages (the base and its -gles equivalent) adding two new binary packages each09:26
sil2100seb128: diffs here https://ci-train.ubuntu.com/job/ubuntu-landing-060-2-publish/3/artifact/ubuntu-ui-toolkit_xenial_packaging_changes.diff and https://ci-train.ubuntu.com/job/ubuntu-landing-060-2-publish/3/artifact/ubuntu-ui-toolkit-gles_xenial_packaging_changes.diff09:26
sil2100seb128: could you take a look and give us a sign if it's good to publish with the new binary packages?09:27
seb128just had a look, the descriptions could be better "Ubuntu gestures library with SwipeArea" doesn't really explain well what that library is, what is "SwipeArea"?09:30
seb128that's not a blocker09:30
seb128also "libubuntugestures" should include the soname and be "libubuntugestures5"09:30
seb128that's a blocker09:30
seb128so please fix that before archive upload09:30
seb128bonus if you improve the description09:30
seb128otherwise looks fine09:30
sil2100seb128: ACK!09:31
sil2100bzoltan_: ^09:31
bzoltan_seb128: sil2100:  fantastic! Thank you gents.09:31
Mirvsil2100: I don't really remember that. I think maybe, but then again I may mistake it with another earlier landing. but all done now anyhow :)09:32
bzoltan_seb128:  the next landing will fix those issues09:32
seb128thanks09:32
sil2100bzoltan_, Mirv: if you could change and fix that, rebuilt and I guess no re-testing will be needed09:32
sil2100Since it's generally just a library package name change09:33
bzoltan_sil2100:  Let me look after it09:34
* sil2100 goes back to his OTA-8.5 promotion hole09:34
bzoltan_zsombi:  the archive core devs require a better package description for the libubuntugestures package09:34
bzoltan_zsombi:  not here09:35
sil2100The biggest blocker is the library package name if anything ;)09:37
sil2100Description can be changed later09:37
bzoltan_sil2100:  so simple s/libubuntugestures/libubuntugestures5/ will do it?09:37
bzoltan_seb128: do you mean to simple change the package name to libubuntugestures509:44
bzoltan_?09:44
seb128bzoltan_, http://ubuntu-packaging-guide.readthedocs.org/en/latest/ubuntu-packaging-guide/libraries.html09:45
seb128bzoltan_, but yes, best practice is to use "libname<soname>" so when the abi/soname change the packages are co-installable which makes transitions easier09:46
bzoltan_seb128:  makes sense09:48
Saviqhmm hmm, where are the packages from https://requests.ci-train.ubuntu.com/#/ticket/725 ??10:22
Saviqtrainguards ↑↑ did that get published at all? there are per-silo excuses now, but those are not visible in xenial excuses... are autopkgtests ran on silos now or something?10:24
* Saviq happy if that's the case, but who can retrigger the failed test? :)10:25
robruSaviq: yes autopkgtests for silos were rolled out on Monday, i forgot to make a big announcement because there was a huge outage at the same time, and also it's a bug experimental as well10:26
Saviqrobru, nice one, /me planned to do that in our Jenkaas, much happier if that's global10:26
robruSaviq: i know pitti can retry autopkgtests, I'm not sure who else though. New uploads will trigger new tests ;-)10:26
Saviqright, new uploads will also require manual re-tests and QA ;P10:27
Saviqrobru, thing is, https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-021/excuses.html shows qtmir-gles regression, but http://autopkgtest.ubuntu.com/packages/q/qtmir-gles/xenial/amd64/ does not10:27
sil2100Not if it's a no-change rebuild! But seriously speaking, just poke pitti on -devel, maybe he can retry it for you for now10:27
Saviqjibel, can't you restart autopkgtests, too? /me hopes pitti's not our single point of failure ;)10:28
robruSaviq: oh yeah no, the autopkgtest.u.c site doesn't show the silo results at all. Click the "regression" link to see the full test run log10:28
Saviqrobru, ok, the invalid links should be stripped, then, if possible :)10:29
Saviqsame with version links pointing to void10:29
robruSaviq: what?10:29
Saviqrobru, https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-021/excuses.html10:29
robruWhat broken links?10:30
Saviqrobru, "amd64", "0.4.7+16.04.20151214.1-0ubuntu1"10:30
Saviqfor qtmir-gles in this case10:30
robruSaviq: links work for me, not sure what you're seeing10:31
Saviqrobru, v10:31
Saviqhttps://launchpad.net/ubuntu/+source/qtmir-gles/0.4.7+16.04.20151214.1-0ubuntu110:31
Saviqthat version is nowhere in ubuntu yet10:32
Saviqrobru, and as you said, http://autopkgtest.ubuntu.com/packages/q/qtmir-gles/xenial/amd64/ does not show results for silo tests10:32
Saviqboth are links out of silo excuses10:32
robruSaviq: hmm, you'll have to raise that with pitti, he maintains the code that generates that page.10:33
Saviqok, not important enough :)10:33
Saviqrobru, can you tell when are they ran? only before publishing or for all builds in silo?10:35
Saviq(/me only found first in mir QA-Granted silo)10:36
robruSaviq: currently they are only run if the qa state is "ready for qa" buy that will change soon, we're working out how to streamline the process a bit10:37
robruSaviq: oh hmmm if qa granted that means the excuses will stop updating ;-)10:37
Saviqrobru, sneaky10:38
* Saviq thought silo 21 was waiting for a +1 from autopkgtests, but will it ever get it, then?10:39
robruSaviq: yeah if it's in granted state the page will never update10:39
robruSaviq: ideally qa shouldn't grant before the tests are passing, this is what i mean by the process needing streamlining ;-)10:40
Saviqrobru, agreed, ideally we shouldn't put "ready for QA" unless it's passing, chicken'n'egg! :)10:40
Saviqrobru, all in all, best xmas gift ever! :)10:41
robruSaviq: yeah i need to invent a new state that means "lander approved, go for autopkgtests" and then it only promotes to ready if the tests pass10:41
robruSaviq: thanks! That was a huge project!10:41
Saviqand a surprise, too ;)10:42
MirvI wonder what's up with my silo publishing to xenial10:54
Mirvhttps://ci-train.ubuntu.com/job/ubuntu-landing-025-2-publish/lastSuccessfulBuild/artifact/packagelist_rsync_ubuntu-landing-025/*view*/10:54
Mirvsil2100: did you have any visibility to what happens after ^ or would we need eg cj_watson?10:55
sil2100Mirv: hmm, sadly not, I don't think our copy2distro scripts have user-visible logs (I think)10:56
sil2100Strange that it would get rejected10:57
Mirvcjwatson: could you check the above ^ rsync, not found in any queue10:58
Mirvsil2100: well it's not rejected either, more like these /dev/null:s for some reason10:58
sil2100By rejected I mean rejected by the script too, but hmmm10:58
cjwatsonit should have mailed whatever the address of the requesting bot is11:00
Mirvsil2100: did we still have anyone with access to the bot emails..11:01
cjwatsonOdd, I'm not seeing any cicopy logs from today11:05
cjwatsonOh, I bet it's locked11:05
* cjwatson clears the lock11:05
cjwatsonMirv: may work in a few minutes11:06
Mirvok11:08
cjwatsonMirv: that seems to have sorted it out; the train should catch up in a bit11:14
cjwatsonI removed /tmp/.cu2d.lock on snakefruit, which was stuck after the train incident last night11:14
bzoltan_sil2100:  The issues pointed out by seb128 are fixed in the silo60 UITK and the new build is all fine. Would you please publish the packages. I have no right to publish the ubuntu-theme11:22
sil2100bzoltan_: let me just grab my food and publish, since I'm done with OTA-8.5 now :)11:24
bzoltan_sil2100: are you? Congratulations for that!11:24
seb128 bzoltan_, small issue (not need to respin for that), usually the -dev depends on the lib (= ${binary:Version})11:25
bzoltan_seb128:  I will fix that for the next release (eta tomorrow). Thank you.11:26
Saviqtrainguards, can we publish https://requests.ci-train.ubuntu.com/#/ticket/725 please? or is it waiting on something?11:26
seb128bzoltan_, thanks11:29
Mirvcjwatson: looks good, thanks! there were indeed another landing stuck  there too but they're now all in11:32
MirvSaviq: a core-dev, so sil2100 could publish it11:33
MirvI pinged RAOF earlier but he was probably already gone11:33
cjwatsonMirv: right, ubuntu-push too11:33
SaviqMirv, ah, tx11:34
seb128xavigarcia, charles, could you look at bug #1502094 for indicator-sound? it's probably just changing gee-1.0 to gee-0.8  in the Makefile and debian/control, would be nice to have that done in one of the next landings if we can11:37
sil2100Saviq: on it in a minute, was a bit busy in the morning ;)11:37
ubot5bug 1502094 in unity-lens-files (Ubuntu) "libgee-0.8-dev should be used, libgee-dev will be removed from the archive" [High,In progress] https://launchpad.net/bugs/150209411:37
seb128xavigarcia, charles, and yeah, the versionning is backward, 1.0 is old and 0.8 newer11:37
xavigarciaseb128: sure, I will take a look11:41
seb128xavigarcia, thanks11:42
seb128xavigarcia, it's probably trivial, https://code.launchpad.net/~seb128/unity-lens-files/use-gee-0.8/+merge/280696 is one example11:42
xavigarciaseb128: I see... I need to check the state of the repository, though, as we had a rolled back landing last month11:43
xavigarciaseb128: and it seems we are delaying some fixes in the sound indicator until a pulseaudio issue is fixed11:43
seb128k11:44
seb128well no hurry11:44
seb128that needs to be done for the LTS11:44
xavigarciaseb128: okay11:46
sil2100seb128: hey! Have time for another binNEW ;) ? This time quite trivial as it's a standard mir soversion bump: https://ci-train.ubuntu.com/job/ubuntu-landing-021-2-publish/1/artifact/mir_xenial_packaging_changes.diff11:54
seb128+111:54
seb128(are we sure the .pc removed is not used?)11:55
seb128lunch now, bbiab11:56
=== mzanetti_ is now known as mzanetti
kdubtrainguards, silo 21 is still undergoing testing, found an 11th hour bug... please don't publish just yet12:16
sil2100Saviq, Mirv: ^12:17
sil2100I wanted to publish but wanted one of the merges approved, and good thing it was unapproved as it wasn't ready for release ;)12:17
sil2100seb128: thanks! :)12:17
Mirvthanks kdub12:18
kdubI'm not sure how it went to QA granted yet, it was toggled to "QA needed" briefly, and then back to "QA required" a few minutes later when the bug was found12:18
sil2100We had a train derailment, maybe it got switched back then12:23
=== alan_g is now known as alan_g|lunch
Saviqsil2100, kdub, ack :(13:45
=== alan_g|lunch is now known as alan_g
Saviq"jenkins is preparing to shut down", should I not start jobs?14:13
Saviqor will they just get picked up when it's back up again?14:14
jhodappsil2100, the release notes for OTA 8.5 don't mention background playlists in media-hub14:17
sil2100jhodapp: ah, right, we had to pull that in with the fixes, right?14:18
jhodappsil2100, yes indeed14:18
jhodappsil2100, can you please dput the qtmultimedia source pkg from ppa:jhodapp/ubuntu/ppa to silo 34 please?14:36
sil2100jhodapp: sure14:37
jhodappooh, double please :)14:37
jhodappthanks14:37
fginthernerochiaro, the lp:camera-app/staging and lp:qtubuntu-camera/staging branches are now setup. Please let us know if there are any changes necessary14:38
jhodappsil2100, let me know when I can do a watch only build on that silo14:40
nerochiarofginther: where do i get the packages ?14:41
sil2100jhodapp: 5.4.1-1ubuntu19, right?14:41
jhodappyes14:42
sil2100jhodapp: ah, we'll need the ~overlay1 appended, right? Can I do it, or do you keep normal versioning for the overlay?14:42
Mirvcharles: you've held to this silo for two months, do you still need it or can it be abandoned to free up silos? https://requests.ci-train.ubuntu.com/#/ticket/50714:42
jhodappsil2100, hmm, robru has never had to do that before14:42
sil2100Not sure what's the notation for qt packages14:43
jhodappsil2100, pretty sure he just uploaded it as is14:43
sil2100Mirv: hey! You append ~overlay to qt packages released to the overlay? I don't think so, right?14:43
Mirvsil2100: usually nowadays yes, like the today's qtdeclarative was ~overlay214:44
sil2100hm hmmm14:44
Mirvand same for qtbase + qtpim14:44
sil2100Ok, so let's do it here too14:44
sil2100jhodapp: no worries, taking care of it :)14:44
Mirvsil2100: here as in where?14:44
jhodappsil2100, thanks!14:45
jhodappMirv, a new qtmultimedia upload from me14:45
sil2100Mirv: qtmultimedia-opensource-src14:45
Mirvsil2100: jhodapp: ah ok, yes, better there too14:45
jhodappMirv, and all of these changes are already upstreamed :)14:45
sil2100\o/ ;)14:45
jhodappMirv, would you be able to push the -gles package after sil2100 is done?14:46
jhodappsilo 3414:46
Mirvjhodapp: great! I hope all of them would be soon merged too in upstream so that we know they're happy with them14:47
sil2100jhodapp: ok, package pushed14:47
Mirvjhodapp: ok14:47
jhodappMirv, they already are happy with them, they just literally need to merge it14:47
jhodappthanks sil210014:47
Mirvjhodapp: I've bookmarked the following three at least: https://codereview.qt-project.org/#/c/138927/ + https://codereview.qt-project.org/#/c/142109/ + https://codereview.qt-project.org/#/c/142334/ all need formal code-review approval, after which you can also yourself click a button to try merging them to staging14:51
Mirvanyway, let's hope they're getting there soonish14:52
jhodappMirv, yes they're in Yoann's hands14:53
Mirvjhodapp: btw I'm not sure if you noticed but tsdgeos filed bug #1523407 - since Unity 8 is doing dual landings (=same code for vivid + xenial), they will need the code to be exactly as it is in upstream also for xenial before they can start utilizing features. so there's some work for January there, to make vivid even more identical upstream and then of course syncing up everything to xenial14:54
ubot5bug 1523407 in Canonical System Image "Playlist support in vivid+overlay and Xenial is different/non compatible" [High,Confirmed] https://launchpad.net/bugs/152340714:54
Mirvand I think it was the comment #1 that they then agreed is the correct way, unlike what Albert wrote in the description :)14:55
Mirvotherwise xenial would need to lie about its version14:55
jhodappMirv, yes that's a story currently in progress for my team's current sprint14:55
sil2100jhodapp: yw!14:55
Mirvjhodapp: ok! anyway, uploading the gles now to the same silo14:56
jhodappMirv, thanks!14:56
jhodappMirv, we did the first steps already of syncing media-hub and gstreamer versions across vivid and xenial, next comes the higher level stuff like qtmultimedia and qtubuntu-media14:56
fginthernerochiaro, oh, let me fix that14:58
Mirvjhodapp: ok, I noticed the gstreamer ones. I think with time you could even move to dual landings (or even the next one could be such potentially).15:00
Mirvthe teams that are doing those generally seem pretty happy with the less complexity15:00
jhodappMirv, yes indeed15:01
jhodappMirv, oh I really want to get there, it is a little annoying because we used to be told to just ignore wily landings15:01
jhodappnow it's the opposite15:01
fginthernerochiaro, I fixed the missing debs. I've retriggered the build for https://code.launchpad.net/~uriboni/camera-app/no-permissions-dialog/+merge/27926015:36
nerochiarofginther: ok, so every MR that is submitted against these two branches will have packages rebuilt automatically and jenkins will post a note on the MR ?15:36
fginthernerochiaro, yes, that should all be working now15:37
nerochiarofginther: thanks15:37
jhodappjibel, does this bug only happen on arale or have you seen it on krillin as well? https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/147903615:39
ubot5Ubuntu bug 1479036 in media-hub (Ubuntu RTM) "/usr/bin/media-hub-server:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:core::ubuntu::media::HashedKeyedPlayerStore::player_for_key" [Critical,Confirmed]15:40
jibelMirv, why do we need silo 5 at all on the overlay? it has nothing to do with the phone, does it?16:19
tvosstrainguards, I would need a silo for https://requests.ci-train.ubuntu.com/#/ticket/79316:29
tvosssil2100, Mirv ^16:29
sil2100On it!16:29
* tvoss making sure the request is seen16:29
Saviqtrainguards, what does "Diff missing" mean when in silo status for a set of packages?16:30
seb128can we get the ubuntu-ui-toolkit/ubuntu-themes silo force merged?16:33
sil2100Saviq: not sure what causes that to happen, but usually a DIFF_ONLY build should help in that case16:33
seb128I want to do another ubuntu-themes landing today before holidays and it's getting tight ... that one already migrated but I guess no way to force merge one component only?16:33
seb128uitk is still doing autopkgtests16:34
Mirvjibel: it's for people like kenvandine who run overlay on their desktop for development purposes.16:34
sil2100seb128: yeah, no standard way of doing that, safest bet is to merge everything16:34
seb128sil2100, can you do it?16:34
sil2100seb128: let me look into that16:35
Saviqsil2100, I think it might be a failed build job causing it16:35
sil2100seb128: hmm, I see it's landed, the changes should be merged?16:36
sil2100https://requests.ci-train.ubuntu.com/#/ticket/778 ?16:36
MirvSaviq: train's diffs are not there. either run build job normally or with DIFF_ONLY for a no-op16:36
SaviqI just had a build with that bombed because of conflicts16:36
SaviqMirv, ack16:36
sil2100seb128: hmm, interesting! The landing didn't have an ubuntu-theme merge in it16:38
seb128hum?16:38
sil2100seb128: or maybe it did but during the train outage it got nuked...16:38
sil2100seb128: it did have the ubuntu-theme package tho16:38
seb128so we need to manually merge?16:38
seb128https://code.launchpad.net/~ci-train-bot/ubuntu-themes/ubuntu-themes-ubuntu-xenial-landing-06016:39
seb128sil2100, ^16:39
sil2100I suppose we need to manually merge as the train obviously forgot about this merge completely16:39
sil2100A bzr push --overwrite is what the train usually does16:39
seb128k, I can do that that16:40
sil2100seb128: thanks! And sorry for this, I suspect the derailment to be the cause of this situation16:41
renatutrainguards, could you assign this silo for me? https://requests.ci-train.ubuntu.com/#/ticket/79416:42
sil2100renatu: assigning!16:42
=== sil2100 changed the topic of #ubuntu-ci-eng to: Train trouble? ping trainguards | CI problems? ping cihelp | Train: http://bit.ly/1hGZsfS | QA Signoffs: http://bit.ly/1qMAKYd | Known Issues: CATASTROPHIC TRAIN FAILURE restored from stale backup, please do your best, I'm sorry. Please run "DIFF_ONLY" build job on your silos. Also, low on silos!
renatusil2100, thanks16:45
jibelbfiller, renatu silo 55 approved17:33
bfillerjibel: thanks17:35
bfillerjibel: looks like 45 landing as well, hope we don't have to rebuild 55 as 45 has address book as well?17:37
bzoltan_trainguards: I would like to ask for a silo  - https://requests.ci-train.ubuntu.com/#/ticket/79617:52
bzoltan_Mirv: sil2100: ^17:54
=== alan_g is now known as alan_g|EOD
bzoltan_Is here a trainguard at this hour?18:14
Mirvbzoltan_: all 60 are assigned right at the moment18:44
Mirvbzoltan_: I'll clean my qtdeclarative one since I follow up it anyway18:44
Mirvbzoltan_: ok you have silo18:46
Mirvbzoltan_: kicked a build too18:47
bzoltan_Mirv:  thank you!18:53
dobeytrainguards: can i get a retry on https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-041/+build/8448901 please?20:40
robrudobey: on it20:47
dobeyrobru: thanks20:50
robrudobey: yw20:50

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