[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1015272: marked as done (liburing autopkgtest started to hang containers in Debian and Ubuntu since ~2022-07-11)

Your message dated Tue, 14 Mar 2023 22:09:46 +0100
with message-id <8c7fd440-a96b-138e-b1f1-b91e3454a6f2@debian.org>
and subject line Re: Bug#1015272: liburing autopkgtest started to hang containers in Debian and Ubuntu since ~2022-07-11
has caused the Debian Bug report #1015272,
regarding liburing autopkgtest started to hang containers in Debian and Ubuntu since ~2022-07-11
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1015272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015272
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: liburing
Version: 2.1-2
Severity: important
X-Debbugs-Cc: brian@ubuntu.com

Dear Guillem,

Some days ago (approximately 7) the autopkgtest of liburing started to
behave badly on the Debian and Ubuntu infrastructure. It's not totally
clear to me what happens, but I have lxc containers left behind after
the test that I can't clean up.

A similar thing seems to happen on the Ubuntu side because they have
blocked the test from running recently and I'll do the same on our
side.

https://git.launchpad.net/~ubuntu-release/autopkgtest-cloud/+git/autopkgtest-package-configs/commit/?id=fedf747ea808837217d373773d105f242819702d

Because your package didn't change in that time, I suspect one of your
dependencies caused liburing to behave differently. It would be great
if we figured out what that is.

Paul

--- End Message ---
--- Begin Message --- 
Hi,

On 04-03-2023 17:22, Paul Gevers wrote:

On 04-03-2023 17:19, Salvatore Bonaccorso wrote:

So would agree, it make sense to update all remaining hosts and then
look into it again in case the problem arise again.
All but s390x are up-to-date and liburing testing works. I can't upgrade s390x because of bug #1031753 (which is worse for ci.d.n than this bug as far as I see).
I upgraded our s390x host to bookworm and it's able to run the liburing test without leaving the lxc container around. 

Paul

For the record:
root@ci-worker-s390x-01:~# uname -a
Linux ci-worker-s390x-01 6.1.0-6-s390x #1 SMP Debian 6.1.15-1 (2023-03-05) s390x GNU/Linux

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
Reply to: