Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #76154 > unrolled thread

Re: Bug#1015272: liburing autopkgtest started to hang containers in Debian and Ubuntu since ~2022-07-11

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Bug#1015272: liburing autopkgtest started to hang containers in  Debian and Ubuntu since ~2022-07-11 Guillem Jover <guillem@debian.org> - 2022-08-21 19:50 +0200
    Processed: Re: Bug#1015272: liburing autopkgtest started to hang  containers in Debian and Ubuntu since ~2022-07-11 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-08-21 19:50 +0200
    Bug#1015272: liburing autopkgtest started to hang containers in Debian and Ubuntu since ~2022-07-11 Bastian Blank <waldi@debian.org> - 2022-08-21 21:40 +0200
      Processed: Re: Bug#1015272: liburing autopkgtest started to hang  containers in Debian and Ubuntu since ~2022-07-11 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-08-21 21:40 +0200
      Bug#1015272: liburing autopkgtest started to hang containers in Debian and Ubuntu since ~2022-07-11 Guillem Jover <guillem@debian.org> - 2023-03-02 13:00 +0100
        Bug#1015272: liburing autopkgtest started to hang containers in Debian and Ubuntu since ~2022-07-11 Salvatore Bonaccorso <carnil@debian.org> - 2023-03-04 17:30 +0100
          Bug#1015272: liburing autopkgtest started to hang containers in Debian and Ubuntu since ~2022-07-11 Paul Gevers <elbrus@debian.org> - 2023-03-04 17:30 +0100
            Bug#1015272: liburing autopkgtest started to hang containers in Debian and Ubuntu since ~2022-07-11 Salvatore Bonaccorso <carnil@debian.org> - 2023-03-05 10:20 +0100

#76154 — Re: Bug#1015272: liburing autopkgtest started to hang containers in Debian and Ubuntu since ~2022-07-11

Control: reassign -1 linux
Control: affects -1 liburing debci

Hi!

It seems like there was a regression with the latest stable update
that affects the autopkgtest for liburing. Reassigning.

On Mon, 2022-07-18 at 21:07:28 +0200, Paul Gevers wrote:
> Source: liburing
> Version: 2.1-2
> Severity: important
> X-Debbugs-Cc: brian@ubuntu.com

> 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.

Thanks,
Guillem

[toc] | [next] | [standalone]

#76155 — Processed: Re: Bug#1015272: liburing autopkgtest started to hang containers in Debian and Ubuntu since ~2022-07-11

Processing control commands:

> reassign -1 linux
Bug #1015272 [src:liburing] liburing autopkgtest started to hang containers in Debian and Ubuntu since ~2022-07-11
Bug reassigned from package 'src:liburing' to 'linux'.
No longer marked as found in versions liburing/2.1-2.
Ignoring request to alter fixed versions of bug #1015272 to the same values previously set
> affects -1 liburing debci
Bug #1015272 [linux] liburing autopkgtest started to hang containers in Debian and Ubuntu since ~2022-07-11
Added indication that 1015272 affects liburing and debci

-- 
1015272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015272
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#76156 — Bug#1015272: liburing autopkgtest started to hang containers in Debian and Ubuntu since ~2022-07-11

Control: tags -1 moreinfo
Control: severity -1 normal

On Sun, Aug 21, 2022 at 07:42:10PM +0200, Guillem Jover wrote:
> It seems like there was a regression with the latest stable update
> that affects the autopkgtest for liburing. Reassigning.

Please provide enough information to make isolating the problem
possible.

https://ci.debian.net/packages/libu/liburing/ is completely silent as
there are not results for any of the failed runs.

Bastian

-- 
There is an order of things in this universe.
		-- Apollo, "Who Mourns for Adonais?" stardate 3468.1

[toc] | [prev] | [next] | [standalone]

#76157 — Processed: Re: Bug#1015272: liburing autopkgtest started to hang containers in Debian and Ubuntu since ~2022-07-11

Processing control commands:

> tags -1 moreinfo
Bug #1015272 [linux] liburing autopkgtest started to hang containers in Debian and Ubuntu since ~2022-07-11
Added tag(s) moreinfo.
> severity -1 normal
Bug #1015272 [linux] liburing autopkgtest started to hang containers in Debian and Ubuntu since ~2022-07-11
Severity set to 'normal' from 'important'

-- 
1015272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015272
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#78386 — Bug#1015272: liburing autopkgtest started to hang containers in Debian and Ubuntu since ~2022-07-11

Hi!

On Thu, 2023-03-02 at 12:12:06 +0100, Paul Gevers wrote:
> Control: fixed -1 5.10.162-1 6.1.8-1

> On Sun, 21 Aug 2022 21:35:58 +0200 Bastian Blank <waldi@debian.org> wrote:
> > On Sun, Aug 21, 2022 at 07:42:10PM +0200, Guillem Jover wrote:
> > > It seems like there was a regression with the latest stable update
> > > that affects the autopkgtest for liburing. Reassigning.
> > 
> > Please provide enough information to make isolating the problem
> > possible.
> > 
> > https://ci.debian.net/packages/libu/liburing/ is completely silent as
> > there are not results for any of the failed runs.

> I decided to try again to see if I could collect more information. The test
> now passes on amd64, arm64, i386 and ppc64el, all running 5.10.162-1 and on
> riscv64 running unstable. However, on armhf, armel (amd64 kernel) and s390x
> (all running 5.10.158-2), it seems that the observation of brian is still
> true, some test in test-unit test segfaults, the test exits and hangs.
> @Guillem, do you see something more in the output below (armhf log) that may
> be of interest? And maybe spot something to run in isolation?

> Reading the changelog of 5.10.162-1 I see io_uring mentioned a couple of
> times. Therefor I assume this bug is fixed in that version. Is it worth
> pursuing the real issue here?

Thanks for looking into this! As this appears fixed in latest Linux
releases, then I'd honestly not bother further, and just try to get the
remaining hosts upgraded to the fixed versions. If this was to reappear
then it might make sense to look into it again.

Regards,
Guillem

[toc] | [prev] | [next] | [standalone]

#78396 — Bug#1015272: liburing autopkgtest started to hang containers in Debian and Ubuntu since ~2022-07-11

Hi,

On Thu, Mar 02, 2023 at 12:47:53PM +0100, Guillem Jover wrote:
> Hi!
> 
> On Thu, 2023-03-02 at 12:12:06 +0100, Paul Gevers wrote:
> > Control: fixed -1 5.10.162-1 6.1.8-1
> 
> > On Sun, 21 Aug 2022 21:35:58 +0200 Bastian Blank <waldi@debian.org> wrote:
> > > On Sun, Aug 21, 2022 at 07:42:10PM +0200, Guillem Jover wrote:
> > > > It seems like there was a regression with the latest stable update
> > > > that affects the autopkgtest for liburing. Reassigning.
> > > 
> > > Please provide enough information to make isolating the problem
> > > possible.
> > > 
> > > https://ci.debian.net/packages/libu/liburing/ is completely silent as
> > > there are not results for any of the failed runs.
> 
> > I decided to try again to see if I could collect more information. The test
> > now passes on amd64, arm64, i386 and ppc64el, all running 5.10.162-1 and on
> > riscv64 running unstable. However, on armhf, armel (amd64 kernel) and s390x
> > (all running 5.10.158-2), it seems that the observation of brian is still
> > true, some test in test-unit test segfaults, the test exits and hangs.
> > @Guillem, do you see something more in the output below (armhf log) that may
> > be of interest? And maybe spot something to run in isolation?
> 
> > Reading the changelog of 5.10.162-1 I see io_uring mentioned a couple of
> > times. Therefor I assume this bug is fixed in that version. Is it worth
> > pursuing the real issue here?
> 
> Thanks for looking into this! As this appears fixed in latest Linux
> releases, then I'd honestly not bother further, and just try to get the
> remaining hosts upgraded to the fixed versions. If this was to reappear
> then it might make sense to look into it again.

FWIW, it is correct, the 5.10.162 release upstream was basically the
one to bring the io_uring implementation inline with 5.15.y series
(with the io_uring codebase from 5.15.85).

So would agree, it make sense to update all remaining hosts and then
look into it again in case the problem arise again.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#78397 — Bug#1015272: liburing autopkgtest started to hang containers in Debian and Ubuntu since ~2022-07-11

[Multipart message — attachments visible in raw view] — view raw

Hi,

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).

Paul

[toc] | [prev] | [next] | [standalone]

#78407 — Bug#1015272: liburing autopkgtest started to hang containers in Debian and Ubuntu since ~2022-07-11

Hi Paul,

On Sat, Mar 04, 2023 at 05:22:32PM +0100, Paul Gevers wrote:
> Hi,
> 
> 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).

Ok understand! The fix for that is included in the next upload.

Regards,
Salvatore

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web