[08:41] <doko> vorlon: the hello autopkg test was meant to replace the libreoffice autopkg test trigger
[09:28] <vorlon> doko: ok, and it's buggy; do you want to fix it?
[09:36] <doko> vorlon: so the correct fix would be to detect the 77 exit status, and then fail in the end with this?
[09:36] <doko> and likely allowing stderr
[11:13] -queuebot:#ubuntu-release- Unapproved: chromium-browser (cosmic-proposed/universe) [71.0.3578.98-0ubuntu0.18.10.1 => 72.0.3626.119-0ubuntu0.18.10.1] (ubuntu-desktop)
[12:04] -queuebot:#ubuntu-release- Unapproved: rejected libunistring [source] (bionic-proposed) [0.9.10-1ubuntu0.1]
[12:06] -queuebot:#ubuntu-release- Unapproved: accepted network-manager-fortisslvpn [source] (bionic-proposed) [1.2.8-1ubuntu1]
[12:09] <Riddell> libxcb update uploaded again should anyone be doing New/SRU queue review https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/1777994
[12:11] -queuebot:#ubuntu-release- Unapproved: accepted qemu [source] (bionic-proposed) [1:2.11+dfsg-1ubuntu7.10]
[12:31] <cpaelzer> thanks
[13:11] <Odd_Bloke> Still looking for a quick hints merge on https://code.launchpad.net/~paelzer/britney/hints-ubuntu-disco-vagrant-mutate/+merge/363463 if anyone has a minute.
[13:12] <Odd_Bloke> (The current version of Vagrant in the release pocket doesn't work with the Virtualbox in the release pocket, which is why I'm keen to get this migrated.)
[13:41] -queuebot:#ubuntu-release- Unapproved: accepted mutter [source] (bionic-proposed) [3.28.3+git20190124-0ubuntu18.04.1]
[13:44] <cpaelzer> sil2100: hi thanks for releasing libpam-mount for bug 1804408 on cosmic
[13:44] <cpaelzer> sil2100: I wonder where the bionic variant of it got lost thou
[13:44] <cpaelzer> I uploaded on the same day, and it was blocked for the 18.04.2 semi-freeze
[13:45] <cpaelzer> but the release of the SUR for cosmic made me re-check and I can't see it in B-proposed nor b-unapproved
[13:45] <cpaelzer> sil2100: I wonder if from the SRU-masters POV you have an idea what happened
[13:46] <cpaelzer> I see no accept/denial nor anything similar
[13:46] <cpaelzer> I'll also double check that I uploaded it back then ....
[13:47] <cpaelzer> Feb  7 17:15 libpam-mount_2.16-3ubuntu0.1_source.ubuntu.upload
[13:47] <cpaelzer> yeah sucessfully uploaded at the same time as the cosmic version (2.16-5ubuntu0.1)
[13:48] <sil2100> cpaelzer: let me finish one review and try to investigate
[13:48] <cpaelzer> sure
[13:49] <cpaelzer> In case "just re-upload it" is an option I can easily do so, but usually if things get lost it is worth to check why :-)
[13:50] -queuebot:#ubuntu-release- Unapproved: accepted gnome-shell [source] (bionic-proposed) [3.28.3+git20190124-0ubuntu18.04.1]
[13:51] <sil2100> cpaelzer: oh, I see it in the Unapproved queue
[13:51] <sil2100> cpaelzer: I'll review it now
[13:51] <cpaelzer> sil2100: stop the "investigation" it is just that the bionic queue is 42 entries long, I'm at #32 and the default view on LP limits to 30 results
[13:51] <sil2100> Probably you didn't see it as it was on the second page ;)
[13:51] <sil2100> Yeah
[13:55] -queuebot:#ubuntu-release- Unapproved: accepted libpam-mount [source] (bionic-proposed) [2.16-3ubuntu0.1]
[13:56] <sil2100> cpaelzer: done ^
[13:57] <cpaelzer> Thank you sil2100
[14:58] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (bionic-proposed/main) [4.18.0-1012.12~18.04.1] (kernel)
[15:02] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (bionic-proposed) [4.18.0-1012.12~18.04.1]
[15:03] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (cosmic-proposed/main) [4.18.0-1012.12] (kernel)
[15:04] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (cosmic-proposed) [4.18.0-1012.12]
[15:04] -queuebot:#ubuntu-release- New binary: linux-signed-azure [amd64] (xenial-proposed/main) [4.15.0-1040.44] (kernel)
[15:12] -queuebot:#ubuntu-release- New: accepted linux-signed-azure [amd64] (xenial-proposed) [4.15.0-1040.44]
[16:36] -queuebot:#ubuntu-release- Unapproved: openssl (bionic-proposed/main) [1.1.0g-2ubuntu4.3 => 1.1.1-1ubuntu2.1~18.04.0] (core) (sync)
[16:36] -queuebot:#ubuntu-release- Unapproved: python3.6 (bionic-proposed/main) [3.6.7-1~18.04 => 3.6.8-1~18.04.1] (core) (sync)
[16:36] -queuebot:#ubuntu-release- Unapproved: python2.7 (bionic-proposed/main) [2.7.15~rc1-1ubuntu0.1 => 2.7.15-4ubuntu4~18.04] (core) (sync)
[16:36] -queuebot:#ubuntu-release- Unapproved: libio-socket-ssl-perl (bionic-proposed/main) [2.056-1 => 2.060-3~ubuntu18.04.0] (core) (sync)
[16:36] -queuebot:#ubuntu-release- Unapproved: nova (bionic-proposed/main) [2:17.0.7-0ubuntu2 => 2:17.0.7-0ubuntu2.1] (openstack, ubuntu-server) (sync)
[16:36] -queuebot:#ubuntu-release- Unapproved: python3.7 (bionic-proposed/universe) [3.7.1-1~18.04 => 3.7.2-1~18.04.1] (no packageset) (sync)
[16:36] -queuebot:#ubuntu-release- Unapproved: ruby-openssl (bionic-proposed/universe) [2.0.5-1build3 => 2.0.9-0ubuntu1] (no packageset) (sync)
[16:36] -queuebot:#ubuntu-release- Unapproved: libnet-ssleay-perl (bionic-proposed/main) [1.84-1build1 => 1.84-1ubuntu0.1] (core) (sync)
[16:36] -queuebot:#ubuntu-release- Unapproved: r-cran-openssl (bionic-proposed/universe) [1.0.1-1ubuntu1 => 1.0.1-1ubuntu1.1] (no packageset) (sync)
[16:36] -queuebot:#ubuntu-release- Unapproved: python-cryptography (bionic-proposed/main) [2.1.4-1ubuntu1.2 => 2.1.4-1ubuntu1.3] (core) (sync)
[16:36] -queuebot:#ubuntu-release- Unapproved: ruby2.5 (bionic-proposed/main) [2.5.1-1ubuntu1.1 => 2.5.1-1ubuntu1.3] (kubuntu, ubuntu-desktop, ubuntu-server) (sync)
[16:50] <juliank> Laney, sil2100, vorlon Should we add any other fields to the autopkgtest journals? I'm not sure what we could be interested in. We could tag failing result logs by exit code, for example
[16:51] <juliank> Then we could do queries by exit code
[16:51] <juliank> but it would only show results, and miss the head of the run
[16:52] <juliank> I feel like we should have a common word we can all configure highlights on, so people can ping about autopkgtest stuff
[16:54] <infinity> juliank: Jabberwocky.
[16:55] <juliank> infinity: i don't like
[16:55] <juliank> I thought @adt but that's too obscure
[16:55] <xnox> argggg
[16:56] <xnox> g
[16:56] <xnox> used wrong from email again
[16:57] <xnox> oh, i am subscribed
[16:57] <infinity> juliank: https://www.youtube.com/watch?v=spyJ5yxTfas
[16:57] <xnox> ah
[16:57] <xnox> The reason it is being held:
[16:57] <xnox>     Too many recipients to the message
[16:57] <xnox> infinity, if you please moderate that email?! =)
[16:57] <infinity> xnox: ... to?
[16:58] <Laney> juliank: cloud region would be good
[16:58] <xnox> infinity,     https://lists.ubuntu.com/mailman/confirm/ubuntu-release/3cbf130433d6a020d9b281155971e932f36bcb74 ubuntu-release mailing list
[16:58] <xnox> infinity, but that's my post/no-post url....
[16:58] <infinity> xnox: The name of the list would have been enough. :P
[16:58] <xnox> ah
[16:58]  * xnox is mailman failure
[16:59]  * Laney tries... to... resist...
[16:59] <Laney> s/mailman //
[16:59] <Laney> sorry :(
[16:59] <juliank> Laney: OK, but we can query for that by limiting on the @<cloud>*.service already, so it doesn ot at
[17:00] <juliank> but that applies to arch too, so...
[17:01] <juliank> We could also differentiate between upstream tests and ubuntu and huge queue tests
[17:01] <juliank> I have no idea how much space this eats
[17:01] <juliank> Gotta read up on the journal format :)
[17:02] <xnox> infinity, also, what did i just watch?!!!!!!!
[17:02] <infinity> xnox: Jabberwocky!  You don't know what it is?
[17:03] <Laney> juliank: the journal is supposed to auto prune anyway, so I wouldn't worry about that
[17:04] <Laney> although it did stop doing that and fill up the disk the other day ...
[17:04] <juliank> +1
[17:04] <xnox> infinity, no idea
[17:04] <xnox> https://www.youtube.com/watch?v=WQVFe8TbFi4 -> this is now on autoplay
[17:04] <infinity> xnox: (That's the joke)
[17:05] <xnox> i'm confused what the show is
[17:05] <Laney> it might be nice to make the other scripts log to the journal too, with some nice metadata
[17:05] <infinity> The show is Better off Ted.  Some of the better TV ever written.
[17:05] <Laney> the maintenance job / the daily image building / ...
[17:05] <xnox> wait is that the 6 parallel / perpendicular lines, with weird colors?!
[17:05] <xnox> ah
[17:05] <Laney> interesting interleaving of conversations, here
[17:06] <xnox> it's unrelated, but added this on autoplay https://www.youtube.com/watch?v=BKorP55Aqvg
[17:07] <juliank> Laney: FWIW, I just removed the attached card you wanted access to. It was the card for scheduling our session
[17:07] <Laney> ok
[17:07] <juliank> it was only supposed to link from "schedule session" -> "https://trello.com/c/wvz1NPzD/26-adding-a-second-cloud-worker" but trello said it would recommended bidirectional ...
[17:40] <vorlon> doko: if it's exit status 77, we shouldn't fail, based on the definition of the upstream test
[17:41] <vorlon> doko: autopkgtest doesn't honor exit status 77, that's (apparently?) an automake thing
[19:03] <tsimonq2> vorlon: css> ack
[20:51] <ginggs> vorlon, doko: any ideas about pandas test regression on ppc64el? ../../../usr/lib/python2.7/dist-packages/pandas/tests/series/test_analytics.py::TestSeriesAnalytics::test_sum_overflow[True] Killed
[20:51] <ginggs> same test passes during the build
[21:04] <mwhudson> ginggs: oom?
[21:06] <ginggs> mwhudson: could be, thanks - how can i prove, or avoid that?
[21:07] <mwhudson> ginggs: no idea to be honest
[21:07] <mwhudson> ginggs: you can mark a package as "big" which means its tests run in a vm with more ram
[21:16] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop amd64 [Xenial 16.04.6] has been marked as ready
[21:16] -queuebot:#ubuntu-release- Builds: Kubuntu Desktop i386 [Xenial 16.04.6] has been marked as ready
[21:43] -queuebot:#ubuntu-release- Unapproved: gnome-desktop3 (cosmic-proposed/main) [3.30.2-0ubuntu1 => 3.30.2.1-0ubuntu1] (ubuntu-desktop)
[23:41] <tumbleweed> vorlon: looks like reverse-depends has been broken since the 9th. Looking at it...
[23:47] <tsimonq2> Laney: Looking at bug 1654761 again, new code up at https://code.launchpad.net/~tsimonq2/autopkgtest-cloud/+git/bug-1654761/+merge/363643
[23:48] <tsimonq2> I think I have a much better grasp of the situation this time around (and my programming skills have improved :P)