[02:22] <mwhudson> i don't suppose anyone who can log into autopkgtest infra is around?
[02:26] <handsome_feng> Hi, ukui-menu 2.0.1-1 is blocked when migrating from -proposed to release because missing build on i386, but the i386 package (ukui-menu=1.1.12-1) is migrate from eoan to focal, how to deal with this situation? Thanks!
[02:31] <xnox> mwhudson:  i think i actually have the right permissions to do that.
[02:31] <xnox> mwhudson:  but after initial training, it might be a while for me to dig up the right hostnames to ssh into
[02:31] <xnox> mwhudson:  what specifically are you after?
[02:31] <mwhudson> xnox: do you have any way of deriving what is causing https://autopkgtest.ubuntu.com/running#pkg-docker.io to hang?
[02:31] <mwhudson> xnox: it doesn't hang when i run it locally :(
[02:33] <xnox> le sigh
[02:33] <xnox> for that one may need to ssh all the way into the guest os, and i'm not sure i've done that, I only got to the queus and workers.
[02:33] <xnox> it should be all local, cause it is importing a tarball and running it.
[02:34] <mwhudson> actually i think it's possible you need to launch a job in a special way to allow a human to log into it, i forget
[02:34] <xnox> unless dockerd is dead, or hung up, with a new kernel....
[02:34] <mwhudson> xnox: it's triggered by the new containerd
[02:34] <xnox> that also sounds like something familear
[02:34] <mwhudson> (in focal-proposed)
[02:35] <xnox> once it times out and fails, there should be a log right. i wonder if things are not happy with new kernel, new systmed, new apparmor and the like with the new containerd.
[02:35] <xnox> plus i thought debian has broken networking
[02:35]  * xnox wonders if ubuntu true test would just work
[02:35] <xnox> although networking stuff should have been fixed by now
[02:35] <xnox> horum
[02:36] <xnox> i'm gonna finish my mint tea and go to bed =)
[02:44] <mwhudson> xnox: nothing in logs iirc but maybe i should check an old failure indeed
[02:44] <mwhudson> xnox: good night
[02:45] <mwhudson> no nothing useful in artifacts
[02:48] <mwhudson> xnox: i want to talk to you about vtoc tomorrow :)
[03:12] -queuebot:#ubuntu-release- New: accepted gitless [amd64] (focal-proposed) [0.8.8-2]
[03:52] <handsome_feng> Sorry, I got it, It's because it migrate from python to qt, and the architecture changes from all to any.
[03:52] <wxl> handsome_feng: p.s. kylin's looking good in qt :)
[03:53] <handsome_feng> wxl, Thanks! :)
[04:00] <handsome_feng> And anyone know how to deal with this situation? I didn't find the document. :(
[05:24] -queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-tesla-418 [amd64] (focal-proposed/multiverse) [418.116.00-3] (no packageset)
[05:32] -queuebot:#ubuntu-release- New binary: nvidia-graphics-drivers-tesla-418 [ppc64el] (focal-proposed/multiverse) [418.116.00-3] (no packageset)
[05:34] <infinity> handsome_feng: Fixing ukui-menu (and panel appears to have the same issue).
[06:08] <handsome_feng> infinity: Thanks!
[06:14] -queuebot:#ubuntu-release- New binary: cinnamon-control-center [s390x] (focal-proposed/universe) [4.4.0-2] (no packageset)
[06:15] -queuebot:#ubuntu-release- New binary: cinnamon-control-center [ppc64el] (focal-proposed/universe) [4.4.0-2] (no packageset)
[06:16] -queuebot:#ubuntu-release- New binary: cinnamon-control-center [amd64] (focal-proposed/universe) [4.4.0-2] (no packageset)
[06:20] -queuebot:#ubuntu-release- New binary: cinnamon-control-center [arm64] (focal-proposed/universe) [4.4.0-2] (no packageset)
[06:20] -queuebot:#ubuntu-release- New binary: cinnamon-control-center [armhf] (focal-proposed/universe) [4.4.0-2] (no packageset)
[07:05] <RAOF> So, now that Mir builds and passes it's !i386 autopkgtests, the thing try do is to delete the stale i386 binaries and everything is hunky-dory, right?
[07:27] <doko> RAOF: did you you schedule the rebuilds for the soname change?
[07:31] -queuebot:#ubuntu-release- New: accepted cinnamon-control-center [amd64] (focal-proposed) [4.4.0-2]
[07:31] -queuebot:#ubuntu-release- New: accepted cinnamon-control-center [armhf] (focal-proposed) [4.4.0-2]
[07:31] -queuebot:#ubuntu-release- New: accepted cinnamon-control-center [s390x] (focal-proposed) [4.4.0-2]
[07:31] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-tesla-418 [ppc64el] (focal-proposed) [418.116.00-3]
[07:31] -queuebot:#ubuntu-release- New: accepted cinnamon-control-center [arm64] (focal-proposed) [4.4.0-2]
[07:31] -queuebot:#ubuntu-release- New: accepted nvidia-graphics-drivers-tesla-418 [amd64] (focal-proposed) [418.116.00-3]
[07:31] -queuebot:#ubuntu-release- New: accepted cinnamon-control-center [ppc64el] (focal-proposed) [4.4.0-2]
[07:46] <RAOF> doko: To my knowledge there are no rdepends of Mir-built binaries (at present)
[07:47] <RAOF> (At least, ones that are not built from the Mir source package)
[07:51] -queuebot:#ubuntu-release- New binary: icu [s390x] (focal-proposed/main) [65.1-1] (core, i386-whitelist)
[07:52] -queuebot:#ubuntu-release- New binary: icu [i386] (focal-proposed/main) [65.1-1] (core, i386-whitelist)
[07:55] -queuebot:#ubuntu-release- New binary: icu [amd64] (focal-proposed/main) [65.1-1] (core, i386-whitelist)
[08:07] -queuebot:#ubuntu-release- New binary: icu [arm64] (focal-proposed/main) [65.1-1] (core, i386-whitelist)
[08:08] -queuebot:#ubuntu-release- New binary: icu [armhf] (focal-proposed/main) [65.1-1] (core, i386-whitelist)
[09:35] <locutus_> mwhudson, hello, I did sync python-traits, not sure but flaky tests seems to be not flaky anymore?
[09:36] <locutus_> it built fine on first attempt
[09:48] <mwhudson> locutus_: i don't remember that package i'm afraid
[09:48] <mwhudson> i guess it's s good thing it's building :)
[10:32] <tseliot> hello admins, I don't think nvidia-graphics-drivers-tesla-418 should have been synced, since we don't sync nvidia drivers from Debian
[10:32] <tseliot> apw ^^
[10:32] <tseliot> also sil2100 ^
[12:05] <rbalint> sil2100, could you please merge https://code.launchpad.net/~rbalint/britney/hints-ubuntu/+merge/378651 for systemd?
[12:25] <apw> tseliot, i'll pull it, and that should also cause it to be blacklisted
[12:27] <tseliot> apw, thanks, I think this one should go with it too https://launchpad.net/ubuntu/+source/nvidia-settings-tesla-418
[12:27] <apw> tseliot, yeah ... both done
[12:27] <tseliot> apw, thanks again
[13:23] <cpaelzer> hiho, why is wal2json in update_excuses complaining about "missing build on armhf: postgresql-12-wal2json (from 2.0-1)"
[13:23] <cpaelzer> the whole point of 2.0-2 was to drop armhf and i386
[13:24] <cpaelzer> please do not that is misses the "2.0-1" binary
[13:24] <cpaelzer> but this is for 2.0-2
[13:25] <cpaelzer> or it misses the armhf binary "coming from 2.0-1"
[13:25] <cpaelzer> but never the less - the current 2.0-2 doesn't want to have the armhf/i386 binaries
[13:25] <cpaelzer> anything I can do to resolve that and get it moving again?
[13:26] <cjwatson> Because 2.0-1 was built on armhf in focal-proposed and not migrated, and proposed-migration doesn't automatically handle that case
[13:26] <cjwatson> I'll remove it by hand
[13:26] <cpaelzer> Full discplaimer: in a few days hopefulyl there will be a 2.1-1 which will re-add armhf/i386 but I'd prefer not to rely on that
[13:26] <cpaelzer> cjwatson: ah so it really is because 2.0-1 had armhf and it is now missing
[13:26] <cpaelzer> thanks cjwatson
[13:27] <cjwatson> done
[13:27] <cpaelzer> great, checking back later how migration goes on then
[13:46] -queuebot:#ubuntu-release- Unapproved: shim-signed (eoan-proposed/main) [1.39.1 => 1.41] (core) (sync)
[13:46] -queuebot:#ubuntu-release- Unapproved: shim (eoan-proposed/main) [15+1533136590.3beb971-0ubuntu1 => 15+1552672080.a4a1fbe-0ubuntu1] (core) (sync)
[13:46] -queuebot:#ubuntu-release- Unapproved: shim-signed (bionic-proposed/main) [1.37~18.04.4 => 1.41] (core) (sync)
[13:46] -queuebot:#ubuntu-release- Unapproved: shim (bionic-proposed/main) [15+1533136590.3beb971-0ubuntu1 => 15+1552672080.a4a1fbe-0ubuntu1] (core) (sync)
[13:47] -queuebot:#ubuntu-release- Unapproved: shim-signed (xenial-proposed/main) [1.33.1~16.04.5 => 1.41] (core) (sync)
[13:47] -queuebot:#ubuntu-release- Unapproved: shim (xenial-proposed/main) [15+1533136590.3beb971-0ubuntu1 => 15+1552672080.a4a1fbe-0ubuntu1] (core) (sync)
[13:47] <juliank> xnox: ^ shims for everyone :)
[13:47] <juliank> Not sure how this is going to work SRU wise, as we don't have an SRU bug number
[13:48] <juliank> last one did not have one either, though
[13:48] <xnox> juliank:  blame the guy who quit! =)
[13:49] <juliank> We can reuse my bug, and tag it update-excuses maybe?
[13:49] <juliank> idk
[13:49] <juliank> certainly we can tag it block-proposed-{xenial,bionic,eoan}
[13:49] <juliank> idk
[13:49] <xnox> oooh update-excuse yeah
[13:49]  * xnox ponders if update-excuse tag should be renamed to udpate-excuses
[13:51]  * RikMills wonders who decided that a test error should show a red grinning face emoji
[14:17] -queuebot:#ubuntu-release- New binary: linux-signed-oem [amd64] (bionic-proposed/main) [4.15.0-1071.81] (kernel)
[14:24] <infinity> RikMills: I believe the "design" (I use that term loosely) of most of that UI was pitti.
[14:25] <rbalint> sil2100, could you please drop current ec2-instance-connect srus from from the unapproved queue? I'm about to upload a new set instead
[14:38] <juliank> hmm should I only have copied shim, and not shim-signed?
[14:38]  * juliank confused
[14:38] -queuebot:#ubuntu-release- Unapproved: ibm-java80 (xenial-release/partner) [8.0.6.0-0ubuntu1 => 8.0.6.5-0ubuntu1] (no packageset) (sync)
[14:39] <juliank> or should I have used proper backport SRUs for shim-signed, so that we get an SRU bug in there?
[14:40] <juliank> wiki page just said copy binaries, but shim-signed seems to have been uploaded with version per release
[15:07] <apw> juliank, if i am remembering correctly (and that is questionable) we have switched things like enforcement at different times which might have necessitated skew
[15:08] <juliank> Hmm
[15:09] <juliank> I think those should be hardcoded in the binaries, and they're the same
[15:09] <juliank> but surrounding might be different
[15:09] <juliank> e.g. update-secureboot-policy
[15:09] <juliank> someone should probably reject the shim-signed uploads
[15:10] <juliank> and then they need redoing
[15:10] <juliank> Well, eoan probably nobody cares
[15:11] <juliank> ah we do
[15:12] <juliank> Yup gotta redo those
[15:12] <apw> juliank, so reject the lot, or just -signed
[15:12] <juliank> apw: just signed is fine, if you reject all, I could copy the unsigned ones back, though, it doesn't really matter
[15:13] <apw> juliank, ack
[15:15] -queuebot:#ubuntu-release- Unapproved: rejected shim-signed [sync] (bionic-proposed) [1.41]
[15:15] -queuebot:#ubuntu-release- Unapproved: rejected shim-signed [sync] (eoan-proposed) [1.41]
[15:15] -queuebot:#ubuntu-release- New: accepted linux-signed-oem [amd64] (bionic-proposed) [4.15.0-1071.81]
[15:15] -queuebot:#ubuntu-release- Unapproved: rejected shim-signed [sync] (xenial-proposed) [1.41]
[15:15] <apw> juliank, ^
[15:15] <juliank> thanks, apw
[15:44] -queuebot:#ubuntu-release- Unapproved: accepted clamav [source] (eoan-proposed) [0.102.1+dfsg-0ubuntu0.19.10.3]
[15:59] -queuebot:#ubuntu-release- Unapproved: accepted clamav [source] (bionic-proposed) [0.102.1+dfsg-0ubuntu0.18.04.3]
[15:59] <slashd> Big thanks sil2100 ^
[16:07] -queuebot:#ubuntu-release- Unapproved: accepted clamav [source] (xenial-proposed) [0.102.1+dfsg-0ubuntu0.16.04.3]
[16:08] <sil2100> yw!
[16:19] <bashfulrobot> infinity: I'm just curious. Are you by chance aware as to when the LTS applications have to be in by?
[16:29] -queuebot:#ubuntu-release- Unapproved: rejected ec2-instance-connect [source] (bionic-proposed) [1.1.12+dfsg1-0ubuntu2~18.04.0]
[16:29] -queuebot:#ubuntu-release- Unapproved: rejected ec2-instance-connect [source] (eoan-proposed) [1.1.12+dfsg1-0ubuntu2~19.10.0]
[16:30] -queuebot:#ubuntu-release- Unapproved: rejected ec2-instance-connect [source] (xenial-proposed) [1.1.12+dfsg1-0ubuntu2~16.04.0]
[16:40] <sil2100> vorlon: hey! Looking at the xenial queue, I see a new ibm-java80 for partner, but the target destination seems to be the Release pocket - guess when I accept it, it will bypass partner proposed, right?
[17:08] -queuebot:#ubuntu-release- New source: python-gffutils (focal-proposed/primary) [0.10.1-1ubuntu1]
[17:34] <vorlon> sil2100_: yeah, if it's targeted to the release pocket, that's the case
[17:34] <vorlon> dannf: ^^
[17:40] <dannf> vorlon, sil2100_ ah, sorry - probably me failing at trying to use copy-package again. should i retry w/ --to-suite xenial-proposed?
[17:41] <vorlon> dannf: yes please :-)
[17:41] <dannf> vorlon: ok - that looks better.
[17:42] -queuebot:#ubuntu-release- Unapproved: ibm-java80 (xenial-proposed/partner) [8.0.6.0-0ubuntu1 => 8.0.6.5-0ubuntu1] (no packageset) (sync)
[17:56] -queuebot:#ubuntu-release- Unapproved: shim-signed (bionic-proposed/main) [1.37~18.04.4 => 1.37~18.04.5] (core)
[17:58] <vorlon> sil2100_: ^^ if you're doing reviews, this is a one-liner fix for a regression in the previous -proposed upload
[18:09] <sil2100_> vorlon: on it o/
[18:19] <sil2100_> vorlon: is this also fixing the previous issue? Since the previous LP bug got lost in the .changes, probably needs a reupload with -v
[18:20] <vorlon> sil2100_: I can do that
[18:20] <vorlon> plz reject
[18:21] -queuebot:#ubuntu-release- Unapproved: shim-signed (bionic-proposed/main) [1.37~18.04.4 => 1.37~18.04.5] (core)
[18:22] -queuebot:#ubuntu-release- Unapproved: rejected shim-signed [source] (bionic-proposed) [1.37~18.04.5]
[18:22] <vorlon> rbalint, xnox: should LP: #1860432 be wontfix for systemd?  sounds like juju is going to change their behavior
[18:23] <xnox> i still wanted to at least file an upstream issue about it
[18:25] <doko> so we still have a lot of b-d's on python and python-dev, which showed up in NBS a while ago. but not anymore. why not?
[18:26] <vorlon> doko: because python and python-dev are not NBS because they have been removed?
[18:26] <vorlon> they were uninstallable, so there was no reason in terms of archive consistency to keep them around in the release pocket
[18:26] -queuebot:#ubuntu-release- Unapproved: accepted shim-signed [source] (bionic-proposed) [1.37~18.04.5]
[18:27] -queuebot:#ubuntu-release- Unapproved: accepted ibm-java80 [sync] (xenial-proposed) [8.0.6.5-0ubuntu1]
[18:27] -queuebot:#ubuntu-release- Unapproved: rejected ibm-java80 [sync] (xenial-release) [8.0.6.5-0ubuntu1]
[18:28] <doko> ok, then I assume we need to setup a transition tracker to point out the remaining ones
[20:14] -queuebot:#ubuntu-release- New binary: icu [amd64] (focal-proposed/main) [65.1-1ubuntu1] (core, i386-whitelist)
[20:14] -queuebot:#ubuntu-release- New binary: icu [s390x] (focal-proposed/main) [65.1-1ubuntu1] (core, i386-whitelist)
[20:15] -queuebot:#ubuntu-release- New binary: icu [i386] (focal-proposed/main) [65.1-1ubuntu1] (core, i386-whitelist)
[20:15] -queuebot:#ubuntu-release- New binary: icu [ppc64el] (focal-proposed/main) [65.1-1ubuntu1] (core, i386-whitelist)
[20:23] -queuebot:#ubuntu-release- New binary: icu [armhf] (focal-proposed/main) [65.1-1ubuntu1] (core, i386-whitelist)
[20:29] -queuebot:#ubuntu-release- New binary: icu [arm64] (focal-proposed/main) [65.1-1ubuntu1] (core, i386-whitelist)
[21:14] <mwhudson> vorlon: ok https://autopkgtest.ubuntu.com/running#pkg-docker.io is hanging, if you could log in and run ps / lsof / strace any likely looking things / etc that would be great
[21:17] <ddstreet> infinity i see you're listed in the sru rotation for today, though i'm not sure if that's still accurate, but if it is could you release qemu for b/e and network-manager for e
[21:45] <vorlon> mwhudson: ps: https://paste.ubuntu.com/p/Yp84qQWhp2/
[21:46] <vorlon> mwhudson: docker ps: https://paste.ubuntu.com/p/48jhgHGY7s/
[21:49] <vorlon> mwhudson: lsof/strace on the 'docker run': https://paste.ubuntu.com/p/tTVWNJ79H9/
[21:50] <vorlon> mwhudson: a second 'docker run' also hangs
[21:56] <mwhudson> vorlon: can you strace the containerd-shim process?
[21:57] <mwhudson> vorlon: also lsof
[22:25] <mwhudson> vorlon: ideally before the test times out :)
[22:27] <vorlon> mwhudson: there are 2 containerd-shim processes, do you know if I should be looking at parent or child?
[22:28] <mwhudson> vorlon: i only see one in your first ps listing, is that because you ran docker run again?
[22:28] <vorlon> oh, maybe?
[22:28] <mwhudson> https://paste.ubuntu.com/p/Yp84qQWhp2/ only has 8092
[22:28] <vorlon> right, it's not parent/child
[22:28] <mwhudson> aiui docker run talks to dockerd talks to containerd
[22:29] <vorlon> mwhudson: https://paste.ubuntu.com/p/bJ4CKfS6tS/
[22:30] <vorlon> the thread eventually woke up again, but it's just more futex/nanosleep nonsense
[22:30] <mwhudson> yeah that's doing a whole lot of nothing isn't it
[22:31] <mwhudson> i wonder if there's any way to see what the eventpoll things are
[22:35] <mwhudson> yeah i definitely think that containerd-shim should have exited
[22:35] <mwhudson> biab
[22:58] <mwhudson> vorlon: i don't suppose it'll reveal much but "ls -l /var/lib/containerd/io.containerd.runtime.v1.linux/moby/c37559527799313b65be7e8b63736947312b28986a3d6fcf3ee9a5a20cdd415a/" ?
[22:59] <mwhudson> vorlon: and maybe ls -l /run/docker/containerd/
[23:01] <mwhudson> vorlon: also can you gdb -p to a containerd-shim and 'thread apply all bt' or whatever that command is?
[23:02] <mwhudson> hm might need to install the ddeb for that to be at all useful :(
[23:02] <vorlon> mwhudson: $ sudo ls -l /var/lib/containerd/io.containerd.runtime.v1.linux/moby/c37559527799313b65be7e8b63736947312b28986a3d6fcf3ee9a5a20cdd415a/
[23:02] <vorlon> total 0
[23:02] <vorlon> prwx------ 1 root root 0 Feb 10 21:05 shim.stderr.log
[23:02] <vorlon> prwx------ 1 root root 0 Feb 10 21:05 shim.stdout.log
[23:02] <vorlon> $ sudo ls -l /run/docker/containerd/
[23:02] <vorlon> total 0
[23:02] <vorlon> drwxr-xr-x 2 root root 80 Feb 10 21:05 c37559527799313b65be7e8b63736947312b28986a3d6fcf3ee9a5a20cdd415a
[23:03] <vorlon> drwxr-xr-x 2 root root 80 Feb 10 21:50 f8d72d17248ce5eb41b87f63a63c7507332bee28f7bee0214a79e3f60c09cff7
[23:03] <mwhudson> hm no we don't strip go things still
[23:03] <mwhudson> hm no apparently we do but there is no ddeb on https://launchpad.net/ubuntu/+source/containerd/1.3.1-0ubuntu1/+build/18193736 ?
[23:04] <vorlon> heh oops
[23:04] <mwhudson> how did we manage that
[23:04] <vorlon> ask the go maintainers
[23:04] <mwhudson> yeah unfortunately that's me
[23:05] <vorlon> mwhudson: yeah, a whole lot of No symbol table info
[23:06] <mwhudson> ah upstream Makefile
[23:06] <mwhudson> ifndef GODEBUG
[23:06] <mwhudson>         EXTRA_LDFLAGS += -s -w
[23:06] <mwhudson> ffffffffffffuuuuuuuuuuuu
[23:12] <mwhudson> oh heh i have containerd 1.3.2 in git locally
[23:16] <vorlon> I do not think I want to define a God EBUG
[23:17] <mwhudson> oh wait maybe we want this fix https://github.com/containerd/containerd/pull/3857
[23:17] <mwhudson> so maybe if i just upload things will start working by magic
[23:17] <gitbot> containerd issue (Pull request) 3857 in containerd "Fix container pid race condition." [Cherry-Pick/1.3.X, Cherry-Picked/1.3.X, Priority/P0, Closed]
[23:24] -queuebot:#ubuntu-release- Unapproved: fwupd (focal-proposed/main) [1.3.7-2 => 1.3.7-3] (core)
[23:28] -queuebot:#ubuntu-release- Unapproved: fwupd (focal-proposed/main) [1.3.7-2 => 1.3.7-3] (core)
[23:28] -queuebot:#ubuntu-release- Unapproved: fwupd (focal-proposed/main) [1.3.7-2 => 1.3.7-3] (core)
[23:35] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [amd64] (focal-proposed) [1.3.7-3]
[23:35] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [armhf] (focal-proposed) [1.3.7-3]
[23:35] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [arm64] (focal-proposed) [1.3.7-3]
[23:44] -queuebot:#ubuntu-release- New binary: qtlocation-opensource-src [s390x] (focal-proposed/universe) [5.12.5+dfsg-5] (i386-whitelist, kubuntu, qt5)
[23:51] -queuebot:#ubuntu-release- New binary: qtlocation-opensource-src [amd64] (focal-proposed/universe) [5.12.5+dfsg-5] (i386-whitelist, kubuntu, qt5)
[23:54] -queuebot:#ubuntu-release- New binary: qtlocation-opensource-src [ppc64el] (focal-proposed/universe) [5.12.5+dfsg-5] (i386-whitelist, kubuntu, qt5)