[13:13] <Mirv> jibel: is the 14.04.4 being delayed? the mandatory HWE upgrade is still in -proposed http://people.canonical.com/~ubuntu-archive/pending-sru.html
[13:13] <Mirv> so it's not useful to test yet that much
[13:13] <jibel> Mirv, it's planned for next week
[13:13] <Mirv> not too much time left
[13:17] <Mirv> querying a bit elsewhere if there's an issue to help with it or if it's just stuck
[13:22] <Mirv> renatu: any ETA on https://requests.ci-train.ubuntu.com/#/ticket/768 ? just asking because it's the oldest non-touched silo we have out of the 61? (although just 3 weeks still)
[13:22] <Mirv> I didn't find any silos to really free up :(
[13:22] <renatu> Mirv, I am waiting bill to review it. I will ping him today
[13:23] <Mirv> renatu: thanks!
[13:23] <renatu> welcome
[13:42] <popey> pmcgowan, dunno if anyone has mentioned to you but the milestones dates look wrong... https://launchpad.net/canonical-devices-system-image/+milestones
[13:44] <pmcgowan> popey, those are the original freeze dates
[13:44] <popey> ah
[13:44] <popey> thought they'd get updated
[13:44] <popey> nvm
[13:54] <Saviq> trainguards, restart https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-057/+build/8964129 please :)
[13:58] <Mirv> Saviq: done
[13:58] <Saviq> Mirv, thank you, /me files a bug about this test
[14:01] <alexabreu> Mirv, do you think that it would be possible to re-launch britney on silo 16?
[14:02] <Mirv> alexabreu: not yet, the feature for retries is not yet available (ETA a couple of weeks). try pinging pitti with the url https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-016/excuses.html on #ubuntu-devel, he can retry
[14:03] <alexabreu> Mirv, ok thanks, I thought you had the powers :)
[14:03] <Mirv> alexabreu: I will, once the feature is there :)
[14:03] <alexabreu> Mirv, hah ;)
[14:04] <Mirv> after it's implemented the retry will be possible for those that have the upload rights too. me and sil2100 for example have plenty of those rights.
[14:14] <pstolowski_> sil2100_, hey, may i ask for removal of thumbnailer packages from silo 24's ppa?
[14:22] <alf_> trainguards: Hi! I am unable to get a silo assigned for train request. Should I just wait a bit and request a silo later, or is there something else going wrong?
[14:24] <Mirv> alf_: the problem is all 60 (61) silos are full and at least I haven't found any that could be easily freed
[14:25] <Mirv> also I think QA is busy with OTA-9.5 so the QA queue has also 6-7 silos that won't be freed any time soon
[14:25] <alf_> Mirv: ok, I guess I will just wait then, thanks!
[14:26] <Mirv> Trevinho: could your two "proposed pocket" silos be freed, are you able to track those trusty/wily SRU:s without train? the trunks would get updated.
[14:27] <Trevinho> Mirv: I don't know what I could do... I mean SRU have been approved, so they should land soon.. Hopefully -_-
[14:28] <Trevinho> Mirv: I don't know whether release team can do that without
[14:28] <Mirv> Trevinho: I mean, is it ok for you if I merge the silos and you need to track them yourself with train page?
[14:28] <Mirv> wihout train page, I mean
[14:31] <Mirv> Trevinho: both look like they will be ok:d to go, 12 in the queue so during the last 5 days release time could already have published them. but I'm asking so that others could get the silos already before the release team acts.
[14:32] <Trevinho> Mirv: ah, ok... Sure. You can merge the ppa..
[14:32] <Trevinho> I just don't want to loose them before are migrated
[14:35] <Mirv> Trevinho: so... you don't want the PPA:s to be emptied before they're migrated? that's ok, I was just asking if it would be ok but I understand this is the default and preferred way.
[14:35] <Mirv> just searching for silos to reuse
[14:35] <Trevinho> Mirv: I'm fine if they're free'd if SRU team can still approve them then, but I can ping someone to migrate quicker maybe?
[14:39] <Mirv> Trevinho: right, the packages are already in -proposed, not in the queue, so they won't disapper even if the silos are freed - https://launchpad.net/ubuntu/+source/compiz/1:0.9.12.2+15.10.20151202-0ubuntu1 https://launchpad.net/ubuntu/+source/unity/7.3.3+15.10.20151203-0ubuntu1 https://launchpad.net/ubuntu/+source/unity-lens-music/6.9.0+14.04.20151120.2-0ubuntu1
[14:39] <Mirv> Trevinho: it's the case when they are still in unapproved queue https://launchpad.net/ubuntu/trusty/+queue?queue_state=1&queue_text= where they aren't yet physically copied
[14:39] <Trevinho> Mirv: ok, fine... Then you can free the silo (and merge branches) if you want
[14:39] <Mirv> Trevinho: thank you :) and alf_ thanks you too.
[14:40] <Trevinho> As bugs are both Ok'ed
[14:40] <Mirv> Trevinho: yes they are, it's just up to stable update release team now
[18:25] <jibel> kgunn, re silo 48, I am not sure what this error means https://requests.ci-train.ubuntu.com/static/britney/vivid/landing-048/excuses.html
[18:25] <jibel> old binaries left
[20:17] <kgunn> jibel: hmmm, i've never seen that before...and for ppc64....and libmirserver35 is quite old
[20:18] <jibel> kgunn, and same on xenial for ppc64 and arm64
[20:18] <kgunn> wow 13.3 even with libmirserver 31
[20:18] <kgunn> slangasek: got something we've never seen before https://requests.ci-train.ubuntu.com/static/britney/vivid/landing-048/excuses.html
[20:18] <kgunn> "old binaries left"
[20:19] <slangasek> kgunn: yes; that implies the old version of the package built on this architecture, and the new one is built on all architectures where it's expected to build but did not build these binary packages on that architecture
[20:20] <slangasek> digging now
[20:21] <kgunn> oh...wow
[20:21] <kgunn> i see it now
[20:21] <kgunn> i didn't realize it didn't build for ppc64/arm64
[20:21] <kgunn> crap
[20:22] <kgunn> we rebuilt so many times...
[20:22] <slangasek> kgunn: is this targeted to the overlay ppa or to SRU?
[20:22] <kgunn> slangasek: overlay ppa + xenial
[20:22] <kgunn> just a point release
[20:23] <slangasek> ok
[20:23] <slangasek> so in the archive, there's no mir build for ppc64el on vivid
[20:23] <kgunn> jibel: slangasek so should we just attempt a rebuild?
[20:23] <slangasek> and in the overlay ppa, let's see
[20:23] <kgunn> i know it builds .....we just rebuilt it over and over
[20:23] <kgunn> arm64 times out frequently
[20:23] <slangasek> um... *why* does it build on ppc64el?
[20:23] <kgunn> altho...ppc64 i've not seen fail
[20:23] <slangasek> why do you want it built there? :)
[20:24] <slangasek> I see that in xenial, it is built on ppc64el
[20:25] <kgunn> slangasek: ah!! that's a kernel bug on ppc64 xenial i think
[20:26] <kgunn> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1540731
[20:26] <ubot5`> Launchpad bug 1540731 in linux (Ubuntu) "SocketMessenger::update_session_creds() fails to get client PID, causing "[ FAILED ] PromptSessionClientAPI.client_pid_is_associated_with_session"" [Critical,In progress]
[20:28] <kgunn> and the same error on vivid....i guess it's using the same kernel
[20:28] <slangasek> kgunn: ok; I would recommend making the test an XFAIL on ppc64el so that you can be unblocked
[20:28] <slangasek> and the build log shows kernel 4.2.0-27-generic
[20:28] <slangasek> the kernel is always the same for the builds, regardless of target release
[20:30] <kgunn> hmmm.... slangasek could it be patched, cause that bug was found with 4.4
[20:30] <kgunn> kernel
[20:30] <slangasek> it's possible
[20:30] <kgunn> it's definitely tell-tale
[20:30] <kgunn> sign
[21:07] <kgunn> jibel: ok, i just disabled the one unit test that the kernel bug makes fail...so i'm gonna rebuild just mir
[21:08] <kgunn> jibel: am i to assume the testing continues, since this is effectively a no change rebuild?