[08:19] <oSoMoN> jibel, hey, can silo 3 be marked ready for QA validation? the automated tests signoff is marked failed because of https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-003/excuses.html , but that’s harmless and a false warning really, given that the version of oxide-qt in xenial-security hasn’t been copied over to the overlay PPA
[08:27] <dbarth> sil2100: one thing i worry though is that enabling arm64 builds in a ppa will not be specific to a release
[08:27] <dbarth> ie, we will have build failures when we upload releases for vivid and below
[08:29] <jibel> oSoMoN, done
[08:30] <oSoMoN> jibel, thanks!
[09:23] <bzoltan> sil2100:  would you be able to merge that silo under the  https://requests.ci-train.ubuntu.com/#/ticket/1485 ?
[09:26] <sil2100> bzoltan: let me take a look
[09:26] <sil2100> bzoltan: do you know why that one autopkgtest is failing?
[09:27] <sil2100> bzoltan: is that some temporary failure? Maybe a retry will help? Or is it a known regression somewhere else?
[09:28] <bzoltan> sil2100: I do not see any regressing autopkg test.
[09:28] <bzoltan> sil2100:  do I miss something?
[09:29] <sil2100> http://people.canonical.com/~ubuntu-archive/proposed-migration/yakkety/update_excuses.html#ubuntu-ui-toolkit
[09:29] <sil2100> Regression in ubuntuone-credentials
[09:29] <sil2100> I could re-run that if you suspect it's a transient issue
[09:32] <bzoltan> sil2100:  must be a flaky test because here it did pass - https://requests.ci-train.ubuntu.com/static/britney/yakkety/landing-047/excuses.html
[09:32] <bzoltan> sil2100:  a restart would be nice, yes, please
[09:33] <bzoltan> sil2100: you are doing what Timo used to do for me :)
[09:33] <sil2100> bzoltan: ok, let's wait and see if it passes, if it does it should migrate and auto-merge in a bit
[09:34] <sil2100> If not we can dive in and then manually merge it
[10:24] <sil2100> bzoltan: autopkgtest passed now, let's see if it migrates soon :)
[10:26] <bzoltan> sil2100: \o/
[15:53] <ChrisTownsend> trainguards: Hey, I set https://requests.ci-train.ubuntu.com/#/ticket/1506 to Lander Approved over 30 minutes ago and it's not running (yet).  How can I check to see if its queued to run?
[15:55] <robru> ChrisTownsend: https://requests.ci-train.ubuntu.com/#/tickets?active_only&lander_signoff=Approved
[15:56] <robru> ChrisTownsend: britney is quite slow, usually an hour iterate over all silos, so usually an hour before it notices a new one
[15:56] <ChrisTownsend> robru: Ok, but can I tell if it's actually queued for britney to run or what the status of that job is from there?
[15:56] <ChrisTownsend> robru: Ok, so another case of me being impatient again:)
[15:58] <robru> ChrisTownsend: http://bazaar.launchpad.net/+branch/bileto/view/head:/britney/iterate.py#L39 here's the actual api endpoint uses to iterate over so as long as your ticket matches that, it'll go
[15:58] <ChrisTownsend> robru: Ok, thanks
[15:59] <robru> ChrisTownsend: you're welcome
[16:29] <oSoMoN> plars, hey, the arale-02 slave of the system-apps jenkins instance is down (has been for quite a few days apparently), is it known?
[16:30] <plars> oSoMoN: looking
[16:32] <plars> oSoMoN: looks like it was continually trying to connect and failing for a while there, so it gives up after too many retries. Possibly IS had brought it down for an upgrade or something?
[16:32] <plars> oSoMoN: should be up now
[16:32] <oSoMoN> plars, awesome, thanks!
[16:48] <dobey> robru: maybe change the UI so that it says "Queueing" or something, when there's no other status yet. or ideally changing the lander signoff would immediately trigger a britney run on that silo.
[16:49] <robru> dobey: no can do. When i implemented the britney support initially goal was to run it in parallel but it OOMs with just a couple running, so it has to be limited just one run at a time
[16:50] <robru> dobey: marking it Approved IS queueing it so I'm not sure why that needs extra status
[16:50] <dobey> robru: because the autopkgtests status being totally blank for an hour or more is obviously confusing
[16:51] <dobey> robru: which is why everyone always comes in here and asks what the status is, and you have to reply with the same answer over and over again :)
[16:51] <robru> dobey: people just need to learn
[16:52] <robru> dobey: fine I'll make it say queued.
[16:52] <dobey> robru: i'll remember that the next time design tells me to change some UI :)
[17:29] <robru> dobey: hey can you access the train? looks to me like train (prod + staging) and canonical irc have gone offlien
[17:29] <dobey> robru: irc went down for me too
[17:29] <robru> dobey: I can ssh into wendigo but I can't juju status
[17:29] <dobey> and train seems down as well
[17:30] <robru> dobey: should we ping somebody about this or just assume they've noticed...?
[17:31] <dobey> robru: not sure, but i would presume IS might notice that everyone disconnected from IRC, assuming they are still connected
[17:31] <robru> dobey: this is because I rolled out that 'queued' feature you wanted, took down the whole network! I blame you!
[17:31] <dobey> but given the hour, i'd expect the people on this side of the pond to have noticed it died :)
[17:32] <dobey> robru: hah. i was only suggesting the change, to help you spend less time answering the same requestion repeatedly :)
[17:32] <dobey> although maybe now it will just be "why is my silo 'queued' for an hour?!"
[17:32] <robru> dobey: yup, looking forward to that one
[17:33] <ChrisTownsend> robru: Why is my silo queued for over an hour now?;-)
[17:33]  * robru tears hair out
[17:34] <robru> #is-outage: 09:59:54 <deej> Rolling out CUD r7435, once more with feeling
[17:34] <robru> 10:14:16 Connection closed unexpectedly
[17:34] <robru> heh
[17:34] <ChrisTownsend> robru: But I think having some sort of feedback in that line is better than nothing, so I appreciate the change.
[17:34] <dobey> ChrisTownsend: https://www.youtube.com/watch?v=Day3oxR9Efk
[17:35] <ChrisTownsend> dobey: lol
[17:36] <robru> heh
[18:03] <pmcgowan> dobey, is xenial using qt 5.6
[18:04] <dobey> probably
[18:05] <dobey> pmcgowan: 5.5.1 still it seems
[18:06] <pmcgowan> hmm
[18:06] <pmcgowan> thanks dobey
[18:16] <robru> Ugh, no queuebot
[19:37] <ChrisTownsend> trainguards: I think the xenial i386 britney run is not really running or queued: https://requests.ci-train.ubuntu.com/static/britney/xenial/landing-051/excuses.html
[19:38] <robru> ChrisTownsend: indeed
[19:39] <robru> ChrisTownsend: pitti is the only person i know that can fixit
[19:40] <ChrisTownsend> robru: Ugh, and he's not around.
[19:40] <robru> ChrisTownsend: yeah sorry.
[19:41] <ChrisTownsend> robru: Not your fault.  Thanks.
[19:41] <robru> ChrisTownsend: you're welcome
[20:13] <ChrisTownsend> Wow, no silos are available: https://ci-train.ubuntu.com/job/prepare-silo/793/console
[20:17] <tvoss> robru, o/
[20:17] <robru> tvoss: ahoy
[20:17] <robru> ChrisTownsend: fun times, I'll try to free a couple up
[20:17] <ChrisTownsend> robru: Ok, thanks
[20:17] <tvoss> robru, hey, could copy the packages from https://launchpad.net/~turbo-private/+archive/ubuntu/ppa to silo 41?
[20:17] <robru> tvoss: sure
[20:17] <tvoss> robru, thx
[20:18] <robru> tvoss: that URL 404s tho
[20:18] <tvoss> robru, try again
[20:20] <robru> tvoss: I don't seem to have permission to copy packages from there
[20:20] <tvoss> robru, just gave you access, please try again
[20:21] <robru> tvoss: https://launchpad.net/~turbo-private/+archive/ubuntu/ppa/+packages "not allowed here"
[20:21] <robru> tvoss: considering that I'm about to copy the packages into a public PPA, maybe just make the PPA public temporarily?
[20:28] <robru> ChrisTownsend: ok I freed one try assigning now
[20:28] <ChrisTownsend> robru: Ok, that worked.  Thanks!
[20:29] <robru> ChrisTownsend: you're welcome
[20:34] <dobey> robru: converting a PPA from private to public (or reverse) is not trivial i think.
[20:35] <dobey> seems like people who are asking to copy packages from a private ppa though, should first just copy said packages to a public PPA somewhere, and then ask to copy from the public PPA. or something
[20:51] <robru> dobey: meh, that would trigger an unnecessary rebuild
[20:53] <dobey> robru: why? binary copy is binary copy
[20:53] <robru> dobey: true.
[20:54] <robru> ChrisTownsend: turns out you can get somebody from #ubuntu-release to retry those autopkgtests for you, just link them to the relevant excuses page.
[20:54] <ChrisTownsend> robru: Ah, that's good to know.  I'm glad not just one person holds the keys to that:)
[20:54] <robru> ChrisTownsend: yeah for a while now I thought it was just pitti, so I learned something today ;-)
[20:56] <ChrisTownsend> robru: I sent a general message in there, so hopefully someone is around.  Thanks for pointing that out.
[20:57] <robru> ChrisTownsend: you're welcome
[21:33] <dobey> robru: what the heck. trying to rebuild a silo, and when i click the big build button it just shows me the log of the previous build, and doesn't actually do anything :-/
[21:33] <robru> dobey: try reloading?
[21:34] <dobey> i did
[21:34] <robru> dobey: what ticket?
[21:34] <dobey> robru: 1461
[21:36] <robru> dobey: hmm one sec
[21:37] <robru> dobey: ok I pushed a fix, try again in 5 minutes.
[21:38] <dobey> ok
[21:42] <robru> dobey: any luck?
[21:43] <dobey> robru: seems to be doing stuff now
[21:46] <dobey> robru: thanks
[21:47] <robru> dobey: yay, sorry about that