[00:10] -queuebot:#ubuntu-release- New: accepted chaosread [arm64] (disco-proposed) [1.1-1]
[00:10] -queuebot:#ubuntu-release- New: accepted chaosread [ppc64el] (disco-proposed) [1.1-1]
[00:10] -queuebot:#ubuntu-release- New: accepted libnfs [armhf] (disco-proposed) [3.0.0-1]
[00:10] -queuebot:#ubuntu-release- New: accepted utox [armhf] (disco-proposed) [0.17.0-1]
[00:10] -queuebot:#ubuntu-release- New: accepted chaosread [armhf] (disco-proposed) [1.1-1]
[00:10] -queuebot:#ubuntu-release- New: accepted utox [arm64] (disco-proposed) [0.17.0-1]
[00:10] -queuebot:#ubuntu-release- New: accepted libnfs [arm64] (disco-proposed) [3.0.0-1]
[00:10] -queuebot:#ubuntu-release- New: accepted utox [ppc64el] (disco-proposed) [0.17.0-1]
[00:10] -queuebot:#ubuntu-release- New: accepted chaosread [amd64] (disco-proposed) [1.1-1]
[00:10] -queuebot:#ubuntu-release- New: accepted chaosread [s390x] (disco-proposed) [1.1-1]
[00:10] -queuebot:#ubuntu-release- New: accepted libnfs [i386] (disco-proposed) [3.0.0-1]
[00:10] -queuebot:#ubuntu-release- New: accepted python-shade [amd64] (disco-proposed) [1.30.0-1]
[00:10] -queuebot:#ubuntu-release- New: accepted utox [i386] (disco-proposed) [0.17.0-1]
[00:11] -queuebot:#ubuntu-release- New: accepted chaosread [i386] (disco-proposed) [1.1-1]
[00:11] -queuebot:#ubuntu-release- New: accepted libnfs [ppc64el] (disco-proposed) [3.0.0-1]
[00:11] -queuebot:#ubuntu-release- New: accepted utox [s390x] (disco-proposed) [0.17.0-1]
[00:11] -queuebot:#ubuntu-release- New: accepted dh-vim-addon [amd64] (disco-proposed) [0.1]
[00:11] -queuebot:#ubuntu-release- New: accepted utox [amd64] (disco-proposed) [0.17.0-1]
[00:11] -queuebot:#ubuntu-release- New: accepted libnfs [amd64] (disco-proposed) [3.0.0-1]
[00:11] -queuebot:#ubuntu-release- New: accepted libnfs [s390x] (disco-proposed) [3.0.0-1]
[05:14] -queuebot:#ubuntu-release- New binary: distorm3 [amd64] (disco-proposed/universe) [3.4.1-3] (no packageset)
[08:11] <acheronuk> something wrong with autotest runners, or the status reporting from them?
[08:12] <acheronuk> I see many tests as running for 7 hrs plus, that never normally would
[08:22] <acheronuk> a lot seem to be stuck at "dpkg-buildpackage: info: binary-only upload (no source included)"
[08:22] <acheronuk> maybe it will clear in a bit, but that seems odd
[08:31] -queuebot:#ubuntu-release- New: accepted distorm3 [amd64] (disco-proposed) [3.4.1-3]
[09:52] <acheronuk> processing of the test queue for amd64, i386, s390x does seem to be stalled, or at least desperately slow
[10:02] <Laney> It's doing stuff
[10:02] <Laney> KDE's tests don't really help, as always
[10:10] <acheronuk> typically as soon as someone else looks, the things that did seem stalled seem to have exited at least. :/
[10:10] <acheronuk> thanks
[10:11] <acheronuk> and for example the amd64 queue just dropped from 105 to 62 in one page refresh, which is quite suss
[10:12] <acheronuk> anyway, as long as things are moving :)
[10:12] <acheronuk> then back up to 105! odd
[10:13] <acheronuk> may have clicked an old unrefreshed tab there. apologies
[10:36] <dgadomski> hi rbasak, could you please publish cups for Xenial (2.1.3-4ubuntu0.7), Bionic (2.2.7-1ubuntu2.3) and Cosmic (2.2.8-5ubuntu1.2)?
[10:44] <rbasak> dgadomski: have you looked at the failures on the pending-sru page please?
[10:56] <dgadomski> rbasak: is the failed build for s390 blocking the release?
[11:28] <rbasak> dgadomski: yes, and also the autopkgtest failures.
[11:28] <rbasak> (which need examining to see if they are false positives)
[11:29] <dgadomski> ack, I see, thanks for explaining that
[12:21] <ahasenack> everytime ocfs2-tools is synced from debian, we have to update a hint for s390x:
[12:21] <ahasenack> # Was skipped in lxc, never passed in a vm, not supported on big-endian
[12:21] <ahasenack> # https://github.com/markfasheh/ocfs2-tools/issues/22
[12:21] <ahasenack> force-badtest ocfs2-tools/1.8.5-6ubuntu1/s390x
[12:21] <gitbot> markfasheh issue 22 in ocfs2-tools "o2image fails on s390x (big endian)" [Open]
[12:21] <ahasenack> question: shouldn't we just skip the test in that arch?
[12:23] <ahasenack> or maybe even not build it for s390x, I'm not sure how impacting the lack of support for big-endian is, if it's just some tool that fails, or the whole thing is useless there
=== Beret- is now known as Beret
[13:38] -queuebot:#ubuntu-release- Unapproved: libreoffice (cosmic-proposed/main) [1:6.1.3-0ubuntu0.18.10.2 => 1:6.1.4-0ubuntu0.18.10.1] (kubuntu, ubuntu-desktop)
[13:40] -queuebot:#ubuntu-release- Unapproved: libreoffice-l10n (cosmic-proposed/main) [1:6.1.3-0ubuntu0.18.10.2 => 1:6.1.4-0ubuntu0.18.10.1] (ubuntu-desktop)
[14:15] -queuebot:#ubuntu-release- Unapproved: grub2-signed (trusty-proposed/main) [1.34.17 => 1.34.18] (core)
[14:15] -queuebot:#ubuntu-release- Unapproved: grub2 (trusty-proposed/main) [2.02~beta2-9ubuntu1.15 => 2.02~beta2-9ubuntu1.16] (core)
[14:16] <cyphermox> rbasak: would you have time to review grub2, grub2-signed in trusty unapproved? just the newer upload I just did, it includes what was already in the queue
[14:34] <rbasak> cyphermox: looks big and scary :(
[14:34] <Laney> doko: hi there, could you look at the openjdk-lts tests please? something's changed and they're trying to create over 6G of artifacts and this is breaking stuff
[14:34] <rbasak> Maybe best to leave it to someone more familiar?
[14:35] <Laney> no results, because the test runs are breaking and not failing
[14:36] <Laney> well, you can have https://paste.ubuntu.com/p/mkcpP5htT4/
[14:37] <tdaitx> Laney: do you mean it is leaving 6+ GB of data in the artifact directory after runs?
[14:38] <tdaitx> it might create a lot of data there but should remove those after each test
[14:38] <Laney> hey tdaitx, that's right
[14:39] <Laney> Seems it's not cleaning it up in some cases, maybe when it fails?
[14:39] <Laney> that pastebin shows the 'jdk' test is failing
[14:39] <tdaitx> hmm, it should clean up even when killed
[14:39] <tdaitx> I will take a look and try to reproduce
[14:40] <Laney> it's mostly in the JTwork directory, you can see some ENOSPC errors at the end
[14:40] <Laney> thanks!
[14:40] <Laney> in the meantime I blacklisted it so we don't kill more things while this is unfixed
[14:40] <Laney> let me know when to remove that
[14:44] <cyphermox> rbasak: sorry, pretty much everything I do is big and scary
[14:45] <cyphermox> fwiw, it's a straight backport of patches in other releases already. they had no meaningful changes (just quilt refresh for two or three patches)
[14:46] <cyphermox> but that's why it'll be in -proposed so we can make sure everything works
[15:05] <juliank> I'm retrying all mariadb-10.1 failures against the proposed one now
[15:07] <juliank> done. this should unblock rsync, krb5, and jemalloc
[15:13] <rbasak> juliank: thank you for sorting mariadb-10.1.
[15:13] <rbasak> I'm just about to upload a mysql-5.7 to unstable with your fix
[15:14] <rbasak> Incidentally a mariadb-10.3 is available in unstable (and has been for a few weeks)
[15:14] <rbasak> It isn't getting autosynced because it takes over libmariadbclient18 AFAICT
[15:14] <rbasak> However I'm also planning MySQL 8.0 real soon now.
[15:14] <rbasak> So I might leave MariaDB alone for a bit.
[15:15] <juliank> rbasak: mariadb used "2030-12-31 21:01:22" as the fix, btw, so that gives us a bit more time until it breaks again
[15:22] <juliank> excuses says wget-udeb/amd64 unsatisfiable Depends: libpcre3-udeb (>= 1:8.35)
[15:22] <juliank> what's going on there?
[15:22] <juliank> it seems libpcre3-udeb moved to universe, while wget-udeb is still in main?
[15:23] <juliank> wget{,-udeb} in proposed was built against pcre2 for a few hours yesterday
[15:23] <juliank> but I reuploaded it to build against pcre3 as pcre2 is not in main yet
[15:42] -queuebot:#ubuntu-release- Unapproved: syslinux (cosmic-proposed/main) [3:6.04~git20171011.af7e95c3+dfsg1-4ubuntu1 => 3:6.04~git20171011.af7e95c3+dfsg1-4ubuntu1.18.10.1] (core)
[15:51] <cyphermox> rbasak: would you prefer I ask someone else about grub2?
[16:01] <bdmurray> sil2100: Could you have a look at my archive-tools MP?
[16:03] <rbasak> cyphermox: yes. Sorry, I thought I conveyed that earlier.
[16:16] <cyphermox> rbasak: wasn't obvious. okay, will do :)
[16:19] <cyphermox> vorlon: bdmurray: would one of you have time to review the grub2 in trusty unapproved queue please? I'm asking because you might have reviewed such a Secure Boot backport SRU before.
[16:20] <bdmurray> cyphermox: Probably not today, but maybe tomorrow
[16:20] <cyphermox> thanks
[16:23] <sil2100> bdmurray: sure
[16:24] <sil2100> Just need a few moments
[16:33] <sil2100> bdmurray: ah, so it was a bug I did not see those yellow ones when switching to Incomplete
[16:33] <sil2100> And I thought it was just me doing something funny
[16:42] <sil2100> bdmurray: I remember this working before, did the task self_link change?
[16:58] <juliank> Laney: I merged the in-archive autopkgtest to 5.7, maybe that fixes its failing autopkgtests
[16:59] <juliank> I wonder if we should not build the in-archive one from our git one
[16:59] <juliank> with the changes we actually run with in it
[17:00] <Laney> there are no changes any more
[17:01] <juliank> Well, if there are any again
[17:01] <juliank> The in-archive one still has lxd changes from stgraber
[17:02] <juliank> oh, the new autopkgtest already is in proposed
[17:02] <juliank> silly me
[17:02] <juliank> and it fails to
[17:03] <juliank> o
[17:03] <juliank> Also, autopkgtest with qemu backend fails completely for me
[17:03] <Laney> #debci might be able to help
[17:03] <juliank> just times out setting up
[17:03] <Laney> for both of those
[17:03] <juliank> right
[17:04] <juliank> I'll let tomorrow julian talk there
[17:04] <Laney> there are recent qemu fixes in git, not sure if those are in 5.7 or not
[17:04]  * Laney runs from a clone
[17:04] <Laney> (& qemu was working today)
[17:05] <juliank> ok
[17:05] <juliank> I'll check that
[17:07]  * Laney high fives cascardo for that
[17:21] <ahasenack> hints update for ocfs2-tools: https://code.launchpad.net/~ahasenack/britney/ocfs2-s390x/+merge/361556
[17:23] -queuebot:#ubuntu-release- New binary: uglify-js [amd64] (disco-proposed/universe) [3.4.9-1] (no packageset)
[17:37] -queuebot:#ubuntu-release- New binary: rdkit [s390x] (disco-proposed/universe) [201809.1+dfsg-3] (no packageset)
[17:38] -queuebot:#ubuntu-release- New binary: rdkit [amd64] (disco-proposed/universe) [201809.1+dfsg-3] (no packageset)
[17:41] -queuebot:#ubuntu-release- New binary: rdkit [ppc64el] (disco-proposed/universe) [201809.1+dfsg-3] (no packageset)
[17:54] -queuebot:#ubuntu-release- New binary: rdkit [i386] (disco-proposed/universe) [201809.1+dfsg-3] (no packageset)
[19:01] -queuebot:#ubuntu-release- New binary: rdkit [arm64] (disco-proposed/universe) [201809.1+dfsg-3] (no packageset)
[19:14] -queuebot:#ubuntu-release- New binary: rdkit [armhf] (disco-proposed/universe) [201809.1+dfsg-3] (no packageset)
[23:10] -queuebot:#ubuntu-release- Unapproved: ufw (cosmic-proposed/main) [0.35-6 => 0.36-0ubuntu0.18.10.1] (core)
[23:11] -queuebot:#ubuntu-release- Unapproved: ufw (bionic-proposed/main) [0.35-5 => 0.36-0ubuntu0.18.04.1] (core)
[23:14] -queuebot:#ubuntu-release- New binary: exempi [s390x] (disco-proposed/main) [2.5.0-2] (kubuntu, ubuntu-desktop)
[23:15] -queuebot:#ubuntu-release- New binary: exempi [ppc64el] (disco-proposed/main) [2.5.0-2] (kubuntu, ubuntu-desktop)
[23:16] -queuebot:#ubuntu-release- New binary: exempi [amd64] (disco-proposed/main) [2.5.0-2] (kubuntu, ubuntu-desktop)
[23:16] -queuebot:#ubuntu-release- New binary: exempi [i386] (disco-proposed/main) [2.5.0-2] (kubuntu, ubuntu-desktop)
[23:18] -queuebot:#ubuntu-release- New binary: uglify-js [amd64] (disco-proposed/universe) [3.4.9-2] (no packageset)
[23:24] -queuebot:#ubuntu-release- New binary: exempi [armhf] (disco-proposed/main) [2.5.0-2] (kubuntu, ubuntu-desktop)
[23:25] -queuebot:#ubuntu-release- New binary: exempi [arm64] (disco-proposed/main) [2.5.0-2] (kubuntu, ubuntu-desktop)