[00:55] -queuebot:#ubuntu-release- New binary: php-imagick [s390x] (jammy-proposed/universe) [3.4.4+php8.0+3.4.4-2+deb11u2ubuntu3] (no packageset)
[00:55] -queuebot:#ubuntu-release- New binary: php-imagick [amd64] (jammy-proposed/universe) [3.4.4+php8.0+3.4.4-2+deb11u2ubuntu3] (no packageset)
[00:56] -queuebot:#ubuntu-release- New binary: php-imagick [ppc64el] (jammy-proposed/universe) [3.4.4+php8.0+3.4.4-2+deb11u2ubuntu3] (no packageset)
[00:57] -queuebot:#ubuntu-release- New binary: php-imagick [armhf] (jammy-proposed/universe) [3.4.4+php8.0+3.4.4-2+deb11u2ubuntu3] (no packageset)
[00:57] -queuebot:#ubuntu-release- New: accepted ignition-tools [amd64] (jammy-proposed) [1.2.0+ds-2]
[01:00] -queuebot:#ubuntu-release- New binary: php-imagick [arm64] (jammy-proposed/universe) [3.4.4+php8.0+3.4.4-2+deb11u2ubuntu3] (no packageset)
[01:21] -queuebot:#ubuntu-release- New binary: php-imagick [riscv64] (jammy-proposed/universe) [3.4.4+php8.0+3.4.4-2+deb11u2ubuntu3] (no packageset)
[01:59] <bdmurray> RAOF: Could you review livecd-rootfs for hirsute? I uploaded it so can't.
[01:59] <RAOF> Will do
[02:00] <bdmurray> RAOF: and speedtest-cli for bionic - I sponsored that
[02:06] <RAOF> bdmurray: What are we doing about verification for https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1940136 which is keeping the existing livecd-rootfs in hirsute-proposed ATM?
[02:07] <bdmurray> RAOF: Oh, that's due to bug 1949116 which needs addressing. I forgot that was blocking livecd-rootfs.
[02:07] <RAOF> Yeah, I think promoting llvm12 to main in hirsute is the right thing to do there, too.
[02:08] <bdmurray> I'd like tjaalton and sil2100 to look at it though
[02:12] <bdmurray> RAOF: Anyway, speedtest-cli should be much easier. ;-)
[02:16] <RAOF> Yeah. I guess what's happened is mesa has been backported to hirsute, including a llvm bump, but since llvm12 wasn't a new package in hirsute it missed being promoted.
[02:18] -queuebot:#ubuntu-release- New binary: php-pecl-http [ppc64el] (jammy-proposed/universe) [4.0.0+3.2.4+2.6.0-0+deb11u1ubuntu1] (no packageset)
[02:18] -queuebot:#ubuntu-release- New binary: php-pecl-http [s390x] (jammy-proposed/universe) [4.0.0+3.2.4+2.6.0-0+deb11u1ubuntu1] (no packageset)
[02:19] -queuebot:#ubuntu-release- Unapproved: accepted speedtest-cli [source] (bionic-proposed) [2.0.0-1ubuntu1]
[02:20] -queuebot:#ubuntu-release- New binary: php-pecl-http [arm64] (jammy-proposed/universe) [4.0.0+3.2.4+2.6.0-0+deb11u1ubuntu1] (no packageset)
[02:20] -queuebot:#ubuntu-release- New binary: php-pecl-http [armhf] (jammy-proposed/universe) [4.0.0+3.2.4+2.6.0-0+deb11u1ubuntu1] (no packageset)
[02:22] -queuebot:#ubuntu-release- New binary: php-pecl-http [amd64] (jammy-proposed/universe) [4.0.0+3.2.4+2.6.0-0+deb11u1ubuntu1] (no packageset)
[02:44] -queuebot:#ubuntu-release- New binary: php-pecl-http [riscv64] (jammy-proposed/universe) [4.0.0+3.2.4+2.6.0-0+deb11u1ubuntu1] (no packageset)
[05:21] -queuebot:#ubuntu-release- New binary: django-cachalot [amd64] (jammy-proposed/universe) [2.4.3-1] (no packageset)
[05:21] -queuebot:#ubuntu-release- New binary: django-render-block [amd64] (jammy-proposed/universe) [0.8.1-1] (no packageset)
[05:21] -queuebot:#ubuntu-release- New binary: django-maintenance-mode [amd64] (jammy-proposed/universe) [0.16.1-1] (no packageset)
[05:21] -queuebot:#ubuntu-release- New binary: django-select2 [amd64] (jammy-proposed/universe) [7.7.2-1] (no packageset)
[05:22] -queuebot:#ubuntu-release- New binary: django-any-js [amd64] (jammy-proposed/universe) [1.1-1] (no packageset)
[05:22] -queuebot:#ubuntu-release- New binary: django-ckeditor [amd64] (jammy-proposed/universe) [6.1.0+ds-1] (no packageset)
[05:22] -queuebot:#ubuntu-release- New binary: django-dbbackup [amd64] (jammy-proposed/universe) [3.3.0-1] (no packageset)
[05:22] -queuebot:#ubuntu-release- New binary: django-titofisto [amd64] (jammy-proposed/universe) [0.1.2.post1-1] (no packageset)
[05:22] -queuebot:#ubuntu-release- New binary: django-celery-email [amd64] (jammy-proposed/universe) [3.0.0-1] (no packageset)
[05:22] -queuebot:#ubuntu-release- New binary: django-favicon-plus-reloaded [amd64] (jammy-proposed/universe) [1.1.3-1] (no packageset)
[05:22] -queuebot:#ubuntu-release- New binary: django-cleanup [amd64] (jammy-proposed/universe) [5.2.0-1] (no packageset)
[05:22] -queuebot:#ubuntu-release- New binary: django-widget-tweaks [amd64] (jammy-proposed/universe) [1.4.8-1] (no packageset)
[05:23] -queuebot:#ubuntu-release- New binary: django-haystack-redis [amd64] (jammy-proposed/universe) [0.0.1-1] (no packageset)
[05:23] -queuebot:#ubuntu-release- New binary: django-phonenumber-field [amd64] (jammy-proposed/universe) [5.2.0-1] (no packageset)
[05:23] -queuebot:#ubuntu-release- New binary: django-otp-yubikey [amd64] (jammy-proposed/universe) [1.0.0.post1-1] (no packageset)
[05:24] -queuebot:#ubuntu-release- New binary: django-bleach [amd64] (jammy-proposed/universe) [0.9.0-1] (no packageset)
[05:26] -queuebot:#ubuntu-release- New binary: django-menu-generator-ng [amd64] (jammy-proposed/universe) [1.2.3-1] (no packageset)
[05:28] -queuebot:#ubuntu-release- New binary: astap-cli [armhf] (jammy-proposed/universe) [0.9.588-3] (no packageset)
[05:28] -queuebot:#ubuntu-release- New binary: astap-cli [amd64] (jammy-proposed/universe) [0.9.588-3] (no packageset)
[05:29] -queuebot:#ubuntu-release- New binary: astap-cli [ppc64el] (jammy-proposed/universe) [0.9.588-3] (no packageset)
[06:51] <tjaalton> bdmurray, RAOF: added a comment now, promotion is fine
[06:55] <RAOF> Hm. I don't suppose there's a “promote the same subset of binary packages as in $series” tool?
[08:19] <GunnarHj> Hello Release team!
[08:19] <GunnarHj> I got one of those emails about why my uploaded package (vte2.91) is stuck in jammy-proposed for 15 days. The answer is: Because autopkgtests have not been run on ppc64el (and hence can't be retried). AFAICT that answer applies to a bunch of other packages as well.
[08:19] <GunnarHj> My counter-question is: Is anybody investigating why autopkgtests are not running on ppc64el?
[08:21] <RikMills> GunnarHj: yes, I asked this yesterday and juliank has been working hard to sort out runner and networking issues for the ppc64el tests
[08:22] <GunnarHj> RikMills: Great, thanks fro letting me know.
[08:38] <juliank> GunnarHj: We are running now :)
[08:39] <juliank> GunnarHj: We're already down from 22k to 21k items in the queue, hooray
[08:39] <juliank> The hypervisor hosts needed reboots
[08:43] <GunnarHj> Good work juliank! :)
[08:44] <juliank> most of that was IS
[09:54] -queuebot:#ubuntu-release- New binary: golang-github-charmbracelet-glamour [amd64] (jammy-proposed/universe) [0.3.0-2] (no packageset)
[11:00] <laney> juliank: can you re-invite me to that grafana as admin please? to @ubuntu.com. or re-active the account / fix the email address or whatever
[11:00] <laney> re-activate*
[11:03] <juliank> laney: technically I can, but am I allowed to? What does sil2100 think?
[11:03] <juliank> laney: i do want to but I also don't want to make this decision myself :)
[11:04] -queuebot:#ubuntu-release- New: accepted astap-cli [amd64] (jammy-proposed) [0.9.588-3]
[11:04] -queuebot:#ubuntu-release- New: accepted astap-cli [ppc64el] (jammy-proposed) [0.9.588-3]
[11:04] -queuebot:#ubuntu-release- New: accepted django-bleach [amd64] (jammy-proposed) [0.9.0-1]
[11:04] -queuebot:#ubuntu-release- New: accepted astap-cli [armhf] (jammy-proposed) [0.9.588-3]
[11:04] -queuebot:#ubuntu-release- New: accepted django-cachalot [amd64] (jammy-proposed) [2.4.3-1]
[11:04] -queuebot:#ubuntu-release- New: accepted django-any-js [amd64] (jammy-proposed) [1.1-1]
[11:04] <juliank> laney: arguably all of ~ubuntu-release should have access to it IMO
[11:04] -queuebot:#ubuntu-release- New: accepted django-celery-email [amd64] (jammy-proposed) [3.0.0-1]
[11:04] -queuebot:#ubuntu-release- New: accepted django-cleanup [amd64] (jammy-proposed) [5.2.0-1]
[11:04] -queuebot:#ubuntu-release- New: accepted django-favicon-plus-reloaded [amd64] (jammy-proposed) [1.1.3-1]
[11:04] -queuebot:#ubuntu-release- New: accepted django-maintenance-mode [amd64] (jammy-proposed) [0.16.1-1]
[11:04] -queuebot:#ubuntu-release- New: accepted django-otp-yubikey [amd64] (jammy-proposed) [1.0.0.post1-1]
[11:04] -queuebot:#ubuntu-release- New: accepted django-render-block [amd64] (jammy-proposed) [0.8.1-1]
[11:04] -queuebot:#ubuntu-release- New: accepted django-titofisto [amd64] (jammy-proposed) [0.1.2.post1-1]
[11:04] -queuebot:#ubuntu-release- New: accepted golang-github-charmbracelet-glamour [amd64] (jammy-proposed) [0.3.0-2]
[11:04] -queuebot:#ubuntu-release- New: accepted django-ckeditor [amd64] (jammy-proposed) [6.1.0+ds-1]
[11:04] -queuebot:#ubuntu-release- New: accepted django-haystack-redis [amd64] (jammy-proposed) [0.0.1-1]
[11:04] -queuebot:#ubuntu-release- New: accepted django-phonenumber-field [amd64] (jammy-proposed) [5.2.0-1]
[11:04] -queuebot:#ubuntu-release- New: accepted django-widget-tweaks [amd64] (jammy-proposed) [1.4.8-1]
[11:04] -queuebot:#ubuntu-release- New: accepted django-dbbackup [amd64] (jammy-proposed) [3.3.0-1]
[11:04] -queuebot:#ubuntu-release- New: accepted django-select2 [amd64] (jammy-proposed) [7.7.2-1]
[11:04] -queuebot:#ubuntu-release- New: accepted django-menu-generator-ng [amd64] (jammy-proposed) [1.2.3-1]
[11:05] <laney> juliank: I agree, also flavour people to be honest
[11:05] <laney> we deliberately set this up the way we did so community people could be given access
[11:05] <laney> as in, separate influx, no private data should ever be written there
[11:06] <laney> but the initiative never took off as much as I might have liked
[11:06] <laney> not too late for that :-)
[11:06] <laney> btw the "no private data" thing is something to bear in mind if you ever start shipping logs over there
[11:12] <juliank> laney: hmm, so private autopkgtests do they have their own influx db?
[11:13] <laney> no
[11:13] <laney> do we report anything that could be considered a leak?
[11:13] <laney> to influx
[11:13] <juliank> we report package name and series
[11:13] <juliank> so you'll see if there are tests running for openssl on xenial or sth
[11:14] <laney> mmm
[11:14] <laney> check the code, see if we replace the package name or something
[11:14] <laney> we do for /running but not sure for the metrics
[11:15] <juliank> afaict not
[11:16] <juliank> I guess I could (a) hack that in or (b) disable metric submission for private tests, but that'd be nasty
[11:16] <laney> do the same name replacement as we do on running
[11:16] <laney> so you see that *a* test is running, but not what
[11:17] <laney> and don't report exit events? not sure about that
[11:17] <laney> biab
[11:18] -queuebot:#ubuntu-release- New binary: astap [ppc64el] (jammy-proposed/universe) [0.9.588-2] (no packageset)
[11:18] <juliank> it just replaces the entire <name> <params> thing with private job, so I guess it keeps the series
[11:18] <juliank> and arch is in the queue name
[11:18] <juliank> so just replace package name with "private job"
[11:19] <juliank> or not log package name at all?
[11:19] <juliank> we don't log triggers either
[11:19] <juliank> we probably should so you can build dashboards for like kernel autopkgtests
[11:20] <laney> that'd be good
[11:20] -queuebot:#ubuntu-release- New binary: astap [amd64] (jammy-proposed/universe) [0.9.588-2] (no packageset)
[11:20] -queuebot:#ubuntu-release- New binary: astap [arm64] (jammy-proposed/universe) [0.9.588-2] (no packageset)
[11:21] -queuebot:#ubuntu-release- New binary: astap [armhf] (jammy-proposed/universe) [0.9.588-2] (no packageset)
[11:27] -queuebot:#ubuntu-release- New: accepted astap [amd64] (jammy-proposed) [0.9.588-2]
[11:27] -queuebot:#ubuntu-release- New: accepted astap [armhf] (jammy-proposed) [0.9.588-2]
[11:27] -queuebot:#ubuntu-release- New: accepted astap [arm64] (jammy-proposed) [0.9.588-2]
[11:27] -queuebot:#ubuntu-release- New: accepted astap [ppc64el] (jammy-proposed) [0.9.588-2]
[12:02] <juliank> So we ran 1500 tests in the past 6 hours roughly, so I anticipate being done in 20/(1.5/6)/24 < 4 days
[12:03] <juliank> ok more like 1300, but still under 4 days if we keep it up and don't get much more test requests
[12:04] <juliank> It was hard watching yesterday evening when like 70% of the cloud was running upstream systemd CI for like 2-4 hours
[12:04] <juliank> (about 50% of the workers run upstream systemd CI; but well, not 100% of the workers were running)
[12:05] <juliank> I'm considering reducing upstream queue processing to 20% of the workers
[12:05] <juliank> as whoa, those tests run long
[12:13] -queuebot:#ubuntu-release- New binary: django-templated-email [amd64] (jammy-proposed/universe) [3.0.0-1] (no packageset)
[12:15] <laney> there's this problem where force-pushes to a PR trigger multiple runs
[12:15] <laney> it sucks
[12:44] -queuebot:#ubuntu-release- Unapproved: accepted corosync [source] (bionic-proposed) [2.4.3-0ubuntu1.3]
[13:04] <juliank> laney: so, we do cache the amqp queue content in json, and it's fast to parse, so I'm actually working on rejecting duplicate test requests
[13:04] <juliank> laney: with github api, I guess it needs to delete the previosu request, though
[13:05] <juliank> laney: but we can just iterate over the live upstream queue there, it does not really hurt much, it's not long usuually
[13:06] <juliank> or run filter-dupes-upstream minutely
[13:06] <juliank> :D
[13:06] <juliank> but it only helps if we don't already run the test of course, as we do not yet cancel tests
[13:07] <juliank> but every little bit helps, especially when the queues are full and upstream tests don't run immediately
[13:39] <LocutusOfBorg> vorlon, hello, can we please kick dune-pdelab from jammy?
[13:39] <LocutusOfBorg> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976499
[13:40] <LocutusOfBorg> I'm doing a no-change rebuild just to have track of the failure
[13:40] -queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-470-server (hirsute-proposed/restricted) [470.57.02-0ubuntu0.21.04.4 => 470.82.01-0ubuntu0.21.04.1] (i386-whitelist)
[13:40] -queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-470-server (impish-proposed/restricted) [470.57.02-0ubuntu4 => 470.82.01-0ubuntu0.21.10.1] (i386-whitelist)
[13:41] -queuebot:#ubuntu-release- Unapproved: fabric-manager-470 (bionic-proposed/multiverse) [470.57.02-0ubuntu0.18.04.1 => 470.82.01-0ubuntu0.18.04.1] (no packageset)
[13:41] -queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-470-server (focal-proposed/restricted) [470.57.02-0ubuntu0.20.04.4 => 470.82.01-0ubuntu0.20.04.1] (i386-whitelist)
[13:41] -queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-470-server (bionic-proposed/restricted) [470.57.02-0ubuntu0.18.04.4 => 470.82.01-0ubuntu0.18.04.1] (no packageset)
[13:41] -queuebot:#ubuntu-release- Unapproved: libnvidia-nscq-470 (bionic-proposed/multiverse) [470.57.02-0ubuntu0.18.04.1 => 470.82.01-0ubuntu0.18.04.1] (no packageset)
[13:41] -queuebot:#ubuntu-release- Unapproved: libnvidia-nscq-470 (focal-proposed/multiverse) [470.57.02-0ubuntu0.20.04.1 => 470.82.01-0ubuntu0.20.04.1] (no packageset)
[13:41] -queuebot:#ubuntu-release- Unapproved: libnvidia-nscq-470 (hirsute-proposed/multiverse) [470.57.02-0ubuntu0.21.04.1 => 470.82.01-0ubuntu0.21.04.1] (no packageset)
[13:41] -queuebot:#ubuntu-release- Unapproved: libnvidia-nscq-470 (impish-proposed/multiverse) [470.57.02-0ubuntu1 => 470.82.01-0ubuntu0.21.10.1] (no packageset)
[13:41] -queuebot:#ubuntu-release- Unapproved: fabric-manager-470 (focal-proposed/multiverse) [470.57.02-0ubuntu0.20.04.1 => 470.82.01-0ubuntu0.20.04.1] (no packageset)
[13:41] -queuebot:#ubuntu-release- Unapproved: fabric-manager-470 (impish-proposed/multiverse) [470.57.02-0ubuntu1 => 470.82.01-0ubuntu0.21.10.1] (no packageset)
[13:41] -queuebot:#ubuntu-release- Unapproved: fabric-manager-470 (hirsute-proposed/multiverse) [470.57.02-0ubuntu0.21.04.1 => 470.82.01-0ubuntu0.21.04.1] (no packageset)
[14:04] -queuebot:#ubuntu-release- New binary: speech-dispatcher-contrib [s390x] (jammy-proposed/multiverse) [0.10.2-3] (i386-whitelist)
[14:05] -queuebot:#ubuntu-release- New binary: speech-dispatcher-contrib [ppc64el] (jammy-proposed/multiverse) [0.10.2-3] (i386-whitelist)
[14:05] -queuebot:#ubuntu-release- New binary: speech-dispatcher-contrib [amd64] (jammy-proposed/multiverse) [0.10.2-3] (i386-whitelist)
[14:05] -queuebot:#ubuntu-release- New binary: speech-dispatcher-contrib [armhf] (jammy-proposed/multiverse) [0.10.2-3] (i386-whitelist)
[14:06] -queuebot:#ubuntu-release- New binary: speech-dispatcher-contrib [arm64] (jammy-proposed/multiverse) [0.10.2-3] (i386-whitelist)
[14:21] <juliank> laney: so i also considered switching to bar charts instead on grafana and then have stacked abnormal+normal exit, which I did locally and which was super useful (aside from grafana bug where it shows you the data for the wrong bar in hover because the hover is not matching the bars but the range, and in a different way)
[14:22] <laney> juliank: you can make copies of dashboards I think, to try stuff
[14:22] <laney> do that
[14:22] <laney> also, on bugs> stop running a year old version :-)
[14:22] <juliank> yeah I did that yesterday :D
[14:24] <juliank> laney: ah yes, the new one I think also can do transform over tag variables so allows you to calculate the failure rate from two different queries
[14:24] <juliank> right now, you can do that with one panel per arch, obviously doesn't scale :D
[14:25] <laney> yup
[14:29] <bdmurray> sil2100: Could you help fix bug 1949116?
[14:30] -queuebot:#ubuntu-release- New binary: speech-dispatcher-contrib [riscv64] (jammy-proposed/multiverse) [0.10.2-3] (i386-whitelist)
[14:32] -queuebot:#ubuntu-release- Unapproved: rejected pure-ftpd [source] (bionic-proposed) [1.0.46-1ubuntu18.04.1]
[14:41] -queuebot:#ubuntu-release- Unapproved: pure-ftpd (bionic-proposed/universe) [1.0.46-1build1 => 1.0.46-1ubuntu18.04.1] (no packageset)
[14:50] <sil2100> bdmurray: looking o/
[15:02] <sil2100> bdmurray: should be done, also poked the security team with a notice
[15:04] <juliank> Current ppc64el test exit rate is 200 tests / hour
[15:04] <juliank> so 98 hours remaining at current velocity
[15:06] <juliank> so we should be empty next week hopefully :D
[15:06] <juliank> (current rate calculated over last 6 hours)
[15:47] <sergiodj> hi ubuntu-archive, Debian has dropped s390x from the list of supported arches of https://launchpad.net/ubuntu/+source/memkind.  could you please remove the s390x binary from the last build, please?
[15:47] <sergiodj> two pleases just in case ;)
[16:52] -queuebot:#ubuntu-release- Unapproved: ubuntu-dev-tools (focal-backports/universe) [0.176 => 0.185~bpo20.04.1] (no packageset)
[17:24] -queuebot:#ubuntu-release- New binary: bibutils [amd64] (jammy-proposed/universe) [7.1-3] (no packageset)
[17:25] -queuebot:#ubuntu-release- New binary: bibutils [ppc64el] (jammy-proposed/universe) [7.1-3] (no packageset)
[17:29] -queuebot:#ubuntu-release- New binary: bibutils [arm64] (jammy-proposed/universe) [7.1-3] (no packageset)
[17:29] -queuebot:#ubuntu-release- New binary: bibutils [armhf] (jammy-proposed/universe) [7.1-3] (no packageset)
[17:34] -queuebot:#ubuntu-release- New binary: bibutils [riscv64] (jammy-proposed/universe) [7.1-3] (no packageset)
[17:34] -queuebot:#ubuntu-release- New binary: bibutils [s390x] (jammy-proposed/universe) [7.1-3] (no packageset)
[17:54] <xnox> vorlon:  i see that proposed-migration finished at 7am and didn't try a new run today after that?
[17:54] <xnox> is it stuck or is it thinking about live
[17:55] <xnox> is it stuck or is it thinking about life
[18:00] <vorlon> xnox: well, it's definitely stuck, looking to see why
[18:01] <vorlon> xnox: rsync hung and blocked the pipeline; stabbing
[18:12] -queuebot:#ubuntu-release- New: accepted bibutils [amd64] (jammy-proposed) [7.1-3]
[18:12] -queuebot:#ubuntu-release- New: accepted bibutils [armhf] (jammy-proposed) [7.1-3]
[18:12] -queuebot:#ubuntu-release- New: accepted bibutils [riscv64] (jammy-proposed) [7.1-3]
[18:12] -queuebot:#ubuntu-release- New: accepted django-templated-email [amd64] (jammy-proposed) [3.0.0-1]
[18:12] -queuebot:#ubuntu-release- New: accepted speech-dispatcher-contrib [armhf] (jammy-proposed) [0.10.2-3]
[18:13] -queuebot:#ubuntu-release- New: accepted bibutils [arm64] (jammy-proposed) [7.1-3]
[18:13] -queuebot:#ubuntu-release- New: accepted bibutils [s390x] (jammy-proposed) [7.1-3]
[18:13] -queuebot:#ubuntu-release- New: accepted speech-dispatcher-contrib [riscv64] (jammy-proposed) [0.10.2-3]
[18:13] -queuebot:#ubuntu-release- New: accepted bibutils [ppc64el] (jammy-proposed) [7.1-3]
[18:13] -queuebot:#ubuntu-release- New: accepted speech-dispatcher-contrib [arm64] (jammy-proposed) [0.10.2-3]
[18:13] -queuebot:#ubuntu-release- New: accepted speech-dispatcher-contrib [amd64] (jammy-proposed) [0.10.2-3]
[18:13] -queuebot:#ubuntu-release- New: accepted speech-dispatcher-contrib [s390x] (jammy-proposed) [0.10.2-3]
[18:13] -queuebot:#ubuntu-release- New: accepted speech-dispatcher-contrib [ppc64el] (jammy-proposed) [0.10.2-3]
[18:36] -queuebot:#ubuntu-release- Unapproved: rejected xca [source] (focal-backports) [2.3.0-1~ubuntu20.04.1]
[18:37] -queuebot:#ubuntu-release- Unapproved: rejected cockpit-machines [source] (focal-backports) [251-1~ubuntu20.04.1]
[18:37] -queuebot:#ubuntu-release- Unapproved: rejected gramps [source] (focal-backports) [5.1.3-1~ubuntu20.04.1]
[18:38] -queuebot:#ubuntu-release- Unapproved: rejected inxi [source] (bionic-backports) [3.0.24-1-1~ubuntu18.04.1]
[19:00] -queuebot:#ubuntu-release- Unapproved: mutter (impish-proposed/main) [40.5-1ubuntu2 => 40.5-1ubuntu3~21.10.1] (desktop-core, desktop-extra)
[19:21] <LocutusOfBorg> vorlon, hello again, what about libdumbtts on i386?
[19:21] <LocutusOfBorg> speech-dispatcher-contrib wants it...
[19:21] -queuebot:#ubuntu-release- Unapproved: mutter (focal-proposed/main) [3.36.9-0ubuntu0.20.04.1 => 3.36.9-0ubuntu0.20.04.2] (desktop-core, desktop-extra)
[19:45] <xnox> vorlon:  thanks a lot
[19:57] <juliank> looking at 19.79/((19.79-18.99)/6)/24 = 6.2 days
[19:57] <juliank> for ppc64el queue processing based on last 6 hours now
[20:01] <juliank> 22.17/((22.17-18.98)/24)/24 = 6.9 days based on 24 hour value
[20:01] <juliank> it's hard to know how many long tests we ran and how many are pending, so no sensible prediction :D
[20:06] <juliank> experiencing broken bos01
[20:17] <vorlon> coreycb: do you need the networking-arista package still? It has no reverse-dependencies and it's been dropped from Debian
[20:23] <vorlon> LocutusOfBorg: dune-pdelab> removed
[20:24] <jchittum> bdmurray: thanks for LP: 1949116  with that done, i was able to verify Hirsute LP: 1940136
[20:25] <vorlon> sergiodj: memkind/s390x removed
[20:25] <jchittum> and now i'm having an SRU tagging memory lag -- do I need to change the "verification-needed" tag to "verification-done" now that i've done all suites? or should that be someone else?
[20:26] <bdmurray> the non-release specific tag isn't important really
[20:26] <jchittum> ah, ok. I did the release specific one already.
[20:26] <coreycb> vorlon: yes, we can keep networking-arista
[20:26] <vorlon> coreycb: s/can/have to/? :)
[20:27] <bdmurray> let it go
[20:27] <coreycb> vorlon: haha, well we don't *have* to but it's a plugin that can be used with neutron and still actively maintained
[20:28] <sergiodj> vorlon: thanks!
[20:31] <vorlon> LocutusOfBorg: libdumbtts/i386 building
[20:32] <vorlon> coreycb: ok leaving it there
[20:33] <juliank> error rate on bos01 actually seems ok, just occasional issues
[20:34] <juliank> we'll double the workers in bos01 now
[20:34] <juliank> as new nodes have been deployed, giving us extra resources for a couple of days
[20:34] <juliank> (so a 50% increase in capacity)
[20:41] <juliank> up from 40 to 51, 9 still starting
[20:44] -queuebot:#ubuntu-release- Unapproved: accepted pure-ftpd [source] (bionic-proposed) [1.0.46-1ubuntu18.04.1]
[20:49] -queuebot:#ubuntu-release- Packageset: Added libdumbtts to i386-whitelist in jammy
[20:50] <juliank> 55 workers running now
[20:52] <vorlon> \o/
[20:52] <juliank> 57 now even
[20:52] <juliank> almost at full 60
[20:53] <juliank> neutron-api was unhappy about 20 additional clients trying to connect and copy security groups at the same time :D
[20:53] <juliank> so they now start in 5 minute intervals
[20:54] <juliank> wonder if we can configure systemd to start them after each other
[20:54] <juliank> it's a bit messy if you reboot a server and it starts all workers in parallel
[20:57] -queuebot:#ubuntu-release- Unapproved: accepted nvidia-graphics-drivers-470-server [source] (impish-proposed) [470.82.01-0ubuntu0.21.10.1]
[20:58] -queuebot:#ubuntu-release- Unapproved: accepted nvidia-graphics-drivers-470-server [source] (hirsute-proposed) [470.82.01-0ubuntu0.21.04.1]
[20:59] -queuebot:#ubuntu-release- Unapproved: accepted nvidia-graphics-drivers-470-server [source] (focal-proposed) [470.82.01-0ubuntu0.20.04.1]
[20:59] -queuebot:#ubuntu-release- Unapproved: accepted nvidia-graphics-drivers-470-server [source] (bionic-proposed) [470.82.01-0ubuntu0.18.04.1]
[21:04] <juliank> we are now at full 150% ppc64el capacity
[21:04]  * sarnold pushes the turbo button
[21:15] <vorlon> coreycb: also, are you aware of python-crypto's deprecation and removal from Debian?  lots of Ubuntu Openstack packages still depend on it, but Debian does not
[21:15] <vorlon> (and it ftbfs in jammy-proposed)
[21:31] -queuebot:#ubuntu-release- Unapproved: accepted ubuntu-dev-tools [source] (focal-backports) [0.185~bpo20.04.1]
[21:39] <juliank> eww, somebody added 1000 autopkgtest requests :D
[21:43] <coreycb> vorlon: I don't think I've heard that. python-cryptography?
[22:21] <vorlon> coreycb: the source package is python-crypto, it has revdeps of python3-{barbican,ironic-lib,manilaclient,openstackclient,trove}