[00:47] <bdmurray> \o/
[00:52] <xnox> bdmurray:  vorlon: please hint https://people.canonical.com/~ubuntu-archive/proposed-migration/impish/update_excuses.html#tp-smapi to migrate. It is being restricted from arch:all to arch:amd64 and thus will never pass arm64 autopkgtest anymore.
[00:52] <xnox> which is currently held up as a regression
[00:54] <bdmurray> xnox: doing so
[01:06] <xnox> thanks!
[01:07] <xnox> bdmurray:  poked src:linux adt-matrix results. Lots of missing. And hinted over linux-aws one, which should get unblocked now too.
[04:32] -queuebot:#ubuntu-release- Unapproved: testssl.sh (impish-proposed/universe) [3.0.5+dfsg1-1 => 3.0.6+dfsg1-1] (no packageset) (sync)
[04:33] -queuebot:#ubuntu-release- Unapproved: accepted testssl.sh [sync] (impish-proposed) [3.0.6+dfsg1-1]
[06:10] <sigv> If an upload was sponsored, as noted by "Unapproved: gist (focal-proposed/universe) [5.0.0-4 => 5.0.0-4ubuntu1]" above, but there is no "verification pending" message on LP: #1940907 -- should I be worried? Is there some hidden step between "sponsor upload" and "start SRU verification process" which was lost along the way here?
[06:45] <juliank> We haven't built an impish image on amd64 lgw since the 28th, it got stuck on the 29th, restarted the process now
[06:50] -queuebot:#ubuntu-release- Unapproved: knockpy (impish-proposed/universe) [5.1.0-1 => 5.2.0-1] (no packageset) (sync)
[06:50] -queuebot:#ubuntu-release- Unapproved: vim-bitbake (impish-proposed/universe) [0~git20200915-1 => 0~git20210803-1] (no packageset) (sync)
[06:51] -queuebot:#ubuntu-release- Unapproved: accepted knockpy [sync] (impish-proposed) [5.2.0-1]
[06:51] -queuebot:#ubuntu-release- Unapproved: accepted vim-bitbake [sync] (impish-proposed) [0~git20210803-1]
[06:58] <juliank> A new autopkgtest image for impish amd64 has been built on lgw01 now, so both amd64 clouds are running uptodate images now
[07:18] -queuebot:#ubuntu-release- Unapproved: dkms (impish-proposed/main) [2.8.4-4ubuntu1 => 2.8.7-1] (i386-whitelist, ubuntu-desktop) (sync)
[08:05] <sil2100> I'll disable 21.10 dailies for now o/
[08:06] <sil2100> We still don't have all we need for release candidates, but we might have stuff migrating soon
[08:46] -queuebot:#ubuntu-release- Unapproved: base-files (impish-proposed/main) [11.1ubuntu4 => 11.1ubuntu5] (core, i386-whitelist)
[08:57] <seb128> sil2100, what's the deal with the arm64 autopkgtest backlog? we still have 160 desktop packages on https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html that need to migrate
[09:03] -queuebot:#ubuntu-release- Unapproved: accepted base-files [source] (impish-proposed) [11.1ubuntu5]
[09:03] <RAOF> sigv: the upload was sponsored into the focal-unapproved queue. The next step is an SRU team member processing the queue and accepting it into -proposed.
[09:30] <sil2100> seb128: we're working on getting it down for now, we'll be dropping quite a few that we think are irrelevant from the backlog in a moment
[09:30] <sil2100> It's still the fallback fron the no-change rebuilds sadly
[09:39] -queuebot:#ubuntu-release- Unapproved: unity-tweak-tool (impish-proposed/universe) [0.0.7+-0ubuntu8 => 0.0.7+-0ubuntu9] (no packageset)
[09:40] -queuebot:#ubuntu-release- Unapproved: accepted unity-tweak-tool [source] (impish-proposed) [0.0.7+-0ubuntu9]
[09:42] <juliank> We are skipping autopkgtests for various no-change zstd rebuilds of meta packages like java-common and  ruby-defaults
[09:42] <juliank> arm64 queues are _long_ :(
[09:53] <juliank> seb128: We now have about 2k tests remainining, it was 3k before I dropped the metapackage-triggered runs
[09:53] <juliank> seb128: I can't find anything other that's skippable
[10:00] -queuebot:#ubuntu-release- Unapproved: libfprint (impish-proposed/main) [1:1.90.7+git20210222+tod1-0ubuntu3 => 1:1.90.7+git20210222+tod1-0ubuntu4] (ubuntu-desktop)
[10:07] <xnox> juliank:  OSError: [Errno 28] No space left on device i see that quite often on a few amd64 adt results. Have our base images run out of space?!
[10:08] <xnox> or is it from the worker?
[10:08] <xnox> https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/a/aflplusplus/20211010_174430_79d60@/log.gz
[10:08] <juliank> xnox: no, the cloud worker yesterday, I fixed it overnight
[10:10] <xnox> juliank:  ack, will retry things like that then.
[10:16] <sigv> RAOF: got it. Thank you for the information.
[10:31] <icey> can the upload of Neutron that's been in the unapproved queue for Focal since the first possibly be accepted into proposed?
[10:51] -queuebot:#ubuntu-release- Unapproved: libfprint (focal-proposed/main) [1:1.90.2+tod1-0ubuntu1~20.04.4 => 1:1.90.2+tod1-0ubuntu1~20.04.5] (desktop-core, ubuntu-desktop)
[11:36] <locutusofborg> bdmurray, hello ping to release LP: #1944744?
[13:19] <utkarsh2102> bdmurray: can you also TAL at LP: #1946649, please? :)
[13:20] <utkarsh2102> ubuntu-archive: I've filed LP: #1946649/azure-cli for removal. If time permits, could you please TAL? Becuase this needs to be removed before we release Impish.
[13:21] <bdmurray> utkarsh2102: I'm not an AA but have pinged one for you
[13:25] <pieq> Hello! Has the RC of 21.10 been released yet? I can only find a link to the beta image: https://cdimage.ubuntu.com/ubuntu/releases/21.10/
[13:25] <sil2100> pieq: hey! Not yet!
[13:25] <sil2100> pieq: we will most possibly be spinning release candidate images somewhat later today
[13:26] <sil2100> https://discourse.ubuntu.com/t/impish-indri-21-10-release-status-tracking/24478
[13:26] <sil2100> (for the most up-to-date info!)
[13:26] <pieq> Good to know. Thanks sil2100!
[13:26]  * apw is looking
[13:26] <pieq> It's late here. if for any reason RC is not ready within 12 hours, do you recommend I use the latest beta, or the latest daily build?
[13:27] <bdmurray> pieq: use for what?
[13:28] <pieq> bdmurray: sorry, forgot to mention. QA on a device that was certified with 20.04
[13:29] <xnox> pieq: even the daily does not yet have the kernel we want to ship.
[13:30] <xnox> it has just migrated. so you do want at least a newer built than whatever is the current timestamp.
[13:30] <pieq> xnox: thanks for the info. In that case I'll get whatever is newer, tomorrow morning my time (Asia/Taipei) :)
[13:35] <utkarsh2102> bdmurray: as always, thanks a bunch! \o/
[14:06] <paride> sil2100, https://bugs.launchpad.net/ubuntu-cdimage/+bug/1946656
[14:23] <sil2100> paride: thanks!
[14:24] <paride> dbungert, I added a subiquity task to https://bugs.launchpad.net/subiquity/+bug/1946656 as I think it affects subiquity self-refresh
[14:24] <paride> I think that really needs confirmation from a second person
[14:25] <bdmurray> sil2100: Do you know anything about the status of the uploads in the Impish queue? The only thing we have notes on is ubuntu-advantage-tools
[14:35] <sil2100> bdmurray: I only briefly looked at it this morning, not sure what's the status with thunderbird
[14:36] <bdmurray> I think oSoMoN had pinged about that some time ago
[14:37] <sil2100> ukui-media looks like something I'd be willing to accept, since we have an ukui-media in -propsoed that FTBFS
[14:37] <sil2100> I don't know if Steve or someone reviewed it before?
[14:38] <sil2100> Thunderbird that is
[14:38] <sil2100> The gimp sync I guess I'll reject
[14:38] <sil2100> Since that's actually a bump of 4 version numbers
[14:40] -queuebot:#ubuntu-release- Unapproved: rejected gimp [sync] (impish-proposed) [2.10.28-1]
[14:40] <oSoMoN> sil2100, thunderbird is tracked by bug #1946098, it's a bugfix release, up to you but it's fine for a 0-day SRU if you prefer
[14:41] <oSoMoN> accepting it would mean we have a fully up-to-date thunderbird in the release on day 1
[14:51] <sil2100> oSoMoN: I think at this stage I'd prefer to maybe 0-day it or similar
[14:51] -queuebot:#ubuntu-release- Unapproved: accepted ukui-media [sync] (impish-proposed) [3.0.3.1-1]
[14:51] <oSoMoN> sil2100, yeah, that's reasonable
[15:00] -queuebot:#ubuntu-release- Unapproved: libunity (impish-proposed/main) [7.1.4+19.04.20190319-5build1 => 7.1.4+19.04.20190319-6] (ubuntu-desktop)
[15:02] <dbungert> paride: thanks, I will investigate this morning
[15:03] <sil2100> dbungert: I pinged both the snapd and snapstore teams about this
[15:03] <sil2100> I'm starting to think it might have been a snapstore issue, maybe temporary even?
[15:04] <dbungert> sil2100: thanks for that, I still want to look and attempt to rule out Subiquity from this
[15:06] <sil2100> THanks!
[15:10] <sil2100> dbungert: ok, I think this is a snapstore issue
[15:10] <dbungert> OK
[15:10] <sil2100> They mentioned having to throttle the sections API endpoint
[15:11] <sil2100> So let's get back to it after a while once I get a green light from them - if we still have an issue, we can then dig deeper
[15:11] <dbungert> sil2100: sounds perfect
[15:51] <bdmurray> Is the ubiquity task on bug 1943816 valid?
[15:56] <bdmurray> Could an AA clear out the NBS list? https://people.canonical.com/~ubuntu-archive/nbs.html
[15:59] <sil2100> bdmurray: on it o/
[16:14] <bdmurray> Trevinho: is libfrpint good as an SRU?
[16:15] <sil2100> Ok, putting the freeze block in place now
[16:36] <dbungert> The patch on LP: #1942648 looks good, I suggest merging.
[16:39] <bdmurray> dbungert: looks good or tests well? ;-)
[16:39] <dbungert> Both :)
[16:40] <bdmurray> that's better!
[16:40] <dbungert> hard to beat a one-liner patch
[16:47] <juliank> seb128 really needs a bouncer :/
[16:50] <bdmurray> Okay, I'll commit the ubiquity change - thanks for testing!
[17:01] -queuebot:#ubuntu-release- Unapproved: accepted neutron [source] (focal-proposed) [2:16.4.1-0ubuntu2]
[17:36] -queuebot:#ubuntu-release- Builds: Ubuntu Budgie Desktop amd64 [Impish Final] (20211011) has been added
[17:47] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Impish Final] (20211011) has been added
[17:48] -queuebot:#ubuntu-release- Builds: Lubuntu Desktop amd64 [Impish Final] (20211011) has been added
[17:54] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Impish Final] (20211011.1) has been added
[17:54] -queuebot:#ubuntu-release- Builds: Xubuntu Desktop amd64 [Impish Final] (20211011.1) has been added
[17:55] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop arm64+raspi [Impish Final] (20211011.1) has been added
[17:58] -queuebot:#ubuntu-release- Builds: Ubuntu MATE Desktop amd64 [Impish Final] (20211011.1) has been added
[18:01] -queuebot:#ubuntu-release- Builds: Ubuntu Studio DVD amd64 [Impish Final] (20211011) has been added
[18:02] -queuebot:#ubuntu-release- Builds: Ubuntu Desktop amd64 [Impish Final] (20211011.1) has been added
[18:02] <dbungert> so I'm looking into this LP: #1946668
[18:25] <sil2100> dbungert: hm, the thing I mentioned that could be a snapstore issue is still creeping around, it's weir
[18:25] <sil2100> *weird
[18:25] <sil2100> Could you maybe still allocate a few cycles today to take a look just in case?
[18:25] <dbungert> yea, I was able to reproduce it easily
[18:25] <dbungert> yes, I've captured some logs at request of #snappy
[18:26] <sil2100> Since I tried now for instance, at one moment I could run `snap list` but later on it was failing, implying as if snapd is gone?!
[18:26] <sil2100> dbungert: thanks ;)
[18:26] <dbungert> for this bug, the steps listed are important.  If you interact with snapd right away on boot I think it's fine, but after a few steps in subiquity it isn't.
[18:27] <sil2100> Yeah, did just that, went a few steps forward, then used `snap list` and first call gave me a list (after a long wait tho), but all consecutive ones not
[18:28] <dbungert> I linked a subiquity bug above, unrelated to the snapd thing.  I think we should fix it for Impish.
[18:29] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity amd64 [Impish Final] (20211011.1) has been added
[18:29] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity arm64 [Impish Final] (20211011.1) has been added
[18:29] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity ppc64el [Impish Final] (20211011.1) has been added
[18:29] -queuebot:#ubuntu-release- Builds: Ubuntu Server Subiquity s390x [Impish Final] (20211011.1) has been added
[18:46] <sil2100> dbungert: hm, so you mean it instantly partitions the device?
[18:46] <dbungert> The 'Confirm destructive action' screen is not shown.  You still go thru filesystem screens before that.
[18:47] <sil2100> I suppose that was working as expected during Beta, right?
[18:47] <sil2100> I agree, this feels like a decent release blocker
[18:49] <dbungert> good news is I can revert one commit and address it, but it's not code I understand well.  I want mwhudson confirmation.
[19:12] <bdmurray> sil2100: rebuilding ubuntu kylin
[19:13] <dbungert> mwhudson: https://github.com/canonical/subiquity/pull/1093
[19:14] <sil2100> bdmurray: thanks o/
[19:18] -queuebot:#ubuntu-release- Builds: Ubuntu Base amd64 [Impish Final] (20211011.1) has been added
[19:19] -queuebot:#ubuntu-release- Builds: Ubuntu Base arm64 [Impish Final] (20211011.1) has been added
[19:19] -queuebot:#ubuntu-release- Builds: Ubuntu Base armhf [Impish Final] (20211011.1) has been added
[19:19] -queuebot:#ubuntu-release- Builds: Ubuntu Base ppc64el [Impish Final] (20211011.1) has been added
[19:19] -queuebot:#ubuntu-release- Builds: Ubuntu Base riscv64 [Impish Final] (20211011.1) has been added
[19:19] -queuebot:#ubuntu-release- Builds: Ubuntu Base s390x [Impish Final] (20211011.1) has been added
[19:28] <mwhudson> dbungert: oops
[19:28] <dbungert> mwhudson: anything else pressing?
[19:29] <mwhudson> dbungert: not that i know about yet!
[19:29] <dbungert> you might want to read LP: #1946656 but I think that's snapd, not subiquity
[19:30] <mwhudson> dbungert: hmm that looks pretty bad :/
[19:32] <vorlon> apw, utkarsh2102: azure-cli builds multiple binary packages, and neither of you checked the reverse-deps for the whole source package before removal; https://people.canonical.com/~ubuntu-archive/proposed-migration/impish_uninst.txt
[19:34] <vorlon> sil2100: has anyone (juliank?) looked into the cause of the arm64 backlog today?  This is not "just" fallout from the no-change rebuilds; something's wrong there, arm64 is normally much faster than this but I also haven't been able to work out where the slow-down is
[19:34] <mwhudson> dbungert: walking my daughter to school, biab
[19:35] <vorlon> (also, 160 desktop packages in -proposed != 160 packages that need to migrate, so if there are packages that specifically *need* to get in for release, those should be highlighted)
[19:35] <juliank> vorlon: I did not see increased error rates
[19:35] <vorlon> juliank: where are you looking to see error rates?
[19:35] <juliank> vorlon: at https://ubuntu-release.kpi.ubuntu.com/d/76Oe_0-Gz/autopkgtest?orgId=1&var-instance=staging
[19:36] <juliank> Well
[19:36] -queuebot:#ubuntu-release- Unapproved: hexchat (focal-proposed/universe) [2.14.3-3ubuntu0.20.04.1 => 2.14.3-3ubuntu0.20.04.2] (no packageset)
[19:36] <juliank> The production one
[19:36] <juliank> arm64 active worker count did not change much
[19:37] <juliank> The others were slow too
[19:37] <apw> vorlon, woh, how did i manage that?
[19:37] <vorlon> apw: dunno :)
[19:37] <juliank> Note that the numbers are off for large periods, we need to fix the grafana queries to aggregate correctly
[19:38] <juliank> (we report 5 min intervals, and 10 min periods sum them up, leading to values reported that are double)
[19:39] <juliank> But I see it doing stuff, so I did not investigate further
[19:39] <juliank> We should see significant exited abnormally, and failed workers if there are issues imo
[19:40] <vorlon> juliank: uh, I've never seen this page before, how do I get to it from https://ubuntu-release.kpi.ubuntu.com/ ?
[19:40] <juliank> vorlon: don't know, sorry, click somewhere to set project to autopkgtest?
[19:41] <vorlon> heh ok
[19:41] <juliank> I need to stop typing for today before my wrist fails harder :(
[19:41] <vorlon> also, I think a thing we want to be graphing is the runtime of each autopkgtest completed during a given interval; it's difficult to synthesize an answer to the question "are autopkgtests currently running slower on the infrastructure" without that
[19:42] <vorlon> this will obviously be noisy at high resolution because autopkgtests individually vary in runtime
[19:43] <juliank> bracket them in 5, 10, 15, 30, 60, 120 minute groups
[19:44] <vorlon> if all the packages jump from being in the 15 minute group to the 30 minute group because of a slow-down, that would be misleading :)
[19:44] <juliank> youll see an increase in 30 min runs, itll be fine
[20:15] <mwhudson> dbungert: re https://bugs.launchpad.net/ubuntu-cdimage/+bug/1946656 it Works For Me tm
[20:15] <mwhudson> dbungert: i see there's been a respin since the iso paride tested though
[20:15] <dbungert> I'll download a new iso
[20:18] -queuebot:#ubuntu-release- Builds: Ubuntu Kylin Desktop amd64 [Impish Final] has been updated (20211011.1)
[20:20] <dbungert> mwhudson: still bad for me with respun iso
[20:20] <mwhudson> dbungert: hmm
[20:21] <bdmurray> Hmm the Ubuntu Kylin didn't get the new ukui-media, building again
[20:21]  * bdmurray tries to delete his previous message
[20:26] <mwhudson> dbungert: hmm fine for me 4 / 4 attempts, i even tried joining the vpn
[20:27] <bdmurray> mwhudson: and this is further along in the installation process?
[20:28] <mwhudson> bdmurray: ah wait i helps if i read the bug!
[20:28] <sil2100> bdmurray: it did get it from what I see! http://cdimage.ubuntu.com/ubuntukylin/daily-live/20211011.1/impish-desktop-amd64.manifest
[20:29] <sil2100> bdmurray: it has ukui-media 3.0.3.1-1 and 3.0.3.1-1 is the one we were expecting I think?
[20:29] <sil2100> bdmurray: did you see something different?
[20:29] <mwhudson> bdmurray, dbungert: ok now i see the same thing
[20:30] <bdmurray> sil2100: I did but it was because I was looking at the image from earlier in the day. ;-)
[20:31] <sil2100> ...actually a similar thing happened to me today!
[20:32] <mwhudson> dbungert, bdmurray: subiquity is trying to restart snapd to pick up the proxy config and snapd is not exiting cleanly afaics
[20:33] <dbungert> mwhudson: something I haven't tested yet is if snapd 2.51.7 is happier
[20:36] <mwhudson> what is going on
[20:36] <mwhudson> have we got a snapd developer to look at this yet?
[20:37] <bdmurray> sil2100 was talking about some rate throttling hence the 403
[20:38] <bdmurray> it should be in the backscroll here
[20:38] <dbungert> mwhudson: there's a little chat in #snappy
[20:38] <mwhudson> if that can make the snapd process fail to exit in response to a SIGTERM then something really funky is going on
[20:38] <mwhudson> i should try without network i guess
[20:41] <mwhudson> yeah i see the same without network
[20:45] <bdmurray> Has anybody verified bug 1944468 now that glibc has migrated?
[20:46] <bdmurray> Eickmeyer: ^
[20:46] <Eickmeyer> bdmurray: Yep, can confirm
[20:46] <Eickmeyer> It's migrated, no issues with electron apps anymore.
[20:54] -queuebot:#ubuntu-release- Builds: Ubuntu Server arm64+raspi [Impish Final] (20211011.1) has been added
[20:54] -queuebot:#ubuntu-release- Builds: Ubuntu Server armhf+raspi [Impish Final] (20211011.1) has been added
[20:54] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+unleashed [Impish Final] (20211011.1) has been added
[20:54] -queuebot:#ubuntu-release- Builds: Ubuntu Server riscv64+unmatched [Impish Final] (20211011.1) has been added
[21:45] -queuebot:#ubuntu-release- New sync: gnome-connections (impish-proposed/primary) [41.0-1]
[21:47] <jbicha> ^ if not too much trouble, please review gnome-connections from the new queue. I'd like for people to be able to try it out easily without a PPA before the next LTS
[22:25] -queuebot:#ubuntu-release- Unapproved: accepted netplan.io [source] (hirsute-proposed) [0.103-0ubuntu5~21.04.2]
[22:26] -queuebot:#ubuntu-release- Unapproved: accepted netplan.io [source] (focal-proposed) [0.103-0ubuntu5~20.04.2]
[23:18] -queuebot:#ubuntu-release- New: accepted gnome-connections [sync] (impish-proposed) [41.0-1]
[23:22] -queuebot:#ubuntu-release- New binary: gnome-connections [s390x] (impish-proposed/none) [41.0-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: gnome-connections [amd64] (impish-proposed/none) [41.0-1] (no packageset)
[23:22] -queuebot:#ubuntu-release- New binary: gnome-connections [ppc64el] (impish-proposed/none) [41.0-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: gnome-connections [arm64] (impish-proposed/universe) [41.0-1] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: gnome-connections [armhf] (impish-proposed/universe) [41.0-1] (no packageset)
[23:25] -queuebot:#ubuntu-release- New: accepted gnome-connections [armhf] (impish-proposed) [41.0-1]
[23:26] -queuebot:#ubuntu-release- New: accepted gnome-connections [amd64] (impish-proposed) [41.0-1]
[23:26] -queuebot:#ubuntu-release- New: accepted gnome-connections [ppc64el] (impish-proposed) [41.0-1]
[23:26] -queuebot:#ubuntu-release- New: accepted gnome-connections [arm64] (impish-proposed) [41.0-1]
[23:26] -queuebot:#ubuntu-release- New: accepted gnome-connections [s390x] (impish-proposed) [41.0-1]
[23:28] <vorlon> juliank: so you dropped metapackage-triggered autopkgtest runs; was there also coordination to skiptest these packages so they would migrate? I see base-files was skiptest'ed, but no others
[23:29] <vorlon> (and 2075 tests 'in progress' on update_excuses, but only 1161 in the queue)
[23:57] -queuebot:#ubuntu-release- New binary: gnome-connections [riscv64] (impish-proposed/universe) [41.0-1] (no packageset)