[00:26] <xnox> bdmurray, it looks lost to me. Neither in results nor in /running
[00:26] <xnox> bdmurray, re-request to rerun them?!
[00:35] <ddstreet> bdmurray i understand what the 'ppa' and 'upstream' autopkgtest.u.c queues are, and i think the 'ubuntu' queue, but what's the 'huge' queue?
[00:41] <xnox> ddstreet, ubuntu, but when a single upload triggers more than X number of package tests (10?) then it goes into huge queue for scheduling purposes.
[00:41] <bdmurray> xnox: the tests are running if you look at excuses - https://people.canonical.com/~ubuntu-archive/proposed-migration/disco/update_excuses.html#ubuntu-release-upgrader they just aren't showing up
[00:41] <ddstreet> xnox aha ok thnx :)
[00:41] <xnox> i.e. such that things that only trigger a few tests, sail through a bit quicker.
[00:41] <xnox> bdmurray, yes.... a classic indication of forgotten.
[00:42] <xnox> bdmurray, cause there is nothing on  http://autopkgtest.ubuntu.com/running for it to be, in fact, running.
[01:28] -queuebot:#ubuntu-release- Unapproved: s390-tools (xenial-proposed/main) [1.34.0-0ubuntu8.9 => 1.34.0-0ubuntu8.10] (no packageset)
=== guiverc_d is now known as guiverc
[06:26] -queuebot:#ubuntu-release- Unapproved: ubuntu-report (disco-proposed/main) [1.4.1 => 1.4.2] (ubuntu-desktop)
[06:28] -queuebot:#ubuntu-release- Unapproved: ubuntu-report (bionic-proposed/main) [1.3.0~18.04 => 1.3.1] (no packageset)
[06:51] -queuebot:#ubuntu-release- Unapproved: pentobi (disco-proposed/universe) [16.2-1 => 16.2-1ubuntu0.1] (no packageset)
[07:13] <Laney> xnox: don't give false advice please. tests *should not* get lost and we want to know about it if that happens. there's a lag between results finishing and the website being updated (https://trello.com/c/8XSNcbDH/11-update-information-on-the-web-faster) which probably explains this one
[07:13] <Laney> bdmurray:
[07:14] <Laney> britney is not subject to that lag, so the next time it refreshes it gets the results
[07:28] <Laney> just turned more jobs back on
[07:28] <Laney> 20 per arch now
[08:36] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (disco-proposed/main) [2.578 => 2.578.1] (desktop-core)
[08:37] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (xenial-proposed/main) [4.15.0-1043.47] (kernel)
[08:38] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (cosmic-proposed/main) [2.542.1 => 2.542.2] (desktop-core)
[08:39] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (xenial-proposed) [4.15.0-1043.47]
[08:43] -queuebot:#ubuntu-release- Unapproved: livecd-rootfs (bionic-proposed/main) [2.525.20 => 2.525.21] (desktop-core)
[10:02] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (trusty-proposed/main) [4.15.0-1043.47~14.04.1] (kernel)
=== cpaelzer__ is now known as cpaelzer
[10:44] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (trusty-proposed) [4.15.0-1043.47~14.04.1]
[10:44] <xnox> Laney, hm. it's just the date of the test is like 21:22 utc, and it was not visible on http://autopkgtest.ubuntu.com/packages/ubuntu-release-upgrader/disco/amd64 at like midnight :40 UTC. I am aware of the lag... but i guess the lag is much longer than the "typical" 5..30min.
[10:46] <Laney> no way to check when it was published I'm afraid
[10:46] <Laney> but, lost jobs: we want to know
[10:47] <Laney> you can skip the web interface entirely if you do URL hacking e.g. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/?format=plain&prefix=disco/amd64/u/ubuntu-release-upgrader/
[10:51] <xnox> ack
[10:57] <Laney> I've ramped autopkgtest back up
[10:58] <Laney> going out for a bit now, will check back in later, hopefully it can cope with this
[11:41] -queuebot:#ubuntu-release- New: accepted mariadb-10.1 [amd64] (cosmic-proposed) [1:10.1.38-0ubuntu0.18.10.1]
[11:41] -queuebot:#ubuntu-release- New: accepted mariadb-10.1 [armhf] (cosmic-proposed) [1:10.1.38-0ubuntu0.18.10.1]
[11:41] -queuebot:#ubuntu-release- New: accepted mariadb-10.1 [ppc64el] (cosmic-proposed) [1:10.1.38-0ubuntu0.18.10.1]
[11:41] -queuebot:#ubuntu-release- New: accepted mariadb-10.1 [arm64] (cosmic-proposed) [1:10.1.38-0ubuntu0.18.10.1]
[11:41] -queuebot:#ubuntu-release- New: accepted mariadb-10.1 [s390x] (cosmic-proposed) [1:10.1.38-0ubuntu0.18.10.1]
[11:41] -queuebot:#ubuntu-release- New: accepted mariadb-10.1 [i386] (cosmic-proposed) [1:10.1.38-0ubuntu0.18.10.1]
[12:00] -queuebot:#ubuntu-release- New binary: linux-signed-gcp [amd64] (cosmic-proposed/main) [4.18.0-1010.11] (kernel)
[12:01] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (xenial-proposed/main) [4.4.0-147.173] (core, kernel)
[12:01] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (disco-proposed/main) [5.0.0-1005.5] (core, kernel)
[12:07] -queuebot:#ubuntu-release- New source: dogtag-pki (eoan-proposed/primary) [10.6.10-0ubuntu1]
[12:14] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (xenial-proposed) [4.4.0-147.173]
[12:25] -queuebot:#ubuntu-release- Unapproved: ceph (bionic-proposed/main) [12.2.11-0ubuntu0.18.04.1 => 12.2.11-0ubuntu0.18.04.2] (desktop-core, ubuntu-server)
[12:40] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (disco-proposed) [5.0.0-1005.5]
[12:40] -queuebot:#ubuntu-release- New: accepted linux-signed-gcp [amd64] (cosmic-proposed) [4.18.0-1010.11]
[13:51] <ddstreet> sil2100 do you know what's going on with the mariadb-10.1 autopkgtests?  update_excuses says it's "missing build"...?
[13:51] <ddstreet> mariadb-10.1 for bionic, that is, cosmic seems to be working ok
[13:52] <juliank> Laney: multiple worker WIP https://code.launchpad.net/~juliank/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/366571
[13:54] <juliank> very early, just the basics
[13:56] <sil2100> ddstreet: ah!
[13:56] <sil2100> ddstreet: crap, I approved the binaries for cosmic but didn't for bionic
[13:56] <sil2100> duuuh
[13:56]  * teward finger-wags at sil2100
[13:56] <ddstreet> ah ok, was this the very first non-security update for it in bionic and cosmic?  wow
[13:57] <teward> all those gosh darn binaries xD
[13:57] <teward> ddstreet: might take a while to even get to the migrateable state though - AFAICT autopkgtests are still bleh
[13:57] <teward> which reminds me I see other autopkgtests have completed, any way to see where in the autopkgtest queue some of the nginx-triggered ones are?
[13:57] <teward> or if they got 'killed' and forgotten?
[13:58] <ddstreet> yep, i'll check on it again next week, give it some time :)
[13:58] <sil2100> ddstreet: no no, it's because this added the new binaries, so those are in binNEW
[13:59] <sil2100> Ok, bionic now also approved
[13:59] <ddstreet> thnx!
[14:00] -queuebot:#ubuntu-release- New: accepted mariadb-10.1 [amd64] (bionic-proposed) [1:10.1.38-0ubuntu0.18.04.2]
[14:00] -queuebot:#ubuntu-release- New: accepted mariadb-10.1 [armhf] (bionic-proposed) [1:10.1.38-0ubuntu0.18.04.2]
[14:00] -queuebot:#ubuntu-release- New: accepted mariadb-10.1 [ppc64el] (bionic-proposed) [1:10.1.38-0ubuntu0.18.04.2]
[14:00] -queuebot:#ubuntu-release- New: accepted mariadb-10.1 [arm64] (bionic-proposed) [1:10.1.38-0ubuntu0.18.04.2]
[14:00] -queuebot:#ubuntu-release- New: accepted mariadb-10.1 [s390x] (bionic-proposed) [1:10.1.38-0ubuntu0.18.04.2]
[14:00] -queuebot:#ubuntu-release- New: accepted mariadb-10.1 [i386] (bionic-proposed) [1:10.1.38-0ubuntu0.18.04.2]
[14:01] <juliank> Now it needs implementing leader-elected and leader-settings-changed to enable/disable the cron job for image building
[14:13] <juliank> ok, this looks better
[14:15] <teward> vorlon: mwhudson: I see the status on the SRU for OpenSSL was changed to "Fix Released" but only for the 'main' task and not the Bionic one.  I assume that this is just to indicate that the OpenSSL in $DEVEL is already at that version, and I should pay attention to the Bionic task specifically?
[14:21] <juliank> So, what we're missing (if everything else works) is spreading the number of cloud workers - gotta figure out how many instances of the charm there are
[14:23] <juliank> also spreading out N units across K hosts, and N//K*K potentially being < N
[14:24] <juliank> 5 workers across 2 hosts and 2 per host we end up with 4
[16:44] -queuebot:#ubuntu-release- Unapproved: unattended-upgrades (disco-proposed/main) [1.10ubuntu5 => 1.10ubuntu5.1] (core)
[18:57] -queuebot:#ubuntu-release- Unapproved: ubuntustudio-controls (disco-proposed/universe) [1.7 => 1.7.1] (ubuntustudio)
[20:34] -queuebot:#ubuntu-release- Unapproved: unattended-upgrades (cosmic-proposed/main) [1.5ubuntu3.18.10.3 => 1.5ubuntu3.18.10.4] (desktop-core, ubuntu-server)