[09:48] <morphis> cjwatson: ping
[09:48] <cjwatson> morphis: Please tell me what you want and I'll reply when I'm around.
[09:49] <morphis> cjwatson: sil2100 added me to the list of silo uploaders but I basically don't get any rejected/successful mails, just dput goes through successfully
[09:49] <morphis> cjwatson: sil2100 suspects that we're missing something very simple in the process, you may know :-)
[09:52] <sil2100> cjwatson: as morphis said, he seems to be dputting stuff correctly but it doesn nothing, no feedback, no upload appearing in the PPA
[09:54] <Mirv> funny, the font size changes in OTA-9
[09:54] <Mirv> I've soon forgotten about them already but the bookmarks in webbrowser-app eg. are in pretty small print, and maybe the indicator titles too are smaller than before
[09:54] <Mirv> and somehow terminal font got huge before I resized it back to smaller
[10:06] <Mirv> ok, it's probably this https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/fontSize/+merge/280831
[10:06] <Mirv> that's alright, the webbrowser bookmark text size is maybe a bit too small only, the title could be larger than the url
[11:31] <morphis> sil2100, Mirv: any reason why the automated sign off does work? I can't switch lander signoff to "approved" for my silo
[11:39] <sil2100> morphis: in which silo is that?
[11:39] <sil2100> 12?
[11:40] <morphis> sil2100: yes, silo 12
[11:41] <morphis> sil2100: you changed something? now I could move it approved
[11:41] <sil2100> morphis: no, but it might mean that autopkgtests were slowly moving to the running state
[11:41] <sil2100> Well, there are some rough edges here and there I guess
[11:43] <morphis> ok
[11:43] <morphis> davmor2: silo 12 should now show up on your list :-)
[11:43] <davmor2> morphis: \o/
[11:43] <morphis> davmor2: and silo 45 will come a bit later
[11:43] <morphis> pulse works fine so far on my krillin
[11:44] <davmor2> morphis: switching between bt headset speaker and loud speaker in a call works then?
[11:45] <morphis> davmor2: not that far yet :-)
[11:45] <morphis> but A2DP does
[11:45] <davmor2> hahaha
[11:45] <davmor2> unless you have an s10 :P
[11:47] <davmor2> morphis: at some point when you are quiet you'll have to fix that you know ;) Of course that could take a while for you to be quiet :)
[11:47] <morphis> davmor2: hehe
[11:47] <morphis> davmor2: suspect somewhere around summer time :-)
[11:47] <cjwatson> morphis: If this is pulseaudio, you're signing it with a key (56B98A9E) that isn't registered in Launchpad.
[11:48] <cjwatson> morphis: https://help.launchpad.net/Packaging/UploadErrors#The_upload_appears_to_work_but_I_don.27t_get_any_email_about_it
[11:48] <morphis> cjwatson: hm
[11:49] <morphis> cjwatson: you're right
[11:50] <morphis> interesting that this wasn't a problem before
[11:50] <rvr> popey: Hello
[11:50] <popey> rvr, o/
[11:51] <rvr> popey: Could you add a link to media-hub MPRIS test cases to the music app test plan?
[11:51] <morphis> cjwatson: but thanks
[11:51] <popey> didn't we discuss this yesterday?
[11:52] <rvr> popey: More or less :D
[11:52] <davmor2> popey: this is the official request over the maybe you could request ;)
[11:53] <popey> it's already on the list to do
[11:53] <popey> but not much point right now given we don't have a new click for you to test
[11:54] <rvr> I must ping charles too about that for indicator-sound
[11:55] <rvr> charles: So, when I available, ping back :)
[11:55] <rvr> s/I //
[12:20] <sil2100> alex_abreu: hey!
[12:21] <sil2100> alex_abreu: so, silo https://requests.ci-train.ubuntu.com/#/ticket/634 needs a rebuild of webbrowser-app right now
[13:19] <bschaefer> hello would anyone be able to restart the ppc64el build on this landing silo? https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-010/+packages (for mir xenial)
[13:22] <Mirv> sil2100: FYI I filed bug #1539076 about the issue with eg silo 060 or any qtbase/qtdeclarative silo
[13:39] <bschaefer> if someone could restart this failure: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-010/+build/8907965
[13:40] <kdub> +1 ^
[13:40] <bschaefer> needs to start the landing process very soon (just 1 flaky test that failed)
[13:46] <bschaefer> sil2100, Mirv if you are able to :) ^
[13:52] <Mirv> bschaefer: ok
[13:52] <bschaefer> thanks!
[13:53] <Mirv> refresh to see how it goes now
[13:53]  * bschaefer crosses fingers :)
[13:56] <morphis> Mirv, sil2100: I am not getting failing tests on my silo: https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-012/excuses.html
[13:56] <morphis> what is the policy how to deal with those things?
[13:56] <morphis> basically hybris changed upstream which we're now basing on which then breaks kwin
[14:02] <Mirv> morphis: it's a bit tough when it comes to community flavors using the same bits we do - my big Qt landings are really difficult, and for Qt 5.5 I ended up fixing some things myself and some things (when it was test only and not build failing) were overridden
[14:03] <Mirv> morphis: also AFAIK kwin is currently forcefully overridden anyway, but as I just filed bug #1539076 the silo autopkgtests don't understands the overrides
[14:03] <Mirv> morphis: but of course a build failure (instead of test failure) should be bug filed against kwin and maybe asking on #kubuntu-devel then if anyone could take a look at fixing it
[14:03] <morphis> Mirv: ok, however we have to land this anyway
[14:05] <Mirv> morphis: yes, for vivid at least and maybe manually to xenial or skipping it for now
[14:05] <morphis> Mirv: not really possible as its a dual landing silo which is already in QA
[14:05] <jibel> can we land in vivid only and fix xenial?
[14:06] <Mirv> I'm not sure who would be the best contact for Plasma Mobile (which is probably the main kwin hybris user) but they have some paid staff AFAIK on it so there should be interest
[14:06] <morphis> Mirv: let me ask in #kwin-devel
[14:06] <Mirv> morphis: jibel: we can always copy stuff manually (after approval) and clean + merge and that way skip one release
[14:06] <Mirv> (skip for xenial)
[14:07] <jibel> not the solution I like though
[14:08] <morphis> IMHO the kwin guys need to fix this as they shouldn't depend on these APIs at all
[14:21] <davmor2> morphis: I guess they do for their mobile version
[14:22] <davmor2> morphis: man I'm on fire today ;)
[14:28] <morphis> davmor2: not only you :-)
[14:59] <bschaefer> trainguards need a rebuild of https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-010/+build/8908391
[15:01] <sil2100> bschaefer: on it
[15:02] <bschaefer> sil2100, thanks!
[15:02] <sil2100> bschaefer: done
[15:02] <sil2100> yw :)
[15:02] <bschaefer> double thanks!
[15:31] <Saviq> trainguards, can we please have qtdeclarative-opensource-src removed from silo 19? patch was deemed incorrect
[15:31] <Saviq> Mirv, ↑
[15:31] <Saviq> Mirv, just FYI, not "do it!"
[15:34] <sil2100> Saviq: on it
[15:34] <Mirv> Saviq: :)
[15:34] <sil2100> Saviq: along with -gles I susspect right?
[15:34] <Saviq> sil2100, yup, thanks
[15:35] <sil2100> Done
[15:41] <sil2100> seb128: hello! We have a silo we'd like to land for OTA-9.5 and the android-headers landing seems to be adding new binary packages that need a binNEW review
[15:42] <sil2100> seb128: I checked all the other packages and rised my concerns there, but I would need someone to do the binNEW review for https://ci-train.ubuntu.com/job/ubuntu-landing-012-1-build/30/artifact/android-headers_vivid_packaging_changes.diff and https://ci-train.ubuntu.com/job/ubuntu-landing-012-1-build/30/artifact/android-headers_xenial_packaging_changes.diff
[15:42] <sil2100> seb128: (I did not manage to browse through the full diff for those yet)
[15:42] <seb128> sil2100, sorry, I was travelling this week and I'm crazy busy and travelling again tomorrow
[15:43] <seb128> can you find somebody else?
[15:43] <sil2100> seb128: ok, no worries :)
[16:10] <sil2100> slangasek: hey! :)
[16:10] <sil2100> slangasek: we need someone with binNEW review powers for android-headers in silo 12
[16:11] <sil2100> slangasek: https://ci-train.ubuntu.com/job/ubuntu-landing-012-1-build/30/artifact/android-headers_vivid_packaging_changes.diff and https://ci-train.ubuntu.com/job/ubuntu-landing-012-1-build/30/artifact/android-headers_xenial_packaging_changes.diff - I didn't yet scan the whole diff for that as I was doing the reviews of all the other packages for now
[16:11] <slangasek> sil2100: ok - after the team meeting? :)
[16:11] <sil2100> AARGH
[16:11] <sil2100> Team meeting!
[16:15] <robru> morphis: sil2100: you can't sign off on a silo if it contains build failures or has packages that are still building
[16:19] <morphis> robru: ah I see
[17:23] <bschaefer> trainguards seems like a flaky test in the autopkg tests: https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-010/excuses.html anyway to restart this process?
[17:24] <robru> bschaefer: for a retry you'll need pitti
[17:26]  * bschaefer does not see him around
[17:27] <robru> bschaefer: I'm not sure who else can. We just implemented a retry thing but it's not an hooked up yet
[17:28] <robru> bschaefer: worst case just rebuild the silo but that's slow and wasteful
[17:28] <bschaefer> yeah that would take a while, but we shall see, camako ^
[17:38] <Saviq> trainguards, can you please drop ubuntu-system-settings from silo 19, we jumped the gun on that, thanks!
[17:39] <sil2100> In a meeting right now, need a few mins
[17:39] <robru> On it
[17:40] <slangasek> sil2100: yes to android-headers
[17:40] <sil2100> slangasek: \o/
[17:41] <slangasek> sil2100: btw, how did this come on your radar to ask about? Looking at the ticket, I don't see anything that tells me there are packaging changes needing review: https://requests.ci-train.ubuntu.com/#/ticket/779
[17:42] <sil2100> slangasek: since it's still in testing, it's not ready for publishing because QA is just testing it - we're doing a review now since this is super important to land ASAP
[17:42] <slangasek> ok
[17:42] <sil2100> So we needed all reviews early
[17:42] <slangasek> sil2100: I think this is a reasonable workflow, I just wasn't sure what triggered it since bileto doesn't seem to support that directly :)
[17:43] <robru> slangasek: click through to the artifacts
[17:44] <slangasek> robru: I know how to find the artifacts; I'm saying that's not the workflow, so how did this come to anyone's /attention/
[17:44] <robru> slangasek: i assume the landers were proactive about it
[17:44] <slangasek> yes
[17:44] <slangasek> that's good :-)
[17:45] <robru> Saviq: done
[17:45] <Saviq> robru, thanks
[17:45] <robru> Yw
[18:07] <robru> slangasek: huh my schroot has /sys, any other ideas why it might not work?
[18:12] <slangasek> robru: as said in meeting, you need the cgroups mounts
[18:12] <robru> slangasek: those aren't covered by just bindmounting /sys? they're all in /sys
[18:13] <slangasek> robru: they are separate mounts; bind mounting a parent directory does not implicitly bind mount the child mounts
[18:13] <robru> slangasek: is there documentation on how to mount those? seems like there's a lot of them
[18:13] <slangasek> robru: you can verify this for yourself by looking at /sys/fs/cgroup in the chroot
[18:13] <slangasek> robru: I don't know
[18:14] <robru> slangasek: is indeed empty
[18:14] <slangasek> your question was if it's possible to run an lxc container inside of a chroot, and the answer is yes; but the details are an exercise for the reader
[18:15] <robru> slangasek: right
[19:34] <dobey> robru: hey. could we maybe make it so that automated signoff doesn't needlessly wait for "always failed" tests to finish?
[20:20] <robru> dobey: could do, can you file a bug against lp:bileto?
[20:23] <sil2100> Publishing that without reviewed branches, the silo is too critical to wait on those ^
[20:23] <camako> robru , theunity8 autopkgtests for silo 10 are taking suspiciously long on armhf (4.5 hours and going). Do you know if this is normal?
[20:24] <camako> this is one of those "always failed" tests :-(
[20:25] <robru> camako: they haven't been running for 4.5 hours, they ran and then they got retried. there's some kind of bug going on that makes specifically unity8 autopkgtests get retried unreasonably often but I haven't been able to track it down just yet
[20:25] <dobey> robru: sure
[20:26] <camako> robru, ok.. will britney eventually give up? or does it need intervention?
[20:27] <robru> camako: it will eventually complete but then it'll probably be retried every 5ish hours until the end of time. also last time they completed there was a failure
[20:27] <robru> camako: actually you need to investigate this problem with mir: https://requests.ci-train.ubuntu.com/static/britney/vivid/landing-010/excuses.html
[20:29] <dobey> robru: https://bugs.launchpad.net/bileto/+bug/1539254
[20:29] <robru> thanks
[20:29] <camako> robru, that is the one I was referring to. So that's an actual failure?
[20:29] <camako> autopkgtest for unity8 8.11+15.04.20160122-0ubuntu1: amd64: Always failed [artifacts], armhf: Test in progress (always failed), i386: Always failed [artifacts]
[20:30] <camako> ^ armhf one
[20:30] <robru> camako: no, look at mir
[20:32] <camako> robru, not sure what the problem is? Is it the comment with the "old binaries.."?
[20:33] <robru> camako: yes, that is causing britney to call this silo a failure.
[20:33] <camako> oh ok thanks I'll investigate
[20:35] <robru> camako: so the version number listed is newer than distro but older than what's in the ppa, did you stop building that package or something?
[20:35] <camako> robru, it was someone else's silo that I took over... Possibly yeah
[20:36] <camako> robru, actually silo says "Running" but I guess you're saying it's "running" due to that unity8 bug, and it'll be a failure becuase of the "old packages..." thing
[20:36] <robru> camako: yes
[20:36] <camako> ok
[20:36] <camako> thanks robru
[20:37] <robru> camako: yeah I'm not sure what that error is, I'll try deleting old versions of the package
[20:38] <robru> camako: check back in ~25 minutes and see if it still says that
[20:38] <rvr> mzanetti: ping
[20:38] <camako> ok thanks.. willl do
[20:59] <camako> ha?
[20:59] <camako> huh
[21:01] <robru> camako: looks like jibel set it to approved by mistake and then tried to set it to 'ready', except that bileto forces ready/required depending on if britney is still running or not
[21:01] <jibel> robru, any idea why autopkgtest on silo 10 are still running for vivid. I don't find it in the run queue.
[21:01] <jibel> ?
[21:02] <camako> robru ok
[21:02] <jibel> camako, yeah sorry, I wanted to mark it ready for QA but bileto doesn't let me do it
[21:02] <robru> jibel: it's in the run queue, http://autopkgtest.ubuntu.com/running.shtml grep for 'landing-010', although it looks in a bad way
[21:03] <robru> jibel: i dunno, just manually put it in the trello board I guess, this britney stuff doesn't work very well
[21:03] <jibel> robru, ah right, i didn't find it
[21:03] <jibel> thanks
[21:03] <jibel> robru, is there a way to force the silo to 'ready for qa' ?
[21:03] <camako> ugh do we need to restart it or something?
[21:04] <robru> jibel: I think if you put some text in the manual download field it'll let you set it as 'ready' but when britney runs & fails again it'll probably override that again
[21:06] <jibel> robru, bad hack but it worked.
[21:07] <camako> \o/
[21:07] <robru> jibel: yeah the manual downloads field is an entirely bad hack to begin with. normally the only way to ever get a silo 'ready' is to have britney approve it, but britney can't approve manual downloads because there's no ppa to review, so I had to disable the qa_signoff auto-setting code if there's any value in manual downloads.
[21:36] <mzanetti> rvr, hey
[22:09] <Elleo> trainguards: any idea why automated signoff doesn't seem to be running on this silo? https://requests.ci-train.ubuntu.com/#/ticket/887 (we had previously started the automated test process then had to switch out of approved for some last minute additions, after switching back to approved it doesn't appear to be starting the test process again)
[22:11] <robru> Elleo: it's only been 15 minutes since you approved it. Britney runs every 35ish minutes
[22:11] <Elleo> robru: ah, didn't realise that; thanks
[22:13] <robru> Elleo: if you want to play "guess when britneys next run is", refer to https://requests.ci-train.ubuntu.com/static/britney/last-run.txt and check the timestamp nearest the bottom, round up to the nearest 5 minutes, then add the elapsed time listed at the very end
[22:14] <Elleo> robru: thanks
[22:14] <robru> Elleo: you're welcome. So probably 30 more minutes, looks like you just missed the cutoff
[22:27] <rvr> mzanetti: https://bugs.launchpad.net/tagger/+bug/1539087
[22:27] <mzanetti> rvr, fixing atm
[22:27] <rvr> mzanetti: Ah, cool!