[00:13] -queuebot:#ubuntu-release- New: accepted haskell-bitarray [amd64] (bionic-proposed) [0.0.1.1-3]
[00:13] -queuebot:#ubuntu-release- New: accepted haskell-bitarray [armhf] (bionic-proposed) [0.0.1.1-3]
[00:13] -queuebot:#ubuntu-release- New: accepted haskell-bitarray [ppc64el] (bionic-proposed) [0.0.1.1-3]
[00:13] -queuebot:#ubuntu-release- New: accepted pytrainer [amd64] (bionic-proposed) [1.11.0-1]
[00:13] -queuebot:#ubuntu-release- New: accepted haskell-bitarray [arm64] (bionic-proposed) [0.0.1.1-3]
[00:13] -queuebot:#ubuntu-release- New: accepted haskell-bitarray [s390x] (bionic-proposed) [0.0.1.1-3]
[00:13] -queuebot:#ubuntu-release- New: accepted haskell-bitarray [i386] (bionic-proposed) [0.0.1.1-3]
[07:30] <slangasek> jbicha: I don't know the impact of changing the derivation of the series after it's already been opened; maybe check with infinity?
[10:04] <cpaelzer> is there a way to get the output of "ip route show 0/0" on the workers that run dep8 tests on LP?
[10:04] <cpaelzer> I'm tracking down multiple issues on s390x (and others)
[10:05] <cpaelzer> and since now two seem to come down to that I'm teased how the output looks there
[10:05] <cpaelzer> My current guess is at least a two line output, but it could be anything
[10:05] <cpaelzer> there must be a better way than to pollute -proposed with something to print it for me
[10:08] <cpaelzer> And assuming that there are multiple interfaces on the default routes network
[10:08] <cpaelzer> which one should I let the tests touch - e.g. how do those interfaces differ?
[11:23] <infinity> cpaelzer: I'm somewhat torn between "it's probably a misconfiguration if there's more than one interface on an autopkgtest VM" and "why do you care?" :P
[11:26] <cpaelzer> infinity: I found a set of issues now popping up and failing on s390x
[11:26] <cpaelzer> infinity: (in case you decide for why do you care)
[11:26] <cpaelzer> infinity: it turned out the issue is not s390x special - instead formerly those worked on s390x (in containers) but now fail
[11:27] <cpaelzer> x86 is on always fail for those
[11:27] <xnox> cpaelzer, good tests, create their own interfaces/bridges and execute tests on those.
[11:27] <cpaelzer> And the only way to recreate that error that I found is if the command above returns two lines
[11:27] <xnox> cpaelzer, there is no specification in autopkgtest to abuse interfaces....
[11:27] <cpaelzer> xnox: lets consider tests ar enot good by default
[11:28] <xnox> =/
[11:28] <cpaelzer> and for now I want to make a totally broken bad test a not broken bad test
[11:28] <xnox> cpaelzer, do declare destroys-testbed and then abuse anything.
[11:28] <xnox> (or whatever the correct term is)
[11:28] <apw> cpaelzer, i believe we know it is two lines
[11:28] <apw> smb, ^^
[11:28] <cpaelzer> that would match the data I've seen
[11:29] <apw> i believe it blew up all our testing for something
[11:29] <cpaelzer> xnox: I'll remember to abuse something once I get the time to do so :-)
[11:29] <smb> apw, is there a tl;dr?
[11:29] <cpaelzer> Tests should not rely on network layout
[11:29] <apw> s390x ADT test runners have two default routes
[11:29] <apw> at least, maybe more
[11:29] <cpaelzer> TL;DR is the above
[11:29] <xnox> =/
[11:30] <infinity> apw: Really?  Openstack does that?
[11:30] <xnox> two default routes does not sound right, missconfigured openstack networking for the s390x compute? missconfigured networking profile for autopkgtest tenant on s390x?
[11:30] <apw> infinity, i thought we thought it was nplan which was doing it, no idea if what it adds is correct
[11:30] <xnox> it should be all virtualsed network....
[11:30] <smb> apw, I think all might, which is something that was brought up as feedback to our fan testing
[11:30] <smb> as part of netplan/systemd-networkd fallout
[11:30] <cpaelzer> btw your laptop with wire+wireless has two defaults in the sense that matters here
[11:31] <apw> right our testing units use the default route and were finding more than one, so we fix'd em
[11:31] <cpaelzer> ip route show 0/0
[11:31] <xnox> apw, if there is one route on xenial; yet two routes on artful/bionic -> it would smell like networkd fallout.
[11:31] <cpaelzer> even back on xenial
[11:31] <infinity> cpaelzer: Only if both are up and have IPs.
[11:31] <xnox> apw, and yes networkd sets up two routes -> one default; and one that routes self to self.
[11:31] <infinity> (and routes)
[11:31] <apw> xnox, it does what now ?
[11:31] <cpaelzer> yep, as they are for me without ever caring to much to configure soemthing special
[11:32] <xnox> no idea why it does it; what it means; and why it is useful.
[11:32] <xnox> apw, i have noticed that when diffing e.g. cloud-init provisioning tables before/after nplan switch.
[11:32] <cpaelzer> xnox: btw thanks for the hint on "test on own bridges" I won't unroll my stack of fixes but will keep it in mind next work on such
[11:33] <apw> xnox, a route self to self would not appear as a default route though as in ip route ls 0/0 would not show it
[11:33] <infinity> So, shouldn't need to play in scalingstack for this.  Booting a generic bionic cloud image should show you what it's doing.
[11:33] <xnox> apw, ack.
[11:33] <infinity> The autopkgtest images are just the generic image minus some bits torn out.
[11:34] <infinity> (But, at the end of the day, a test that makes assumptions about the network setup in the testbed seems a bit busted)
[11:34] <cpaelzer> infinity: ack I want to make them less busted atm which brought me to the initial question
[11:35] <infinity> cpaelzer: I guess my point is that the initial question seems irrelevant if you make the tests not care about the testbed's network setup. :P
[11:35] <cpaelzer> even if I'm not going for the ideal target of being totally non-dependent that will make them better than they are
[11:35] <apw> cpaelzer, we chose to assume the first default route was the one we wanted if that helps any
[11:35] <cpaelzer> infinity: you had my buy in already
[11:36] <cpaelzer> apw: I chose so as well an hour ago
[11:36] <cpaelzer> thanks
[11:37] <infinity> In theory, you want the one with the lowest metric.
[11:37] <infinity> But if you have multiple, the assumption is that all work.
[11:42] -queuebot:#ubuntu-release- Unapproved: ceph (artful-proposed/main) [12.2.0-0ubuntu1 => 12.2.1-0ubuntu0.17.10.1] (kubuntu, ubuntu-desktop, ubuntu-server)
[11:42] <infinity> cpaelzer: You also may be interested in 'ip ro get' instead of show.
[11:42] <infinity> (base)adconrad@nosferatu:~$ ip ro sh 0/0
[11:42] <infinity> default via 10.0.0.1 dev eth0 proto static metric 100
[11:42] <infinity> default via 10.0.0.1 dev wlan0 proto static metric 600
[11:42] <infinity> (base)adconrad@nosferatu:~$ ip ro ge 8.8.8.8
[11:42] <infinity> 8.8.8.8 via 10.0.0.1 dev eth0 src 10.0.0.4
[11:43] <infinity> (Will give you the lowest metric, or preferred route)
[11:53] <apw> infinity, though that does not actually tell you the route, so if you cared about the route component you don't know the prefix informatio there
[11:54] <cpaelzer> still interesting, thanks infinity
[11:54] <infinity> apw: No, true, it doesn't, except that if any of our VMs have a static route to 8.8.8.8, rather than it going via 0/0, I'd be very suspicious.
[11:54] <infinity> And amused.
[11:55] <apw> indeed all of that, in most cases we are looking specificall for 0/0 so that would work just fine
[11:55] <infinity> Anyhow, a "head -n1" should be good enough, as a machine with multiple 0/0 routes where they don't all work *is* misconfigured.
[11:55] <cpaelzer> which is what I currently coded to fix the test
[11:55] <cpaelzer> (head -n 1)
[12:14] <slashd> o/ Hi SRU (vanguard: sil2100, infinity) Could you please approve the upload of landscape-client for A, Z, X & T ? thanks in advance
[12:15] <sil2100> slashd: will take care of those after lunch
[12:16] <slashd> sil2100, thanks
[13:07] -queuebot:#ubuntu-release- New source: qqc2-desktop-style (bionic-proposed/primary) [5.40.0-0ubuntu1]
[13:28] -queuebot:#ubuntu-release- New binary: linux-signed-hwe [amd64] (xenial-proposed/main) [4.10.0-41.45~16.04.1] (kernel)
[14:06] -queuebot:#ubuntu-release- Unapproved: snapd (xenial-proposed/main) [2.29.3 => 2.29.4] (desktop-core, ubuntu-server)
[14:07] -queuebot:#ubuntu-release- Unapproved: snapd (trusty-proposed/universe) [2.29.3~14.04 => 2.29.4~14.04] (no packageset)
[14:07] -queuebot:#ubuntu-release- Unapproved: snapd (zesty-proposed/main) [2.29.3+17.04 => 2.29.4+17.10] (desktop-core, ubuntu-server)
[14:11] <slashd> tinoco ^
[14:50] -queuebot:#ubuntu-release- New: accepted linux-signed-hwe [amd64] (xenial-proposed) [4.10.0-41.45~16.04.1]
[16:17] -queuebot:#ubuntu-release- Unapproved: accepted landscape-client [source] (artful-proposed) [16.03-0ubuntu3.17.10.1]
[16:26] <smb> Is it possible to do the same adt hinting for snapd on s390x for xenial as it seems to be done for artful (the error seems to be the same and most likely due to the same reason of being just now moved to nova testing)
[16:27] -queuebot:#ubuntu-release- Unapproved: accepted landscape-client [source] (zesty-proposed) [16.03-0ubuntu3.17.04.1]
[16:32] -queuebot:#ubuntu-release- Unapproved: accepted landscape-client [source] (xenial-proposed) [16.03-0ubuntu2.16.04.2]
[16:38] -queuebot:#ubuntu-release- Unapproved: accepted landscape-client [source] (trusty-proposed) [14.12-0ubuntu6.14.04.1]
[16:41] -queuebot:#ubuntu-release- Unapproved: accepted python-defaults [source] (zesty-proposed) [2.7.13-2ubuntu1]
[16:42] -queuebot:#ubuntu-release- Unapproved: snapd (artful-proposed/main) [2.29.3+17.10 => 2.29.4+17.10] (desktop-core, ubuntu-server)
[16:43] -queuebot:#ubuntu-release- Unapproved: rejected snapd [source] (zesty-proposed) [2.29.4+17.10]
[16:46] -queuebot:#ubuntu-release- Unapproved: snapd (zesty-proposed/main) [2.29.3+17.04 => 2.29.4+17.04] (desktop-core, ubuntu-server)
[17:10] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (artful-proposed) [2.29.4+17.10]
[17:10] -queuebot:#ubuntu-release- New binary: i2c-tools [ppc64el] (bionic-proposed/universe) [4.0-1] (no packageset)
[17:11] -queuebot:#ubuntu-release- New binary: erlang-fs-listener [ppc64el] (bionic-proposed/none) [2.12.0-1] (no packageset)
[17:11] -queuebot:#ubuntu-release- New binary: libcleri [ppc64el] (bionic-proposed/none) [0.9.3-1] (no packageset)
[17:11] -queuebot:#ubuntu-release- New binary: pg-cron [ppc64el] (bionic-proposed/none) [1.0.2-1] (no packageset)
[17:11] -queuebot:#ubuntu-release- New binary: libcleri [arm64] (bionic-proposed/none) [0.9.3-1] (no packageset)
[17:11] -queuebot:#ubuntu-release- New binary: powercap [ppc64el] (bionic-proposed/none) [0.1.1-1] (no packageset)
[17:11] -queuebot:#ubuntu-release- New binary: libqxp [ppc64el] (bionic-proposed/none) [0.0.0-1] (no packageset)
[17:12] -queuebot:#ubuntu-release- New binary: i2c-tools [s390x] (bionic-proposed/universe) [4.0-1] (no packageset)
[17:12] -queuebot:#ubuntu-release- New binary: libftdi1 [amd64] (bionic-proposed/universe) [1.4-1] (kubuntu)
[17:12] -queuebot:#ubuntu-release- New binary: libcleri [armhf] (bionic-proposed/none) [0.9.3-1] (no packageset)
[17:12] -queuebot:#ubuntu-release- New binary: libftdi1 [ppc64el] (bionic-proposed/universe) [1.4-1] (kubuntu)
[17:13] -queuebot:#ubuntu-release- New binary: i2c-tools [arm64] (bionic-proposed/universe) [4.0-1] (no packageset)
[17:13] -queuebot:#ubuntu-release- New binary: i2c-tools [i386] (bionic-proposed/universe) [4.0-1] (no packageset)
[17:13] -queuebot:#ubuntu-release- New binary: libftdi1 [s390x] (bionic-proposed/universe) [1.4-1] (kubuntu)
[17:13] -queuebot:#ubuntu-release- New binary: i2c-tools [armhf] (bionic-proposed/universe) [4.0-1] (no packageset)
[17:13] -queuebot:#ubuntu-release- New binary: pmix [ppc64el] (bionic-proposed/universe) [2.1.0~rc1-2] (no packageset)
[17:13] -queuebot:#ubuntu-release- New binary: libftdi1 [i386] (bionic-proposed/universe) [1.4-1] (kubuntu)
[17:13] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (zesty-proposed) [2.29.4+17.04]
[17:14] -queuebot:#ubuntu-release- New binary: erlang-fs-listener [arm64] (bionic-proposed/none) [2.12.0-1] (no packageset)
[17:14] -queuebot:#ubuntu-release- New binary: libqxp [arm64] (bionic-proposed/none) [0.0.0-1] (no packageset)
[17:14] -queuebot:#ubuntu-release- New binary: pmix [amd64] (bionic-proposed/universe) [2.1.0~rc1-2] (no packageset)
[17:14] -queuebot:#ubuntu-release- New binary: i2c-tools [amd64] (bionic-proposed/universe) [4.0-1] (no packageset)
[17:14] -queuebot:#ubuntu-release- New binary: pg-cron [arm64] (bionic-proposed/none) [1.0.2-1] (no packageset)
[17:14] <slashd> snapd got approved tinoco ^
[17:15] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (xenial-proposed) [2.29.4]
[17:15] -queuebot:#ubuntu-release- New binary: backblaze-b2 [amd64] (bionic-proposed/none) [1.0.0-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: erlang-fs-listener [amd64] (bionic-proposed/none) [2.12.0-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: erlang-fs-listener [i386] (bionic-proposed/none) [2.12.0-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: libcleri [i386] (bionic-proposed/none) [0.9.3-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: libftdi1 [armhf] (bionic-proposed/universe) [1.4-1] (kubuntu)
[17:15] -queuebot:#ubuntu-release- New binary: pg-cron [armhf] (bionic-proposed/none) [1.0.2-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: construct.legacy [amd64] (bionic-proposed/none) [2.5.3-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: erlang-fs-listener [s390x] (bionic-proposed/none) [2.12.0-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: libqxp [armhf] (bionic-proposed/none) [0.0.0-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: erlang-fs-listener [armhf] (bionic-proposed/none) [2.12.0-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: powercap [arm64] (bionic-proposed/none) [0.1.1-1] (no packageset)
[17:15] <sil2100> Oh, someone approved it
[17:15] -queuebot:#ubuntu-release- New binary: libcleri [s390x] (bionic-proposed/none) [0.9.3-1] (no packageset)
[17:15] -queuebot:#ubuntu-release- New binary: pmix [i386] (bionic-proposed/universe) [2.1.0~rc1-2] (no packageset)
[17:16] -queuebot:#ubuntu-release- Unapproved: accepted snapd [source] (trusty-proposed) [2.29.4~14.04]
[17:16] <sil2100> Makes sense as I didn't see the artful SRU in the queue anymore
[17:16] -queuebot:#ubuntu-release- New binary: emacs-helm-ag [amd64] (bionic-proposed/none) [0.58-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: libqxp [amd64] (bionic-proposed/none) [0.0.0-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: pmix [s390x] (bionic-proposed/universe) [2.1.0~rc1-2] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: libcleri [amd64] (bionic-proposed/none) [0.9.3-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: powercap [armhf] (bionic-proposed/none) [0.1.1-1] (no packageset)
[17:16] -queuebot:#ubuntu-release- New binary: pg-cron [s390x] (bionic-proposed/none) [1.0.2-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: libqxp [s390x] (bionic-proposed/none) [0.0.0-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: pg-cron [i386] (bionic-proposed/none) [1.0.2-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: powercap [i386] (bionic-proposed/none) [0.1.1-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: pg-cron [amd64] (bionic-proposed/none) [1.0.2-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: powercap [s390x] (bionic-proposed/none) [0.1.1-1] (no packageset)
[17:17] -queuebot:#ubuntu-release- New binary: powercap [amd64] (bionic-proposed/none) [0.1.1-1] (no packageset)
[17:18] -queuebot:#ubuntu-release- New binary: ruby-notiffany [amd64] (bionic-proposed/none) [0.1.1-1] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: libqxp [i386] (bionic-proposed/none) [0.0.0-1] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: ruby-airbrussh [amd64] (bionic-proposed/none) [1.3.0-1] (no packageset)
[17:19] -queuebot:#ubuntu-release- New binary: pmix [arm64] (bionic-proposed/universe) [2.1.0~rc1-2] (no packageset)
[17:20] -queuebot:#ubuntu-release- New binary: libftdi1 [arm64] (bionic-proposed/universe) [1.4-1] (kubuntu)
[17:20] -queuebot:#ubuntu-release- New binary: pmix [armhf] (bionic-proposed/universe) [2.1.0~rc1-2] (no packageset)
[17:21] -queuebot:#ubuntu-release- New binary: libdancer2-plugin-ajax-perl [amd64] (bionic-proposed/none) [0.300000-1] (no packageset)
[17:37] -queuebot:#ubuntu-release- New binary: linux-signed-lts-xenial [amd64] (trusty-proposed/main) [4.4.0-102.125~14.04.1] (kernel)
[17:59] -queuebot:#ubuntu-release- New: accepted backblaze-b2 [amd64] (bionic-proposed) [1.0.0-1]
[17:59] -queuebot:#ubuntu-release- New: accepted emacs-helm-ag [amd64] (bionic-proposed) [0.58-1]
[17:59] -queuebot:#ubuntu-release- New: accepted erlang-fs-listener [i386] (bionic-proposed) [2.12.0-1]
[17:59] -queuebot:#ubuntu-release- New: accepted construct.legacy [amd64] (bionic-proposed) [2.5.3-1]
[17:59] -queuebot:#ubuntu-release- New: accepted erlang-fs-listener [amd64] (bionic-proposed) [2.12.0-1]
[18:00] -queuebot:#ubuntu-release- New: accepted erlang-fs-listener [arm64] (bionic-proposed) [2.12.0-1]
[18:00] -queuebot:#ubuntu-release- New: accepted erlang-fs-listener [ppc64el] (bionic-proposed) [2.12.0-1]
[18:00] -queuebot:#ubuntu-release- New: accepted i2c-tools [amd64] (bionic-proposed) [4.0-1]
[18:00] -queuebot:#ubuntu-release- New: accepted i2c-tools [armhf] (bionic-proposed) [4.0-1]
[18:00] -queuebot:#ubuntu-release- New: accepted i2c-tools [ppc64el] (bionic-proposed) [4.0-1]
[18:00] -queuebot:#ubuntu-release- New: accepted libcleri [amd64] (bionic-proposed) [0.9.3-1]
[18:00] -queuebot:#ubuntu-release- New: accepted libcleri [armhf] (bionic-proposed) [0.9.3-1]
[18:00] -queuebot:#ubuntu-release- New: accepted libcleri [ppc64el] (bionic-proposed) [0.9.3-1]
[18:00] -queuebot:#ubuntu-release- New: accepted libdancer2-plugin-ajax-perl [amd64] (bionic-proposed) [0.300000-1]
[18:00] -queuebot:#ubuntu-release- New: accepted libftdi1 [arm64] (bionic-proposed) [1.4-1]
[18:00] -queuebot:#ubuntu-release- New: accepted erlang-fs-listener [armhf] (bionic-proposed) [2.12.0-1]
[18:00] -queuebot:#ubuntu-release- New: accepted i2c-tools [arm64] (bionic-proposed) [4.0-1]
[18:00] -queuebot:#ubuntu-release- New: accepted i2c-tools [s390x] (bionic-proposed) [4.0-1]
[18:00] -queuebot:#ubuntu-release- New: accepted libcleri [i386] (bionic-proposed) [0.9.3-1]
[18:00] -queuebot:#ubuntu-release- New: accepted libftdi1 [amd64] (bionic-proposed) [1.4-1]
[18:00] -queuebot:#ubuntu-release- New: accepted libftdi1 [i386] (bionic-proposed) [1.4-1]
[18:00] -queuebot:#ubuntu-release- New: accepted libftdi1 [s390x] (bionic-proposed) [1.4-1]
[18:00] -queuebot:#ubuntu-release- New: accepted libqxp [arm64] (bionic-proposed) [0.0.0-1]
[18:00] -queuebot:#ubuntu-release- New: accepted libqxp [i386] (bionic-proposed) [0.0.0-1]
[18:00] -queuebot:#ubuntu-release- New: accepted libqxp [s390x] (bionic-proposed) [0.0.0-1]
[18:00] -queuebot:#ubuntu-release- New: accepted erlang-fs-listener [s390x] (bionic-proposed) [2.12.0-1]
[18:00] -queuebot:#ubuntu-release- New: accepted libcleri [arm64] (bionic-proposed) [0.9.3-1]
[18:00] -queuebot:#ubuntu-release- New: accepted libftdi1 [armhf] (bionic-proposed) [1.4-1]
[18:00] -queuebot:#ubuntu-release- New: accepted libqxp [amd64] (bionic-proposed) [0.0.0-1]
[18:00] -queuebot:#ubuntu-release- New: accepted libqxp [ppc64el] (bionic-proposed) [0.0.0-1]
[18:00] -queuebot:#ubuntu-release- New: accepted pg-cron [arm64] (bionic-proposed) [1.0.2-1]
[18:00] -queuebot:#ubuntu-release- New: accepted pg-cron [i386] (bionic-proposed) [1.0.2-1]
[18:00] -queuebot:#ubuntu-release- New: accepted pg-cron [s390x] (bionic-proposed) [1.0.2-1]
[18:00] -queuebot:#ubuntu-release- New: accepted i2c-tools [i386] (bionic-proposed) [4.0-1]
[18:00] -queuebot:#ubuntu-release- New: accepted libftdi1 [ppc64el] (bionic-proposed) [1.4-1]
[18:00] -queuebot:#ubuntu-release- New: accepted pg-cron [amd64] (bionic-proposed) [1.0.2-1]
[18:00] -queuebot:#ubuntu-release- New: accepted pg-cron [ppc64el] (bionic-proposed) [1.0.2-1]
[18:00] -queuebot:#ubuntu-release- New: accepted libcleri [s390x] (bionic-proposed) [0.9.3-1]
[18:00] -queuebot:#ubuntu-release- New: accepted pg-cron [armhf] (bionic-proposed) [1.0.2-1]
[18:00] -queuebot:#ubuntu-release- New: accepted libqxp [armhf] (bionic-proposed) [0.0.0-1]
[18:00] -queuebot:#ubuntu-release- New: accepted pmix [arm64] (bionic-proposed) [2.1.0~rc1-2]
[18:00] -queuebot:#ubuntu-release- New: accepted pmix [i386] (bionic-proposed) [2.1.0~rc1-2]
[18:00] -queuebot:#ubuntu-release- New: accepted pmix [s390x] (bionic-proposed) [2.1.0~rc1-2]
[18:00] -queuebot:#ubuntu-release- New: accepted powercap [arm64] (bionic-proposed) [0.1.1-1]
[18:00] -queuebot:#ubuntu-release- New: accepted powercap [i386] (bionic-proposed) [0.1.1-1]
[18:00] -queuebot:#ubuntu-release- New: accepted powercap [s390x] (bionic-proposed) [0.1.1-1]
[18:00] -queuebot:#ubuntu-release- New: accepted ruby-notiffany [amd64] (bionic-proposed) [0.1.1-1]
[18:01] -queuebot:#ubuntu-release- New: accepted pmix [amd64] (bionic-proposed) [2.1.0~rc1-2]
[18:01] -queuebot:#ubuntu-release- New: accepted pmix [ppc64el] (bionic-proposed) [2.1.0~rc1-2]
[18:01] -queuebot:#ubuntu-release- New: accepted powercap [armhf] (bionic-proposed) [0.1.1-1]
[18:01] -queuebot:#ubuntu-release- New: accepted ruby-airbrussh [amd64] (bionic-proposed) [1.3.0-1]
[18:01] -queuebot:#ubuntu-release- New: accepted pmix [armhf] (bionic-proposed) [2.1.0~rc1-2]
[18:01] -queuebot:#ubuntu-release- New: accepted powercap [ppc64el] (bionic-proposed) [0.1.1-1]
[18:01] -queuebot:#ubuntu-release- New: accepted powercap [amd64] (bionic-proposed) [0.1.1-1]
[18:14] <LocutusOfBorg> coreycb, "Resetting proxy settings in tests is bad, and makes ubuntu infra cry" why did you reintroduce it again for python-eventlet? the -3 upload was fine, the failure was a network error, not a misconfiguration in proxy
[18:16] <coreycb> LocutusOfBorg: james' delta was overwritten by a sync so i was re-enabling that. i included your delta as well but perhaps i shouldn't have?
[18:19] <LocutusOfBorg> damn, I syncd by loosing the python patch
[18:19] <LocutusOfBorg> the control file had the changes...
[18:19] <LocutusOfBorg> mea culpa!
[18:19] <LocutusOfBorg> I don't understand why enum34-compat.patch is not needed in debian then
[18:21] <LocutusOfBorg> so, let me reupload without the proxy change, so the delta is reduced to only one patch, and I'll send it to debian
[18:21] <coreycb> LocutusOfBorg: i'm not sure. i think jamespage submitted that back to debian but it wasn't included.
[18:21] <coreycb> LocutusOfBorg: ok thanks
[18:22] <LocutusOfBorg> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881989
[18:22] <ubot5> Debian bug 881989 in python-eventlet "python-eventlet: Missing dependency on enum-compat (which is a shim to enum34)" [Normal,Fixed]
[18:22] <LocutusOfBorg> indeed
[18:24] <coreycb> LocutusOfBorg: i wonder if they accidentally missed the patch and only updated d/control. i'll check with Ondrej.
[18:24] <LocutusOfBorg> I'm reopening the bug report
[18:24] <LocutusOfBorg> with an updated patch
[18:25] <coreycb> LocutusOfBorg: ok that'll work. thanks.
[18:25] <LocutusOfBorg> sent
[18:26] <LocutusOfBorg> better have a public followup from public bug, to avoid the same discussion on next upload :P
[18:26] <LocutusOfBorg> thanks!
[18:39] <slangasek> infinity: so, interesting that the arm64 queue didn't seem to drop much since last night... if only we had graphs of these queues ;)  I think we have quota to try to stand up a few more runners, if that hasn't already been done
[18:42] <slangasek> infinity: and currently we have 20 s390x workers running, but only 16 configured in git... not sure what awayney has in mind there, hmm, but I'll axe the last 4 which should reduce our chances of hitting quota to arm64's detriment
[18:56] <slangasek> infinity: ok, bumped from 40 to 45 workers now for arm64; assuming there is hardware to back up that quota, maybe that will be enough.  Alternatively, we could disable arm64 in britney again, which would let the currently scheduled tests still run but wouldn't block things yet?
[19:07] <tsimonq2> Any archive admin around who would be willing to help me with Britney?
[19:08] <tsimonq2> I don't know if I messed up or Britney did...
[19:10] <tsimonq2> I have some LXQt stuff synced from Experimental that just isn't migrating. All are valid candidates, and all are completely installable locally
[19:13] <tsimonq2> Can someone give me a hint here? I'm stuck
[19:16] <tsimonq2> infinity, slangasek: ^^^
[19:34] <slangasek> tsimonq2: have you looked at http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt ?
[19:36] <jbicha> slangasek: what are we going to do with s390x autopkgtests that only started failing once we got machine isolation?
[19:36] <jbicha> examples are cockpit, dahdi-linux, gsequencer, gvfs
[19:37] <tsimonq2> slangasek: Yes, and the uninstallable arch has seemingly fluctuated, always works on amd64, and I don't see why those are uninstallable
[19:37] <jbicha> lxcfs
[20:02] <slangasek> jbicha: I gladly accept MPs against lp:~ubuntu-release/britney/hints-ubuntu/ with force-badtest hints for any packages whose test history shows the failure is present in the release pocket
[20:04] <jbicha> slangasek: do you want all/s390x for those ones?
[20:04] <slangasek> jbicha: I prefer pinning to specific package versions and re-reviewing on new uploads
[20:04] <slangasek> tsimonq2: so the uninstallable arch will fluctuate because it's an arch: all package; I don't know specifically why it's not installable; are there lxqt packages not yet ready to migrate?
[20:08] <jbicha> maybe lxqt-config (source & binary) needs to be removed first? since the new lxqt packages break/replace it
[20:08] <tsimonq2> You mean lxqt-common?
[20:08] <tsimonq2> That might work
[20:09] <tsimonq2> slangasek: And yeah, half the stack migrated and half didn't, which is the worst case scenario.
[20:09] <slangasek> it shouldn't be a worst-case scenario if your package dependencies are correct
[20:10] <slangasek> any problems caused by a half-migrated stack through proposed-migration are also issues for dist upgrades
[20:10] <tsimonq2> That's where I need to go and talk to Debian, deps were't done right
[20:10] <slangasek> so the uninstallable package is lxqt; which is from lxqt-metapackages; I don't see how lxqt-config would be related
[20:10] <tsimonq2> And that's migrated already...
[20:11] <tsimonq2> Er
[20:12] <tsimonq2> I *thought* it did
[20:13] <tsimonq2> ...I still don't see how it would be uninstallable
[20:13] <tsimonq2> slangasek: either way, lxqt-common was split upstream and should be removed from Bionic.
[20:14] <tsimonq2> Although I'm not sure if it will make a difference or not...
[20:15] <tsimonq2> slangasek: To answer your earlier question, as far as I can see, everything should be good to migrate, I just don't get why it hasn't already
[20:24] <slangasek> tsimonq2: try a test install of lxqt from -proposed; see which dependencies it pulls from -proposed; work out which of these is missing and not migrating?
[20:24] <slangasek> tsimonq2: alternatively, since lxqt-metapackages makes lxqt uninstallable all by itself, you should be able to pin lxqt-metapackages source and see what it's failing to pull in as a dep
[20:25] <tsimonq2> slangasek: Sure, I'll give it a try.
[20:25] <slangasek> (because there are no differences to the Depends: from 19 to 20 except the versioned dep on lxqt-core, which is not uninstallable)
[20:29] <slangasek> tsimonq2: ah - it is the lxqt-common thing
[20:29] -queuebot:#ubuntu-release- Unapproved: cockpit (artful-backports/universe) [151-1 => 156-1~ubuntu17.10.1] (no packageset)
[20:29] <slangasek> hmm, I think
[20:29] <slangasek> triple-checking
[20:30] -queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (artful-backports) [156-1~ubuntu17.10.1]
[20:30] <tsimonq2> slangasek: Like I said, needs to be removed anyways, so if that's not the answer, no harm done
[20:30] -queuebot:#ubuntu-release- Unapproved: cockpit (zesty-backports/universe) [151-1~ubuntu17.04.1 => 156-1~ubuntu17.04.1] (no packageset)
[20:31] <slangasek> right, but if it were just that, britney would have no problem resolving it
[20:31] -queuebot:#ubuntu-release- Unapproved: cockpit (xenial-backports/universe) [151-1~ubuntu16.04.1 => 156-1~ubuntu16.04.1] (no packageset)
[20:32] -queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (xenial-backports) [156-1~ubuntu16.04.1]
[20:32] -queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (zesty-backports) [156-1~ubuntu17.04.1]
[20:32] <slangasek> ok, I've chased through that dep chain and am back to having no idea
[20:33] <slangasek> new lxqt-session is needed to drop the dep on lxqt-common, but that's already part of the hint
[20:33] <tsimonq2> I'm tempted to no-change-rebuild the things but I doubt that will make a difference
[20:34] <slangasek> it shouldn't make a difference, so please don't
[20:34] <jbicha> I think it's unusual to use a versioned breaks/replaces (when the broken version doesn't even exist anywhere) so maybe that's what's needs manual hinting
[20:35] <slangasek> it's unusual and in fact it's incorrect, but britney isn't supposed to care
[20:35] <tsimonq2> slangasek: Right, not going to do, but it's a passing thought that was worth mentioning imo
[20:36] <acheronuk> tsimonq2: ask me the others day to have a look, and I had no idea, so the above makes me feel better :P
[20:36] <acheronuk> *asked me the other day
[20:37] <tsimonq2> Heh
[20:40] <jbicha> slangasek: it does increase the uninstallability count though, right? I'm just guessing here
[20:41] -queuebot:#ubuntu-release- New: accepted linux-signed-lts-xenial [amd64] (trusty-proposed) [4.4.0-102.125~14.04.1]
[20:50] <slangasek> jbicha: yes, the uninstallable count goes up from 0 to not-0
[20:50] <slangasek> and it's lxqt that becomes uninstallable, and I also can't work out why
[20:51] <slangasek> are there any other binaries that are part of the hinted packages which are dropped in -proposed?
[21:35] <tsimonq2> slangasek: Not that I can see
[21:45] <bdmurray> slangasek: Could you review my django-tastypie Xenial SRU sometime?
[22:13] <jbicha> slangasek: your lxqt hint worked :)
[22:13] <tsimonq2> Oh did it?
[23:04] <slangasek> tsimonq2, jbicha: yeah, I hinted in the minimal set of packages needed in order for lxqt to be installable, to see what happened; and what happened was that britney shook loose the bug :P
[23:21] <slangasek> bdmurray: ok
[23:21] -queuebot:#ubuntu-release- Unapproved: accepted django-tastypie [source] (xenial-proposed) [0.13.3-1~16.04.1]
[23:23] <bdmurray> slangasek: Thanks
[23:41] <tsimonq2> slangasek: \o/
[23:43] -queuebot:#ubuntu-release- Unapproved: apport (artful-proposed/main) [2.20.7-0ubuntu3.5 => 2.20.7-0ubuntu3.6] (core)
[23:44] <tsimonq2> slangasek: Yep, I can confirm, the whole LXQt stack is through, thanks!
[23:45] <tsimonq2> slangasek: Do you think this is preventable in the future or was this Britney being... fun? :)
[23:56] <slangasek> tsimonq2: I haven't diagnosed why britney didn't get it right on its own; it's also a fluke that I don't think I've seen before, and unlikely to be a good use of anyone's time trying to debug now
[23:56] <tsimonq2> Alright