[00:01] -queuebot:#ubuntu-release- New: accepted dcmtk [amd64] (hirsute-proposed) [3.6.5-1]
[00:01] -queuebot:#ubuntu-release- New: accepted dcmtk [s390x] (hirsute-proposed) [3.6.5-1]
[00:01] -queuebot:#ubuntu-release- New: accepted ycm-cmake-modules [amd64] (hirsute-proposed) [0.12.0-1]
[00:01] -queuebot:#ubuntu-release- New: accepted dcmtk [ppc64el] (hirsute-proposed) [3.6.5-1]
[00:01] -queuebot:#ubuntu-release- New: accepted ruby-simpleidn [amd64] (hirsute-proposed) [0.1.1-2]
[00:02] -queuebot:#ubuntu-release- New: accepted ruby-simpleidn [amd64] (hirsute-proposed) [0.1.1-1]
=== guiverc2 is now known as guiverc
[01:44] <valorie> tjaalton: that sounds like an important one
[02:57] -queuebot:#ubuntu-release- Unapproved: snapd-glib (groovy-proposed/main) [1.57-0ubuntu4 => 1.58-0ubuntu0.20.10.0] (desktop-core, i386-whitelist, ubuntu-server)
[03:57] -queuebot:#ubuntu-release- Unapproved: snapd-glib (focal-proposed/main) [1.57-0ubuntu3 => 1.58-0ubuntu0.20.04.0] (desktop-core, i386-whitelist)
[05:16] -queuebot:#ubuntu-release- New binary: libavif [amd64] (hirsute-proposed/universe) [0.8.3-1] (no packageset)
[05:16] -queuebot:#ubuntu-release- New binary: libavif [s390x] (hirsute-proposed/universe) [0.8.3-1] (no packageset)
[05:16] -queuebot:#ubuntu-release- New binary: libavif [ppc64el] (hirsute-proposed/universe) [0.8.3-1] (no packageset)
[05:22] -queuebot:#ubuntu-release- New binary: nim-d3 [amd64] (hirsute-proposed/universe) [0.1.3-1] (no packageset)
[05:22] -queuebot:#ubuntu-release- New binary: pageedit [amd64] (hirsute-proposed/universe) [1.3.0+dfsg1-1] (no packageset)
[05:25] -queuebot:#ubuntu-release- New binary: libavif [armhf] (hirsute-proposed/universe) [0.8.3-1] (no packageset)
[05:26] -queuebot:#ubuntu-release- New binary: libavif [arm64] (hirsute-proposed/universe) [0.8.3-1] (no packageset)
[05:29] -queuebot:#ubuntu-release- New binary: libavif [riscv64] (hirsute-proposed/universe) [0.8.3-1] (no packageset)
[05:41] -queuebot:#ubuntu-release- New binary: pageedit [arm64] (hirsute-proposed/universe) [1.3.0+dfsg1-1] (no packageset)
[05:49] -queuebot:#ubuntu-release- New binary: pageedit [armhf] (hirsute-proposed/universe) [1.3.0+dfsg1-1] (no packageset)
[08:37] -queuebot:#ubuntu-release- New: accepted libavif [amd64] (hirsute-proposed) [0.8.3-1]
[08:37] -queuebot:#ubuntu-release- New: accepted libavif [armhf] (hirsute-proposed) [0.8.3-1]
[08:37] -queuebot:#ubuntu-release- New: accepted libavif [riscv64] (hirsute-proposed) [0.8.3-1]
[08:38] -queuebot:#ubuntu-release- New: accepted nim-d3 [amd64] (hirsute-proposed) [0.1.3-1]
[08:38] -queuebot:#ubuntu-release- New: accepted pageedit [arm64] (hirsute-proposed) [1.3.0+dfsg1-1]
[08:38] -queuebot:#ubuntu-release- New: accepted libavif [arm64] (hirsute-proposed) [0.8.3-1]
[08:38] -queuebot:#ubuntu-release- New: accepted libavif [s390x] (hirsute-proposed) [0.8.3-1]
[08:38] -queuebot:#ubuntu-release- New: accepted pageedit [armhf] (hirsute-proposed) [1.3.0+dfsg1-1]
[08:38] -queuebot:#ubuntu-release- New: accepted libavif [ppc64el] (hirsute-proposed) [0.8.3-1]
[08:38] -queuebot:#ubuntu-release- New: accepted pageedit [amd64] (hirsute-proposed) [1.3.0+dfsg1-1]
[09:29] <Laney> vorlon: now fix the graph at the bottom there :>
[09:59] <juliank> Laney: I want to add short_tests option and add aptdaemon to it, make it timeout after 30 minutes; because sometimes it gets stuck completely and sits around for 2.5 hours doing nothing
[09:59] <juliank> well most of the time :D
[10:00] <juliank> most of the time on armhf that is
[10:00] <Laney> isn't that better to do in your test itself?
[10:01] <juliank> Laney: No idea how I'd sensibly built a timeout in there
[10:02] <Laney> I mean fix the bug where it's getting stuck
[10:03] <juliank> Now that's even harder :D
[10:03] <juliank> There's a race somewhere I presume
[10:04] <juliank> should add idle timeout to tests
[10:06] <juliank> tests run with --disable-timeout and then get stuck waiting on timeout
[10:14] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [amd64] (hirsute-proposed) [2.04-1ubuntu36]
[10:14] -queuebot:#ubuntu-release- Unapproved: accepted grub2 [arm64] (hirsute-proposed) [2.04-1ubuntu36]
[10:14] <sil2100> Eickmeyer: hey! I don't see a re-upload of agordejo in NEW yet, is that still in progress?
[10:35] <juliank> Laney: So I think I found where britney goes wrong with trigger generation, but I need to do some testing and analyze why it's there in the first place
[10:35] <juliank> Laney: e.g. dogtail has trigger  "apache2/2.4.46-1ubuntu1", which is in release pocket for ages
[10:38] <Laney> juliank: yeah, did you see the code that does that?#
[10:40] <Laney> juliank: you might want to discuss this with elbrus rather than me though, he should know this area better
[10:40] <Laney> or in addition to me, i.e. in #debian-release maybe
[10:40] <juliank> Laney: There's code in                 if binary not in source_data_srcdist.binaries: that seems to add that
[10:40] <juliank> Laney: I can't get the test suite to run without errors though
[10:42] <juliank> py.test-3  tests/test_policy.py  should work ...
[10:44] <Laney> I might have broken that one, I never ran it 🙈
[10:45] <juliank> aha
[10:45] <Laney> juliank: it seems to work on the upstream branch, so either feel free to fix those
[10:45] <Laney> orrrr just do it on that branch
[10:45] <Laney> would prefer the latter if you would submit it to debian too :-)
[10:45] <juliank> Laney: Oh I think the reason is that we have PARTIAL_UNSTABLE; which merges testing into unstable to make it whole
[10:46] <juliank> Laney: Hence it sees the package as being in unstable and adds a trigger
[10:46] <juliank> hmm
[10:46] <juliank> or not?
[10:47] <juliank> that shouldn't happen with full unstable either
[10:47] <juliank> debian/master seems better, buts till fails
[10:48] -queuebot:#ubuntu-release- New binary: llvm-toolchain-11 [riscv64] (focal-proposed/universe) [1:11.0.0-2~ubuntu20.04.1] (i386-whitelist)
[10:48] <juliank> just one error, though
[11:30] <Laney> bah, amd64 all-proposed (perl) runs are falling over because grub2-signed
[11:31]  * Laney retries the build to get it out of depwait faster
[11:40] <juliank> I need to rewrite my excuses filtering tool, it takes like 2 minutes right now
[11:40] <juliank> rewrite in a faster language than python
[11:40] <Laney> good chance to learn rust!
[11:40] <juliank> It basically spends all time in yaml.safe_load
[11:40] <juliank> Laney: Basically just need an insanely fast yaml library
[11:41] <juliank> or I should just parse the html instead
[11:41] <juliank> The tool asks notmuch which packages I last uploaded (from:archive subject:hirsute) and then creates an excuses.html with just those packages
[11:42] <juliank> So I can quickly track my own uploads
[11:42] <Laney> not sure I'd be bothered by 2 minutes to be honest, would timer it and forget
[11:42] <Laney> but you do you :-)
[11:42] <juliank> It's now in a crontab
[11:43] <juliank> pulling excuses every 30 mins and parsing them
[11:45] <juliank> Laney: I want to allow autopkgtest-cloud to allow migration-reference/0 as a trigger, such that you can manually retrigger with that and it does the baseline reset in britney
[11:46] <juliank> So, manual baseline retesting :D
[11:46] <juliank> Avoids the need to have these force-reset-test things set manually
[11:47] <Laney> maybe, if you enforce no other triggers are allowed there
[11:48] <Laney> but I'm not sure, part of what we wanted to see was the baseline test happening as often as possible so we actually catch the regressions near to where they happen rather than a random period later
[11:48] <juliank> Laney: That's what we still want, yes
[11:48] <Laney> I think using reference triggers to implement baseline retesting is a decent enough idea though
[11:49] <juliank> Laney: But allowing manual run of the baseline retest _as well_ (or first) is useful too IMO
[11:49] <Laney> dunno, it's basically allowing everyone to potentially add hints
[11:49] <Laney> the first thing to happen will be someone scripts this
[11:49] <Laney> and then we have the behaviour we don't want
[11:49] <juliank> heh
[11:50] <Laney> you could maybe restrict it to ubuntu-release?
[11:50] <Laney> but still not 100% sure
[11:51] <juliank> OTOH, if it does that weekly anyway, you get "hints" on a weekly basis anyway
[11:51] <juliank> wITHOUt release team control
[11:52] <Laney> not weekly, as often as possible - but indeed, the point is to have the delta be small enough to be assessable by a human at which point we've said hinting is "fine"
[11:52] <Laney> what'll happen if you let anyone schedule these is: regression, baseline trigger, hint, migrate
[11:52] <Laney> and the delta will be potentially huge and unworkable
[11:55] <Laney> we're no closer to understanding what actually broke the thing, which is the idea
[11:55] <juliank> true that
[12:06] -queuebot:#ubuntu-release- New binary: qclib [s390x] (hirsute-proposed/universe) [2.2.1-0ubuntu1] (no packageset)
[12:20] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-11 [amd64] (focal-proposed) [1:11.0.0-2~ubuntu20.04.1]
[12:20] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-11 [armhf] (focal-proposed) [1:11.0.0-2~ubuntu20.04.1]
[12:20] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-11 [ppc64el] (focal-proposed) [1:11.0.0-2~ubuntu20.04.1]
[12:20] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-11 [s390x] (focal-proposed) [1:11.0.0-2~ubuntu20.04.1]
[12:20] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-11 [arm64] (focal-proposed) [1:11.0.0-2~ubuntu20.04.1]
[12:20] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-11 [riscv64] (focal-proposed) [1:11.0.0-2~ubuntu20.04.1]
[12:20] -queuebot:#ubuntu-release- New: accepted llvm-toolchain-11 [i386] (focal-proposed) [1:11.0.0-2~ubuntu20.04.1]
[12:56] <doko> Laney: are all ppc64el autopkg testers enabled?
[12:56] <Laney> doko: They are now, see IS channel backlog
[12:56] <doko> ta
[12:57] <Laney> well "all" is 50% of "all", but we can't do anything about that really
[12:58]  * Laney and stgraber have been raising that problem, has now been assigned to a sysadmin so should hopefully get moving soon
[13:04] <Laney> juliank: btw, if you want to look into something autopkgtest-ish, lots of the x86 jobs are failing with '/tmp/autopkgtest-run-wrapper: command not found', and I have no idea what that is about, how can that not be there? disk problems on the compute hosts?
[13:05] <Laney> they retry and usually succeed but it's still making it slower than it needs to be
[13:05] <juliank> Laney: hmm that's odd stuff
[13:05] <juliank> Laney: Please cherry-pick my britney commit from debian :D
[13:05] <juliank> For the trigger stuff
[13:06] <Laney> yeah, will do later
[13:06] <Laney> I actually have a full rebase prepared
[13:06] <juliank> that's nicer
[13:06] <Laney> but I have kept it away from LP
[13:06] <Laney> until all this stuff is finished, don't want to risk it
[13:06] <juliank> I think I'm done with universe merges too, nothing interesting in there
[13:07] <juliank> I can merge without testing of course
[13:07] <juliank> but meh
[13:11] <Laney> and some mysterious tar failures (tar is used to copy the package being tested back to the controller if the machine needs to be recreated for some reason)
[13:11] <Laney> have a suspicion something is unhealthy in one of the x86 clouds
[13:27] -queuebot:#ubuntu-release- Unapproved: s390-tools (hirsute-proposed/main) [2.14.0-1ubuntu1 => 2.14.0-2ubuntu1] (core)
[13:35] -queuebot:#ubuntu-release- Unapproved: qemu (groovy-proposed/main) [1:5.0-5ubuntu9 => 1:5.0-5ubuntu9.1] (ubuntu-server, virt)
[13:36] -queuebot:#ubuntu-release- Unapproved: qemu (focal-proposed/main) [1:4.2-3ubuntu6.8 => 1:4.2-3ubuntu6.9] (ubuntu-server, virt)
[13:46] <cpaelzer> There is movement on the Debian fio package (some issues in hirsute proposed), I'd want to get our testing fixed before it gets auto-synced
[13:47] <cpaelzer> therefore I wanted to ask if a ubuntu-release member could check if https://code.launchpad.net/~paelzer/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/393641 makes sense and could be applied
[14:02] -queuebot:#ubuntu-release- New: accepted microcode-initrd [source] (focal-proposed) [2~20.04.0]
[14:05] -queuebot:#ubuntu-release- New binary: microcode-initrd [amd64] (focal-proposed/none) [2~20.04.0] (no packageset)
[14:14] -queuebot:#ubuntu-release- New: accepted microcode-initrd [amd64] (focal-proposed) [2~20.04.0]
[14:33] <GunnarHj> Anybody who can take a look at this MR:
[14:33] <GunnarHj> https://code.launchpad.net/~gunnarhj/britney/+git/hints-ubuntu/+merge/393650
[14:33] <GunnarHj> It's a real issue with isenkram-cli and reported to Debian. My thought is to prevent it from blocking the migration of several packages until the issue gets fixed.
[14:36] -queuebot:#ubuntu-release- Unapproved: adcli (groovy-proposed/main) [0.9.0-1ubuntu1 => 0.9.0-1ubuntu1.1] (ubuntu-desktop, ubuntu-server)
[14:46] <seb128> if not, https://autopkgtest.ubuntu.com/packages/i/isenkram/hirsute/amd64 , the gtk!=-3.0 hirsute version got retried and failed the same way so it's not a gtk regression, could we get gtk unblocked?
[15:25] <Eickmeyer[m]> sil2100: Yes, still in progress, but teward has ERR:DayJob
[15:25] <teward> and a stomach bug again on top of that.
[15:25] <Eickmeyer[m]> Oof
[15:26] -queuebot:#ubuntu-release- New source: python-pytest-flake8 (groovy-proposed/primary) [1.0.6-2~20.10]
[15:26] <sil2100> Ouch!
[15:26] <sil2100> Eickmeyer[m], teward: just give me a pong once it's uploaded
[15:30] <GunnarHj> seb128: L_aney merged the MR after changing from badtest to reset-test.
[15:30] <seb128> GunnarHj, ah, nice
[15:39] -queuebot:#ubuntu-release- New: accepted python-pytest-flake8 [source] (focal-proposed) [1.0.6-2~20.04]
[15:42] -queuebot:#ubuntu-release- New: accepted python-pytest-flake8 [source] (groovy-proposed) [1.0.6-2~20.10]
[15:42] -queuebot:#ubuntu-release- New binary: python-pytest-flake8 [amd64] (focal-proposed/none) [1.0.6-2~20.04] (no packageset)
[15:45] -queuebot:#ubuntu-release- New binary: python-pytest-flake8 [amd64] (groovy-proposed/none) [1.0.6-2~20.10] (no packageset)
[15:53] -queuebot:#ubuntu-release- New: accepted python-pytest-flake8 [amd64] (focal-proposed) [1.0.6-2~20.04]
[15:53] -queuebot:#ubuntu-release- New: accepted python-pytest-flake8 [amd64] (groovy-proposed) [1.0.6-2~20.10]
=== _hc[m] is now known as _hc
[17:35] -queuebot:#ubuntu-release- New binary: qwertone [ppc64el] (hirsute-proposed/universe) [0.3.0-2] (no packageset)
[17:35] -queuebot:#ubuntu-release- New binary: qwertone [s390x] (hirsute-proposed/universe) [0.3.0-2] (no packageset)
[17:39] -queuebot:#ubuntu-release- New binary: qwertone [amd64] (hirsute-proposed/universe) [0.3.0-2] (no packageset)
[17:41] <juliank> sru-team
[17:41] <juliank> https://github.com/dino/dino/compare/v0.1.0...v0.1.1
[17:41] <juliank> dino-im want's to update to 0.1.1 in stable releases
[17:42] <juliank> I don't really have any experience with updating graphical applications, and there don't seem to be any tests added, so I don't think there's a huge test suite checking regressions
[17:42] <juliank> But then almost all of these bug fixes seem important
[17:43] <juliank> So I'm not sure how to do SRU paperwork for that
[17:44]  * juliank generally only SRUs individual fixes, or big apt releases, but apt has huge test suite
[17:44] <juliank> s/generally/usually/
[17:46] <juliank> Do I need a separate exception from tech board to be able to sru that?
[17:46] <juliank> or I guess sru team self-approves stable release exception now
[17:48] <juliank> I don't know, the policy is far more strict than practice is :)
[17:48] <juliank> And when it comes to interpreting policies, I'm even more strict usually than intended
[17:48] <blackboxsw> sil2100: if there is an SRU-review slot for today. We have a verified cloud-utils SRU for Xenial at #1493188 #1630274
[17:52] <juliank> Looking at other bigger updates I stumbled upon https://bugs.launchpad.net/ubuntu/+source/vala/+bug/1879329
[17:52] <ubot5> Ubuntu bug 1879329 in vala (Ubuntu) "[SRU] Update to vala 0.48.6 in focal" [High,Fix released]
[17:52] <juliank> which says vala falls under the GNOME exception, when the gnome exception says "Vala is not considered part of GNOME for the purposes of micro release updates"
[17:53] <juliank> ah heh that bit is newer than the SRU :D
[18:11] <bdmurray> doko: The first crash has ProcMaps https://errors.ubuntu.com/oops/9ba4e3ca-093b-11eb-b591-fa163e6cac46
[18:13] <doko> bdmurray: yes, as expected, locally installed extensions
=== ijohnson is now known as ijohnson|lunch
[18:39] -queuebot:#ubuntu-release- New binary: qwertone [riscv64] (hirsute-proposed/universe) [0.3.0-2] (no packageset)
[19:04] -queuebot:#ubuntu-release- New binary: qwertone [arm64] (hirsute-proposed/universe) [0.3.0-2] (no packageset)
[19:07] -queuebot:#ubuntu-release- New binary: qwertone [armhf] (hirsute-proposed/universe) [0.3.0-2] (no packageset)
=== ijohnson|lunch is now known as ijohnson
[19:44] -queuebot:#ubuntu-release- Unapproved: opencryptoki (bionic-proposed/universe) [3.9.0+dfsg-0ubuntu1.2 => 3.9.0+dfsg-0ubuntu1.3] (no packageset)
[21:32] <Eickmeyer[m]> ubuntu-archive: bug 1904060 could use your attention.
[21:32] <ubot5> bug 1904060 in musescore (Ubuntu) "Please remove the musescore source package (renamed to musescore3) from hirsute and newer" [Medium,Triaged] https://launchpad.net/bugs/1904060
=== ebarretto_ is now known as ebarretto
[23:35] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (xenial-proposed/main) [4.4.0-195.227] (core, kernel)