=== luc14n0373 is now known as luc14n0_
=== luc14n0_42 is now known as luc14n0
[07:52] <tjaalton> mvo: hi, your snapd sru's reuse the old lp bug?
[07:57] <mvo> tjaalton: I can create a new one, sorry for that. our sru policy is a bit special so it might not be too bad but happy to create a new one if you folks prefer that
[07:59] <tjaalton> I see 2.57.1 and .4 used the same bug
[08:01] <tjaalton> I guess it's fine as is
[08:10] <mvo> tjaalton: yeah, thank you!
[08:12] <tjaalton> mvo: xenial has had several uploads stuck in the queue, why's that?
[08:13] <mvo> tjaalton: please remove them all, my appologies
[08:13] <mvo> tjaalton: I keep forgetting that it's in ESM, for us it's still supported because core is supported and I'm sometimes on auto pilot when uploading
[08:13] <tjaalton> okay, good.. I think it's supposed to be EOL for regular sru's anyway :)
[08:14] <mvo> tjaalton: excactly
[13:44] <nteodosio> Is there up to date information on how to retrieve core dumps from snaps?
[13:44] <nteodosio> https://forum.snapcraft.io/t/core-dumps-in-snapd/920/2 doesn't work.
[14:04] <bluca> we started seeing seemingly random asserts in the systemd test suite, on jammy + ppc64el
[14:04] <bluca> we cannot reproduce on other OSes ppc64el, nor on jammy with other architectures
[14:05] <bluca> they look like random corruptions
[14:05] <bluca> are there known issues in jammy+ppc64el toolchain or something like that?
[14:05] <bluca> full info: https://github.com/systemd/systemd/issues/25091
[14:05] -ubottu:#ubuntu-devel- Issue 25091 in systemd/systemd "Spurious assertions in the ppc64el Ubuntu Jammy job" [Open]
[14:13] <enr0n> bluca: I started hitting that in autopkgtest as well, but haven't figured out the root cause. The one observation I made is that it only seems to affect tests that run in QEMU.
[14:15] <enr0n> Bug 1992178
[14:15] -ubottu:#ubuntu-devel- Bug 1992178 in systemd (Ubuntu) "autopkgtest: upstream tests that run in qemu hang on ppc64el" [Medium, Fix Released] https://launchpad.net/bugs/1992178
=== philcox_ is now known as philcox
[14:18] <bluca> yes only in qemu, same observation
=== falcojr9 is now known as falcojr1
=== falcojr1 is now known as falcojr
[18:04] <bdmurray> enr0n: You might want to have a look at bug 1921664
[18:04] -ubottu:#ubuntu-devel- Bug 1921664 in qemu (Fedora) "Coroutines are racy for risc64 emu on arm64 - crash on Assertion" [Medium, In Progress] https://launchpad.net/bugs/1921664
[18:06] <enr0n> bdmurray: looking
[18:14] <enr0n> bdmurray: The issue occurred even after that QEMU upload. Or are you suggesting the issue may be related, but different?
[18:15] <bdmurray> enr0n: I didn't think it had been fixed in Jammy
[18:17] <bdmurray> Although I guess you were talking about Kinetic in bug 1992178
[18:17] <enr0n> bdmurray: Oh I see. It's present in Kinetic, which is where I have been trying to investigate.
[18:17] -ubottu:#ubuntu-devel- Bug 1992178 in systemd (Ubuntu) "autopkgtest: upstream tests that run in qemu hang on ppc64el" [Medium, Fix Released] https://launchpad.net/bugs/1992178
[18:17] <bdmurray> enr0n: I understand now.
[18:18] <enr0n> Thanks for the tip in any case
=== pizza is now known as pineapplepizza
=== pineapplepizza is now known as pizza
=== arraybolt3 is now known as abcdefghijklmnop
=== abcdefghijklmnop is now known as arraybolt3