[05:11] -queuebot:#ubuntu-release- New binary: keras-preprocessing [amd64] (disco-proposed/none) [1.0.5-1] (no packageset)
[05:12] -queuebot:#ubuntu-release- New binary: keras-applications [amd64] (disco-proposed/none) [1.0.6-1] (no packageset)
[07:44] -queuebot:#ubuntu-release- Unapproved: cockpit (cosmic-backports/universe) [183-1~ubuntu18.10.1 => 184-1~ubuntu18.10.1] (no packageset)
[07:46] -queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (cosmic-backports) [184-1~ubuntu18.10.1]
[07:52] -queuebot:#ubuntu-release- New: accepted keras-applications [amd64] (disco-proposed) [1.0.6-1]
[07:52] -queuebot:#ubuntu-release- New: accepted kuttypy [amd64] (disco-proposed) [1.0-2]
[07:52] -queuebot:#ubuntu-release- New: accepted schroedinger-coordgenlibs [amd64] (disco-proposed) [1.1-2]
[07:52] -queuebot:#ubuntu-release- New: accepted schroedinger-coordgenlibs [armhf] (disco-proposed) [1.1-2]
[07:52] -queuebot:#ubuntu-release- New: accepted schroedinger-coordgenlibs [ppc64el] (disco-proposed) [1.1-2]
[07:52] -queuebot:#ubuntu-release- New: accepted keras-preprocessing [amd64] (disco-proposed) [1.0.5-1]
[07:52] -queuebot:#ubuntu-release- New: accepted schroedinger-coordgenlibs [arm64] (disco-proposed) [1.1-2]
[07:52] -queuebot:#ubuntu-release- New: accepted schroedinger-coordgenlibs [s390x] (disco-proposed) [1.1-2]
[07:52] -queuebot:#ubuntu-release- New: accepted lasagne [amd64] (disco-proposed) [0.1+git20181019.a61b76f-1]
[07:52] -queuebot:#ubuntu-release- New: accepted schroedinger-coordgenlibs [i386] (disco-proposed) [1.1-2]
[08:05] <vorlon> Laney: so https://wiki.ubuntu.com/ProposedMigration/AutopkgtestInfrastructure#Worker_administration (before and after my latest edits) said to deploy the armhf lxd hosts using "the latest LTS".  Do you think we should actually do that here?  Should I deploy this new one w/ bionic or xenial?
[08:20] -queuebot:#ubuntu-release- Unapproved: ibm-java80 (xenial-release/partner) [8.0.5.25-0ubuntu1 => 8.0.5.25-0ubuntu1] (no packageset) (sync)
[08:21] -queuebot:#ubuntu-release- Unapproved: ibm-java80 (bionic-release/partner) [8.0.5.22-0ubuntu1 => 8.0.5.25-0ubuntu1] (no packageset) (sync)
[08:34] -queuebot:#ubuntu-release- New: accepted linux-signed-azure-edge [amd64] (bionic-proposed) [4.18.0-1008.8~18.04.1]
[08:34] -queuebot:#ubuntu-release- New: accepted linux-signed-gcp [amd64] (bionic-proposed) [4.15.0-1027.28]
[08:34] -queuebot:#ubuntu-release- New: accepted linux-signed-oracle [amd64] (bionic-proposed) [4.15.0-1008.10]
[08:34] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (bionic-proposed) [4.15.0-1037.39]
[08:34] -queuebot:#ubuntu-release- New: accepted linux-signed-oem [amd64] (bionic-proposed) [4.15.0-1032.37]
[08:36] -queuebot:#ubuntu-release- Unapproved: rejected snapd [source] (bionic-proposed) [2.36.1+18.04]
[08:36] -queuebot:#ubuntu-release- Unapproved: rejected snapd [source] (cosmic-proposed) [2.36.1+18.10]
[08:36] <apw> ^ duplicate in the queue ...
[08:37] -queuebot:#ubuntu-release- Unapproved: rejected snapd [source] (trusty-proposed) [2.36.1~14.04]
[08:37] -queuebot:#ubuntu-release- Unapproved: rejected snapd [source] (xenial-proposed) [2.36.1]
[08:37] -queuebot:#ubuntu-release- New source: ec2-hibinit-agent (bionic-proposed/primary) [1.0.0-0ubuntu1~18.04.0]
[08:37] -queuebot:#ubuntu-release- New source: ec2-hibinit-agent (xenial-proposed/primary) [1.0.0-0ubuntu1~16.04]
[08:37] -queuebot:#ubuntu-release- New source: ec2-hibinit-agent (cosmic-proposed/primary) [1.0.0-0ubuntu1~18.10.0]
[09:08] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (cosmic-proposed) [2.37+18.10]
[10:00] <Laney> juliank sil2100 vorlon: I think we might need to provision another cloud-worker at some point soon (sprint?)
[10:01] <juliank> nice
[10:01] <Laney> load >>80 and I'm seeing failures that look like IO is timing out
[10:01] <Laney> like copying things to/from testbeds
[10:01] <Laney> not sure if there's anything that would prevent that Just Working?
[10:01] <juliank> Laney: oh, I see the emails now too, but they all land in spam
[10:01] <Laney> yes, there is of course
[10:01] -queuebot:#ubuntu-release- Unapproved: ubuntu-geoip (xenial-proposed/main) [1.0.2+14.04.20131125-0ubuntu2 => 1.0.2+14.04.20131125-0ubuntu2.16.04.1] (ubuntu-desktop)
[10:02] <Laney> each instance would think that cloud VMs spawned by the other are orphaned
[10:02] <Laney> and terminate them
[10:04] <vorlon> Laney: and that's not related to the recent switch outage?
[10:05] <Laney> no, it's running 999999 tar processes at the same time
[10:06] <sil2100> Ouch
[10:06] <Laney> I suppose modify the worker to put the owning cloud-worker in the nova instance names
[10:06] <Laney> and then modify the maint script to only consider its own ones
[10:06] <Laney> ?
[10:07] <juliank> sounds right
[10:07] <Laney> anyone fancy it? :-)
[10:08] <Laney> also will need to partition the template instances somehow so each one gets 1/n of them
[10:10] <juliank> hmm
[10:15] <juliank> Laney: So  adt-$RELEASE-$ARCHITECTURE-$PACKAGENAME-$TIMESTAMP becomes  adt-$RELEASE-$ARCHITECTURE-$PACKAGENAME-$TIMESTAMP-$HOSTNAME?
[10:16] <juliank> So you end up with adt-disco-s390x-libreoffice-20190117-060217-juju-prod-ues-proposed-migration-machine-11 as the instance name, which is a bit unwieldy, but easy I guess
[10:17] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (bionic-proposed/main) [2.525.12 => 2.525.13] (desktop-core)
[10:17] <juliank> and then just get the list of instances | grep $HOSTNAME
[10:17] <Laney> right, or the machine-id but at least the hostname is somewhat readable
[10:18] <Laney> yeah, the python equivalent of that :P
[10:18] <juliank> right, that seems easy
[10:18]  * Laney nods
[10:19] <juliank> we should really try to get an autopkgtest-staging.ubuntu.com setup at some point, though
[10:19] <juliank> have it run like 1% of the normal load just to check
[10:19] <juliank> and test new stuff
[10:19] <Laney> right, I would be quite surprised if you could just run ./deploy.sh and get a working setup at this point
[10:20] <Laney> IS would probably want us to move to current juju too *cough*
[10:23] <juliank> Laney: I guess the starting point would be to run deploy with a staging setup, and then diff and fix things up until they are identical
[10:23] <Laney> ye
[10:24] <juliank> Laney: I guess we could also make a staging setup by throwing a bunch of lxd containers together
[10:25] <juliank> or VMs
[10:25] <juliank> like, a local staging setup where you manually run things
[10:26] <juliank> then you commit it to the online staging service, and if it works there, move to production
[10:27] <Laney> we rely on swift, a proper staging environment would need to provide that
[10:27] <Laney> I don't think it'd be a propblem to get one if we asked IS
[10:28] <Laney> I have http://appstream.staging.ubuntu.com/ for the other thing I run (appstream)
[10:28] <Laney> in IS terms it's a mirror of the production one
[10:28] <juliank> right, then we need autopkgtest.staging.ubuntu.com :)
[10:28] <Laney> but there was no problem getting it
[10:28] <juliank> but it would also be fun to setup some sort of local VM deployment, possibly vms inside vms or something (if that works at all)
[10:29] <juliank> then you could even potentially run CI on the cloud setup
[10:29] <Laney> I've run workers locally before by hacking out the swift bits
[10:29] <Laney> it does work
[10:29] <Laney> 1 container for rabbit, 1 worker, start tests with the lxd backend
[10:30] <Laney> quite manual to set up though
[10:32] <juliank> Laney: I think tools/create-nova-image-new-release also needs adjusting for multiple workers, as we'd otherwise generate the same imagies from both
[10:32] <juliank> not sure how that works actually, are they stored on the cloud worker?
[10:33] <juliank> probably on a controller, or whatever nova calls it
[10:34] <Laney> they get uploaded into the cloud itself (glance)
[10:34] <Laney> and yes, that's a good point
[10:35] <juliank> so I guess we'd need one designated worker that builds images
[10:35] <juliank> or split the load
[10:35] <juliank> time to write some cards
[10:35] <Laney> I think juju has the concept of leadership, maybe that's what we want?
[10:36] <Laney> (never used that though, might be off the mark)
[10:38] <juliank> Laney: https://trello.com/c/wvz1NPzD/26-adding-a-second-cloud-worker
[10:39] <Laney> 👍
[10:39] <Laney> (/me makes that board public; wasn't logged in and noticed that it was private)
[11:21] <juliank> Laney: I added a card to the sprint topics to schedule a autopkgtest working session
[11:22] <juliank> in the foundations board, that is
[11:22] <Laney> k00l
[12:51] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (xenial-proposed/main) [4.4.0-142.168] (core, kernel)
[13:03] <sil2100> infinity: hey! Was looking into translation updates for the upcoming bionic point release - I contacted Gunnar asking about the state but he didn't respond, didn't see him online for a while
[13:03] <sil2100> infinity: not sure if we'll have anyone to coordinate a formal testing period, there's no testing schedule set up or anything
[13:04] <sil2100> infinity: was wondering, should we do it by ourselves? Or maybe, like for .1, should we just update all the langpacks?
[13:04] <sil2100> (since usually during formal delta testing only 3-4 languages get tested and updated in the end always)
[13:05] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (xenial-proposed) [4.4.0-142.168]
[13:10] -queuebot:#ubuntu-release- New binary: gnustep-base [s390x] (disco-proposed/universe) [1.26.0-2] (no packageset)
[13:12] -queuebot:#ubuntu-release- New binary: gnustep-base [i386] (disco-proposed/universe) [1.26.0-2] (no packageset)
[13:12] -queuebot:#ubuntu-release- New binary: gnustep-base [ppc64el] (disco-proposed/universe) [1.26.0-2] (no packageset)
[13:19] -queuebot:#ubuntu-release- New binary: gnustep-base [amd64] (disco-proposed/universe) [1.26.0-2] (no packageset)
[13:21] -queuebot:#ubuntu-release- New binary: gnustep-base [arm64] (disco-proposed/universe) [1.26.0-2] (no packageset)
[13:33] -queuebot:#ubuntu-release- New binary: gnustep-base [s390x] (disco-proposed/universe) [1.26.0-2ubuntu1] (no packageset)
[13:34] -queuebot:#ubuntu-release- New binary: gnustep-base [i386] (disco-proposed/universe) [1.26.0-2ubuntu1] (no packageset)
[13:34] -queuebot:#ubuntu-release- New binary: gnustep-base [ppc64el] (disco-proposed/universe) [1.26.0-2ubuntu1] (no packageset)
[13:35] -queuebot:#ubuntu-release- New binary: gnustep-base [amd64] (disco-proposed/universe) [1.26.0-2ubuntu1] (no packageset)
[13:39] -queuebot:#ubuntu-release- New binary: gnustep-base [arm64] (disco-proposed/universe) [1.26.0-2ubuntu1] (no packageset)
[13:40] -queuebot:#ubuntu-release- New binary: gnustep-base [armhf] (disco-proposed/universe) [1.26.0-2ubuntu1] (no packageset)
[13:45] -queuebot:#ubuntu-release- New: accepted gnustep-base [amd64] (disco-proposed) [1.26.0-2]
[13:45] -queuebot:#ubuntu-release- New: accepted gnustep-base [i386] (disco-proposed) [1.26.0-2]
[13:45] -queuebot:#ubuntu-release- New: accepted gnustep-base [s390x] (disco-proposed) [1.26.0-2]
[13:45] -queuebot:#ubuntu-release- New: accepted gnustep-base [arm64] (disco-proposed) [1.26.0-2ubuntu1]
[13:45] -queuebot:#ubuntu-release- New: accepted gnustep-base [i386] (disco-proposed) [1.26.0-2ubuntu1]
[13:45] -queuebot:#ubuntu-release- New: accepted gnustep-base [s390x] (disco-proposed) [1.26.0-2ubuntu1]
[13:45] -queuebot:#ubuntu-release- New: accepted gnustep-base [arm64] (disco-proposed) [1.26.0-2]
[13:45] -queuebot:#ubuntu-release- New: accepted gnustep-base [amd64] (disco-proposed) [1.26.0-2ubuntu1]
[13:45] -queuebot:#ubuntu-release- New: accepted gnustep-base [ppc64el] (disco-proposed) [1.26.0-2ubuntu1]
[13:45] -queuebot:#ubuntu-release- New: accepted gnustep-base [ppc64el] (disco-proposed) [1.26.0-2]
[13:45] -queuebot:#ubuntu-release- New: accepted gnustep-base [armhf] (disco-proposed) [1.26.0-2ubuntu1]
[14:21] -queuebot:#ubuntu-release- Unapproved: update-notifier (bionic-proposed/main) [3.192.1.4 => 3.192.1.5] (ubuntu-desktop, ubuntu-server)
[14:49] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (trusty-proposed/main) [3.13.0-165.215] (core, kernel)
[14:51] -queuebot:#ubuntu-release- New binary: gnustep-gui [s390x] (disco-proposed/universe) [0.27.0-2] (no packageset)
[14:52] -queuebot:#ubuntu-release- New binary: gnustep-gui [ppc64el] (disco-proposed/universe) [0.27.0-2] (no packageset)
[14:53] -queuebot:#ubuntu-release- New binary: gnustep-gui [amd64] (disco-proposed/universe) [0.27.0-2] (no packageset)
[14:55] -queuebot:#ubuntu-release- New binary: gnustep-gui [i386] (disco-proposed/universe) [0.27.0-2] (no packageset)
[14:58] -queuebot:#ubuntu-release- New: accepted gnustep-gui [amd64] (disco-proposed) [0.27.0-2]
[14:58] -queuebot:#ubuntu-release- New: accepted gnustep-gui [ppc64el] (disco-proposed) [0.27.0-2]
[14:58] -queuebot:#ubuntu-release- New: accepted gnustep-gui [i386] (disco-proposed) [0.27.0-2]
[14:58] -queuebot:#ubuntu-release- New: accepted gnustep-gui [s390x] (disco-proposed) [0.27.0-2]
[15:04] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (trusty-proposed) [3.13.0-165.215]
[15:25] <oSoMoN> it looks like the libreoffice autopkgtests in the queue have been consistently timing out for the past 3 days, for all architectures and all series, are there known issues with the infra?
[15:26] <Laney> yes, see what we talked about earlier
[15:30] <Laney> hopefully it picks up over the weekend :/
[16:04] <oSoMoN> Laney, ack, thanks
[16:48] -queuebot:#ubuntu-release- New: accepted ec2-hibinit-agent [source] (cosmic-proposed) [1.0.0-0ubuntu1~18.10.0]
[16:48] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (bionic-proposed) [2.37+18.04]
[16:49] -queuebot:#ubuntu-release- New binary: ec2-hibinit-agent [amd64] (cosmic-proposed/universe) [1.0.0-0ubuntu1~18.10.0] (no packageset)
[16:53] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (xenial-proposed) [2.37]
[16:54] -queuebot:#ubuntu-release- New binary: gnustep-back [i386] (disco-proposed/universe) [0.27.0-2] (no packageset)
[16:54] -queuebot:#ubuntu-release- New binary: gnustep-back [s390x] (disco-proposed/universe) [0.27.0-2] (no packageset)
[16:54] -queuebot:#ubuntu-release- New binary: gnustep-back [ppc64el] (disco-proposed/universe) [0.27.0-2] (no packageset)
[16:55] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (trusty-proposed) [2.37~14.04]
[16:56] -queuebot:#ubuntu-release- New: accepted ec2-hibinit-agent [source] (bionic-proposed) [1.0.0-0ubuntu1~18.04.0]
[16:56] -queuebot:#ubuntu-release- New binary: gnustep-back [amd64] (disco-proposed/universe) [0.27.0-2] (no packageset)
[16:58] -queuebot:#ubuntu-release- New binary: ec2-hibinit-agent [amd64] (bionic-proposed/none) [1.0.0-0ubuntu1~18.04.0] (no packageset)
[17:07] -queuebot:#ubuntu-release- New: accepted gnustep-back [amd64] (disco-proposed) [0.27.0-2]
[17:07] -queuebot:#ubuntu-release- New: accepted gnustep-back [ppc64el] (disco-proposed) [0.27.0-2]
[17:07] -queuebot:#ubuntu-release- New: accepted gnustep-back [i386] (disco-proposed) [0.27.0-2]
[17:07] -queuebot:#ubuntu-release- New: accepted gnustep-back [s390x] (disco-proposed) [0.27.0-2]
[17:08] -queuebot:#ubuntu-release- New: rejected ec2-hibinit-agent [source] (xenial-proposed) [1.0.0-0ubuntu1~16.04]
[17:08] -queuebot:#ubuntu-release- New source: ec2-hibinit-agent (xenial-proposed/primary) [1.0.0-0ubuntu1~16.04.0]
[17:19] <doko> LocutusOfBorg: you did ocaml ABI uploads in the past. do you remember how to resolve the cyclic camomile / ocaml-gettext ?
[17:34] -queuebot:#ubuntu-release- New: accepted ec2-hibinit-agent [source] (xenial-proposed) [1.0.0-0ubuntu1~16.04.0]
[17:42] -queuebot:#ubuntu-release- New binary: ec2-hibinit-agent [amd64] (xenial-proposed/universe) [1.0.0-0ubuntu1~16.04.0] (no packageset)
[18:05] <LocutusOfBorg> doko, never had it...
[18:05] <LocutusOfBorg> what is that?
[18:06] <LocutusOfBorg> not sure, maybe uploading a fake lower version...
[18:31] -queuebot:#ubuntu-release- Unapproved: busybox (bionic-proposed/main) [1:1.27.2-2ubuntu3 => 1:1.27.2-2ubuntu3.1] (core)
[20:35] <tsimonq2> The queues seem to be halted.
[20:35] <tsimonq2> And no, KDE is not to blame (this time). :P
[20:35] <tsimonq2> Laney, vorlon: ^
[20:36] <tsimonq2> (autopkgtests specifically)
[20:42] -queuebot:#ubuntu-release- Unapproved: initramfs-tools (bionic-proposed/main) [0.130ubuntu3.6 => 0.130ubuntu3.7] (core)
[21:11] <Laney> They are being handholded by me
[21:11] <Laney> Don't panic.
[21:22] <teward> tsimonq2: ^ STAY CALM AND DON'T PANIC.  :P
[21:35]  * mwhudson finds his towel
[21:39]  * acheronuk finds his Joo Janta 200 Super-Chromatic Peril Sensitive Sunglasses
[23:14] -queuebot:#ubuntu-release- Unapproved: initramfs-tools (bionic-proposed/main) [0.130ubuntu3.6 => 0.130ubuntu3.7] (core)
[23:22] -queuebot:#ubuntu-release- Unapproved: rejected initramfs-tools [source] (bionic-proposed) [0.130ubuntu3.7]
[23:44] <OldManWinter> Hello, I'm not exactly sure where arch-install-scripts 21-1 is?  Seems it was sync'd, but I don't see it in the queue or in -proposed and rmadison isn't showing it anywhere.