Your message dated Sat, 23 Nov 2024 19:40:16 +0000
with message-id
<CAJ3BuoTX+XksPKF_OdNF6aDf8KcipnOgfcgYXNTQPacxXs=b...@mail.gmail.com>
and subject line Re: Bug#1087692: sbuild: provide a way to apply a timeout to
piuparts and autopkgtests
has caused the Debian Bug report #1087692,
regarding sbuild: provide a way to apply a timeout to piuparts and autopkgtests
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 [email protected]
immediately.)
--
1087692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1087692
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sbuild
Version: 0.85.0
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
$stalled_pkg_timeout terminates the build after inactivity, but it would be
nice if there was
an equivalent for the use of piuparts (--run-piuparts) or (--run-autopkgtests)
Especially with piuparts it is easy to start a build, and it will be hang
waiting for a sudo password
The documentation in sbuild.conf says this is based on writes to the build log,
but this does not include
writes from piuparts or autopkgtests
I tried
$piuparts_root_args=['timeout', '20m', 'sudo', '--'];
but it did not kill the sudo call
-- System Information:
Debian Release: 12.8
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.1.0-27-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages sbuild depends on:
ii adduser 3.134
ii libsbuild-perl 0.85.0
ii perl 5.36.0-7+deb12u1
Versions of packages sbuild recommends:
ii autopkgtest 5.28
ii debootstrap 1.0.128+nmu2+deb12u1
ii schroot 1.6.13-3+b2
ii uidmap 1:4.13+dfsg1-1+b1
Versions of packages sbuild suggests:
pn deborphan <none>
ii e2fsprogs 1.47.0-2
ii kmod 30+20221128-1
ii wget 1.21.3-1+b2
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, 18 Nov 2024 19:02:13 +0000 Richard Lewis
<[email protected]> wrote:
> This works great thanks. ill add this to the debian wiki page.
>
On second thoughts, it can just be closed, given that the page is now
focused on unshare
> On Sun, 17 Nov 2024, 17:20 Johannes Schauer Marin Rodrigues, <
> [email protected]> wrote:
>
> > Hi Richard,
> >
> > Quoting Richard Lewis (2024-11-17 11:43:11)
> > > $stalled_pkg_timeout terminates the build after inactivity, but it would
> > be
> > > nice if there was an equivalent for the use of piuparts (--run-piuparts)
> > or
> > > (--run-autopkgtests)
> > >
> > > Especially with piuparts it is easy to start a build, and it will be hang
> > > waiting for a sudo password
> > >
> > > The documentation in sbuild.conf says this is based on writes to the
> > build
> > > log, but this does not include writes from piuparts or autopkgtests
> > >
> > > I tried
> > > $piuparts_root_args=['timeout', '20m', 'sudo', '--'];
> > > but it did not kill the sudo call
> >
> > from timeout(1):
> >
> > --foreground
> > when not running timeout directly from a shell prompt,
> > allow COMMAND to read from the TTY and get TTY signals;,
> >
> > Did you try running timeout with the --foreground option?
> >
> > Thanks!
> >
> > cheers, josch
--- End Message ---
