=== pieq_ is now known as pieq
=== WrathOfA1hilles is now known as WrathOfAchilles
[05:57]  * enyc meows
[09:20] -queuebot:#ubuntu-release- Unapproved: nvidia-graphics-drivers-460 (hirsute-proposed/restricted) [460.73.01-0ubuntu1 => 460.73.01-0ubuntu1.21.04.1] (core, i386-whitelist)
[09:30] -queuebot:#ubuntu-release- Unapproved: gtk+3.0 (hirsute-proposed/main) [3.24.25-1ubuntu4 => 3.24.25-1ubuntu5] (i386-whitelist, ubuntu-desktop)
[09:33] <guiverc> vorlon, I still haven't noticed the 16.04 ML annoucement
[09:48] <sil2100> Laney: hey! hm hm, where can I find the logic behind running proposed migration (britney2 especially) for specific series? I'm asking since I see that we had no britney2 runs for bionic since the 27th
[09:48] <sil2100> https://people.canonical.com/~ubuntu-archive/proposed-migration/log/bionic/
[09:51] <Laney> sil2100: it starts from archive-reports calling run_proposed_migration
[09:51] <sil2100> Thanks!
[09:51] <Laney> one of those tests is probably failing I guess
[09:51]  * sil2100 digs into that
[09:51] <Laney> at 151
[09:52] <Laney> s/one/all/ !
[09:53] <sil2100> Will find out eventually, this is a good occassion for me to get to know this stuff
[09:54] <Laney> yep, good to know how it fits together
[09:56] <Laney> there's also a lockfile btw, chance that might have gotten stuck
[09:56] <Laney> bin/run-proposed-migration line 38
[09:57] <icey> sil2100: the additional bug you referenced on https://bugs.launchpad.net/cloud-archive/+bug/1923036 should only block Nova, if I'm reading it right?
[09:57] <ubot3> Launchpad bug 1923036 in octavia (Ubuntu Focal) "[SRU] Ussuri stable releases" [Undecided, Fix Committed]
[09:58] <sil2100> Laney: yeah, I just saw that, I see the lockfile is from the 27th
[09:58] <sil2100> So I guess we just need t o remove it
[09:59] <Laney> nod
[09:59] <Laney> check there's no stuck britney process or anything
[09:59] <sil2100> icey: yes, but we usually release the whole stack at once - is it safe to leave out nova in -proposed but release the rest?
[10:00] <sil2100> Laney: none for bionic at least
[10:00] <icey> sil2100: that should be OK for the OpenStack point releases, as the various projects don't release them in any kind of coordinated fashion, in general
[10:00] <Laney> sil2100: good, then go ahead and remove, it should run I guess/hope
[10:02] <sil2100> icey: good to know! Let me release those in a moment then ;)
[10:02] <icey> thanks sil2100! I got poked on Monday about another Neutron bug for Focal so I wanted to see if I could progress this :)
[11:06] <sil2100> icey: yw!
[11:06] <sil2100> Laney: yay, it's running now o/
[11:07] <Laney> w00t
[11:07] <sil2100> rbalint: hey! Do you know when we can expect systemd 248 in impish? I see it's still not imported into Debian
[11:14] -queuebot:#ubuntu-release- New binary: ssshtest [amd64] (impish-proposed/none) [0.0+git20190416.6f5438a-1] (no packageset)
[12:27] <ddstreet> icey for neutron are you referring to lp: #1832021? just asking to see if you are planning to sponsor it, if you're too busy i can help with sponsoring
[12:27] <ubot3> Launchpad bug 1832021 in neutron (Ubuntu Bionic) "Checksum drop of metadata traffic on isolated networks with DPDK" [Medium, New] https://launchpad.net/bugs/1832021
[12:29] <icey> ddstreet: it looks like there's a Neutron upload from yesterday that's accepted into bionic-proposed with three bugs attached already; coreycb I don't remember if you wanted me to grab ^ as well or if you were?
[12:31] <icey> ah ddstreet - that's not the bug I was thinking of
[12:31] <icey> ddstreet: so no summary on that yet, this is the first I'm seeing it
[12:33] <ddstreet> well i just was told of another neutron bug, lp: #1883089
[12:33] <ubot3> Launchpad bug 1883089 in neutron (Ubuntu Focal) "[L3] floating IP failed to bind due to no agent gateway port(fip-ns)" [Undecided, New] https://launchpad.net/bugs/1883089
[12:35] <ddstreet> icey i'm sure dosaboy will sync with you guys on these, and we're happy to help with sponsoring/uploading if you're all busy
[12:35] <icey> ddstreet: indeed, Monday's the normal sync day
[12:36] <icey> I intend to upload the change for 3089 to Focal in a few, verifying that it builds correctly
[12:53] <jamespage> lukasm: if you have cycles there are a couple of ceph uploads in the focal and groovy UNAPPROVED queues which drop the patch which failed verficiation in the current -proposed versions
[12:54] <lukasm> jamespage: I guess that is directed to sil2100
[12:54] <jamespage> doh yes
[12:54] <jamespage> ETOMANYCONVERSATIONS
[12:55] <lukasm> and ETOMANYLUKAS[Z]s
[13:06] <sil2100> o/
[13:06] <sil2100> heh
[13:21] <rbalint>  sil2100 re:systemd 248: i'd like to migrate 247.3-5ubuntu1 first and then land 248 which is being tested in https://bileto.ubuntu.com/#/ticket/3840
[13:21] <rbalint> sil2100, looking at the arm64 queue the optimistic ETA is mid next week
=== alan_g_ is now known as alan_g
[13:25] <sil2100> rbalint: thanks for the update! That works
[13:25] <sil2100> jamespage: on it in a moment o/
[13:26] <jamespage> sil2100: thanks muchly :)
[13:38] -queuebot:#ubuntu-release- Unapproved: neutron (focal-proposed/main) [2:16.3.1-0ubuntu1 => 2:16.3.1-0ubuntu1.1] (openstack, ubuntu-server)
[13:55] -queuebot:#ubuntu-release- Unapproved: linux-firmware-raspi2 (focal-proposed/multiverse) [3-0ubuntu2~20.04.1 => 4-0ubuntu0~20.04.1] (raspi)
[13:56] <doko> Laney, juliank: arm64 autpkg test queue is still filling up. any estimate when we'll see more capacity?
[13:56] <Laney> I'm trying
[13:58] <Laney> I've been asking IS to help out, and they have to be fair, hopefully the slope should look better soon
[14:00] <doko> nice
[14:02] <waveform> Laney, juliank -- more optimizations for publish-db proposed here: https://code.launchpad.net/~waveform/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/402343 -- do let me know if anything's too obscure/requires more explanation, and obviously feel free to ignore if you're too busy!
[14:03] <Laney> waveform: nice, thanks, on first glance it looks like good educational material for me too!
[14:03] <Laney> will try to get to it at some point™
[14:08] <juliank> waveform: looks good to me, need to apply in staging and see if there are any bugs :D (CC Laney - shall I do that?)
[14:10] <Laney> if you're confident in your review :p
[14:11] <juliank> Laney: the staging change is part of the review :D
[14:11] <juliank> but yes
[14:11] <Laney> you can release into edge if you want, no problemo
[14:12] <juliank> did that :D
[14:27] <sil2100> jamespage: ouch! hm, could you re-upload ceph either when building with -v (but you'd have to leave out this one LP bug  that failed verification somehow) or with a changelog entry that has the LP bugs to verify? Since right now the .changes file has no launchpad bugs attached
[14:27] <sil2100> So we can't really accept it as it would be unverifiable
[14:29] <juliank> Laney: $ time curl -o /dev/null -s https://autopkgtest.ubuntu.com/statistics
[14:29] <juliank> real    1m1,718s
[14:30] <juliank> People can make us spend a lot of CPU time on this
[14:32] <juliank> waveform: It seems in browse.cgi there are a lot of queries matching WHERE test.id == result.test_id [...], but result.test_id has no index :)
[14:34] <juliank> I should add an index on that, maybe change the field to say it's a foreign key but meh
[14:34] <waveform> juliank, there *sort of* is in that test_id is at the front of the PK on the result table. Now, while that's not quite as good as an index solely on test_id itself, prefixes of indexes can still be used for query optimization
[14:34] <waveform> in other words adding such an index might be a gain but it'd be a small one and you'd likely lose that gain to the maintenance of that additional index itself
[14:34] <juliank> waveform: oh i see
[14:36] <juliank> maybe we should just add caching for /statistics in the haproxy, as that one can be used to DoS us easily I guess
[14:36] <juliank> Made 4 requests and workers now run at 100% CPU
[14:36] <juliank> yay
[14:37] <juliank> waveform: This can't be fast, though: SELECT DISTINCT release from test'
[14:37] <juliank> followed by SELECT DISTINCT arch from test WHERE release=?
[14:37] <juliank> for each release
[14:38] <juliank> Also can't I just select DISTINCT (release, arch) from test?
[14:38] <waveform> oh yeah - I noticed that one and thought SELECT DISTINCT arch, release FROM test would be much preferable
[14:38] <waveform> yes - no need for the parentheses though (DISTINCT is a SELECT level option, not field level)
[14:38] <waveform> and then you can ditch that loop obviously
[14:40] -queuebot:#ubuntu-release- Unapproved: rejected ceph [source] (groovy-proposed) [15.2.11-0ubuntu0.20.10.2]
[14:41] <sil2100> xnox: looking at your DKMS rebuild batch!
[14:41] -queuebot:#ubuntu-release- Unapproved: rejected ceph [source] (focal-proposed) [15.2.11-0ubuntu0.20.04.2]
[14:44] <juliank> waveform: The next two queries at https://git.launchpad.net/~juliank/autopkgtest-cloud/tree/charms/focal/autopkgtest-web/webcontrol/browse.cgi#n350 can be merged into one too
[14:46] <juliank> and "number of packages with tests that pass" at the end I don't see need to first extract source versions for each release, and then do a loop over release x arch and big query for each of them
[14:46] <waveform> hmm, the GROUP BY might be an issue there but I'll have a look (oh, and I'll get rid of that WHERE == too - urgh :)
[14:47] <juliank> waveform: The group by is fine, just that we get multiple rows that we need to add together because they are now grouped by exitcode too
[14:48] <jamespage> sil2100: ack - I'll do with -v and then we can drop the verification requirement for the bug reverted
[14:49] <waveform> juliank, okay -- I'll have a play with it in a mo, and yes - I think you're correct about the later big-query-in-a-loop
[14:50] <juliank> So much sadness
[14:53] -queuebot:#ubuntu-release- Unapproved: ceph (groovy-proposed/main) [15.2.11-0ubuntu0.20.10.1 => 15.2.11-0ubuntu0.20.10.2] (ubuntu-desktop, ubuntu-server)
[14:54] -queuebot:#ubuntu-release- Unapproved: ceph (focal-proposed/main) [15.2.11-0ubuntu0.20.04.1 => 15.2.11-0ubuntu0.20.04.2] (desktop-core, ubuntu-server)
[14:59] <sil2100> jamespage: yeah, that could work, but we'll have to remember to switch it back to not fixed once we release the SRU
[15:01] <jamespage> sil2100: agreed :)
[15:15] -queuebot:#ubuntu-release- Unapproved: accepted acpi-call [sync] (focal-proposed) [1.1.0-5ubuntu0.2]
[15:16] -queuebot:#ubuntu-release- Unapproved: accepted backport-iwlwifi-dkms [sync] (focal-proposed) [8324-0ubuntu3~20.04.3]
[15:16] -queuebot:#ubuntu-release- Unapproved: accepted bcmwl [sync] (focal-proposed) [6.30.223.271+bdcom-0ubuntu7~20.04.2]
[15:17] -queuebot:#ubuntu-release- Unapproved: accepted dahdi-linux [sync] (focal-proposed) [1:2.11.1~dfsg-1ubuntu6.2]
[15:18] -queuebot:#ubuntu-release- Unapproved: accepted dm-writeboost [sync] (focal-proposed) [2.2.9-1ubuntu1.2]
[15:20] -queuebot:#ubuntu-release- Unapproved: accepted evdi [sync] (focal-proposed) [1.7.0+dfsg-1ubuntu1~20.04.3]
[15:21] <jamespage> sil2100: both uploaded with -v so the changelog includes the previous entry aswell
[15:21] -queuebot:#ubuntu-release- Unapproved: accepted gost-crypto [sync] (focal-proposed) [0.3.2-2ubuntu0.2]
[15:22] -queuebot:#ubuntu-release- Unapproved: accepted iptables-netflow [sync] (focal-proposed) [2.4-2ubuntu0.3]
[15:25] -queuebot:#ubuntu-release- Unapproved: accepted liblzf [sync] (focal-proposed) [3.6-2~ubuntu1.20.04.2]
[15:26] -queuebot:#ubuntu-release- Unapproved: accepted lime-forensics [sync] (focal-proposed) [1.9-1ubuntu0.2]
[15:30] -queuebot:#ubuntu-release- Unapproved: accepted lttng-modules [sync] (focal-proposed) [2.12.2-1ubuntu1~20.04.2]
[15:30] -queuebot:#ubuntu-release- Unapproved: accepted nvidia-graphics-drivers-340 [sync] (focal-proposed) [340.108-0ubuntu5.20.04.2]
[15:32] -queuebot:#ubuntu-release- Unapproved: accepted oss4 [sync] (focal-proposed) [4.2-build2010-5ubuntu6~20.04.2]
[15:33] -queuebot:#ubuntu-release- Unapproved: accepted r8168 [sync] (focal-proposed) [8.048.00-1ubuntu0.20.04.2]
[15:34] -queuebot:#ubuntu-release- Unapproved: accepted rtl8812au [sync] (focal-proposed) [4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2]
[15:34] -queuebot:#ubuntu-release- Unapproved: accepted sysdig [sync] (focal-proposed) [0.26.4-1ubuntu0.3]
[15:35] -queuebot:#ubuntu-release- Unapproved: accepted v4l2loopback [sync] (focal-proposed) [0.12.3-1ubuntu0.4]
[15:36] -queuebot:#ubuntu-release- Unapproved: accepted virtualbox [sync] (focal-proposed) [6.1.16-dfsg-6~ubuntu1.20.04.2]
[15:37] -queuebot:#ubuntu-release- Unapproved: accepted virtualbox-hwe [sync] (focal-proposed) [6.1.16-dfsg-6ubuntu1.20.04.2]
[15:39] -queuebot:#ubuntu-release- Unapproved: accepted zfs-linux [sync] (focal-proposed) [0.8.3-1ubuntu12.9]
[15:40] <juliank> Laney: doko mentioned we should skip running tests triggered by build-essential
[15:40] <juliank> or well, britney shouldn't trigger tests for build-essential
[15:48] -queuebot:#ubuntu-release- Unapproved: rejected shim-signed [source] (hirsute-proposed) [1.46.1]
[15:48] -queuebot:#ubuntu-release- Unapproved: rejected shim [sync] (hirsute-proposed) [15.4-0ubuntu2]
[15:49] <xnox> ok
[16:00] -queuebot:#ubuntu-release- Unapproved: ceph (groovy-proposed/main) [15.2.11-0ubuntu0.20.10.1 => 15.2.11-0ubuntu0.20.10.2] (ubuntu-desktop, ubuntu-server)
[16:01]  * blackboxsw sil2100: thanks for the review on ua-tools 27.0 to Bionic++. I added the comment  about known PPC and riscv package build failures due to goloang dependency issues. We plan to fix this in 27.1. I'm checking on whether this is considered an SRU blocker
[16:02] <sil2100> jamespage: ...ok, so I actually hand tinkered .changes file for the ceph uploads so that we don't have to remember about this one reverted bug!
[16:04] -queuebot:#ubuntu-release- Unapproved: rejected ceph [source] (groovy-proposed) [15.2.11-0ubuntu0.20.10.2]
[16:14] -queuebot:#ubuntu-release- Unapproved: ceph (focal-proposed/main) [15.2.11-0ubuntu0.20.04.1 => 15.2.11-0ubuntu0.20.04.2] (desktop-core, ubuntu-server)
[16:16] -queuebot:#ubuntu-release- Unapproved: rejected ceph [source] (focal-proposed) [15.2.11-0ubuntu0.20.04.2]
[16:20] -queuebot:#ubuntu-release- Unapproved: accepted ceph [source] (groovy-proposed) [15.2.11-0ubuntu0.20.10.2]
[16:22] -queuebot:#ubuntu-release- Unapproved: accepted ceph [source] (focal-proposed) [15.2.11-0ubuntu0.20.04.2]
[16:24] <sil2100> xnox: ok, so I'm reviewing shim for hirsute - since this is a special snowflake I'll accept it as is, but could you take a look at the SRU bugs and make sure those are verifiable and verified?
[16:25] -queuebot:#ubuntu-release- Unapproved: accepted shim [sync] (hirsute-proposed) [15.4-0ubuntu2]
[16:27] -queuebot:#ubuntu-release- Unapproved: accepted shim-signed [sync] (hirsute-proposed) [1.47]
[16:28] -queuebot:#ubuntu-release- Unapproved: rejected shim-signed [sync] (groovy-proposed) [1.46]
[16:28] -queuebot:#ubuntu-release- Unapproved: rejected shim [sync] (groovy-proposed) [15.4-0ubuntu1]
[17:24] <xnox> sil2100:  will do.
[18:22] <bryce> ubuntu-archive: we can go ahead and let php8.0 into impish, I plan to start working on the transition.  (lp: #1927288)
[18:22] <ubot3> Launchpad bug 1927288 in php8.0 (Ubuntu) "Please enable php8.0 in Ubuntu 21.10" [Undecided, New] https://launchpad.net/bugs/1927288
[18:25] <doko> bryce: sure, there are no other transitions ongoing. would be nice to mention this transiton and also others in the impish release schedule
[18:38] <bryce> doko yes that would be nice
[18:39] <bryce> doko I've drafted my plan here, if it is worth linking:  https://wiki.ubuntu.com/ServerTeam/Transition/Php8.0
[18:40] <doko> bryce: please do in the second table in https://discourse.ubuntu.com/t/impish-indri-release-schedule/18540
[19:40] <bryce> doko done tentatively; obviously when the transition can be done depends on when php8.0 becomes available in the archive
[21:17] <mwhudson> vorlon: did you look into the initramfs-tools autopkgtest failures after your merge at all?
[21:20] <mwhudson> also imports of the package appear to be stuck :(
[21:26] <mwhudson> (not meant to be any kind of oblique dig, i just want any information you have!)
=== tomreyn_ is now known as tomreyn