Bug#966368: lintian gets stuck when run by sbuild within rebuildd
Hi Raphael, On Mon, Jul 27, 2020 at 11:45 AM Raphael Hertzog wrote: > > I saw #964770 but it > didn't seem exactly the same issue. That bug is also unconfirmed—iincluding by the IO::Async developers. Kind regards Felix Lechner
Bug#966368: lintian gets stuck when run by sbuild within rebuildd
Hi, On Mon, 27 Jul 2020, Chris Lamb wrote: > > In Kali, our build daemons run "rebuildd" with a build script that calls > > sbuild --run-lintian. Since lintian 2.85 (I believe 2.84.0 is not affected), > > the build process get stuck at the point when lintian is run. I see two > > lintian > > processes (a parent and its child) and both are stuck in epoll_pwait() > > according to strace. > > I think this is the same as #966122 and/or #966072. Looks like the same as #966122 since it seems to break in the same check (deb-format which is the only place where I expect "ar t" to be called). I didn't find this one while looking for duplicate... I saw #964770 but it didn't seem exactly the same issue. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/ ⠈⠳⣄ Debian Long Term Support: https://deb.li/LTS
Bug#966368: lintian gets stuck when run by sbuild within rebuildd
Hi Raphaël, > In Kali, our build daemons run "rebuildd" with a build script that calls > sbuild --run-lintian. Since lintian 2.85 (I believe 2.84.0 is not affected), > the build process get stuck at the point when lintian is run. I see two > lintian > processes (a parent and its child) and both are stuck in epoll_pwait() > according to strace. I think this is the same as #966122 and/or #966072. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org chris-lamb.co.uk `-
Bug#966368: lintian gets stuck when run by sbuild within rebuildd
Package: lintian Version: 2.85.0 Severity: important User: de...@kali.org Usertags: origin-kali In Kali, our build daemons run "rebuildd" with a build script that calls sbuild --run-lintian. Since lintian 2.85 (I believe 2.84.0 is not affected), the build process get stuck at the point when lintian is run. I see two lintian processes (a parent and its child) and both are stuck in epoll_pwait() according to strace. In normal (non-verbose mode) there's no output of lintian before it gets stuck: Example in this build log: http://buildd-amd64.kali.org/build-logs/golang-github-projectdiscovery-gologger_1.0.0-0kali1-kali-dev-amd64-20200724-124452.3196.log When I add the --debug option you see this: http://buildd-amd64.kali.org/build-logs/kali-meta_2020.3.10-kali-dev-amd64-20200727-132744.3202.log The last lines are like this: N: Check script control-files for binary:kali-tools-forensics/2020.3.10/amd64 done (0.015s) N: Running check: cron on binary:kali-tools-forensics/2020.3.10/amd64 ... N: Check script cron for binary:kali-tools-forensics/2020.3.10/amd64 done (0.009s) N: Running check: cruft on binary:kali-tools-forensics/2020.3.10/amd64 ... N: Check script cruft for binary:kali-tools-forensics/2020.3.10/amd64 done (0.015s) N: Running check: deb-format on binary:kali-tools-forensics/2020.3.10/amd64 ... The process tree is like this: kalibui+ 32428 0.0 0.0 19640 3252 ?Ss 13:28 0:00 \_ /bin/sh /srv/build.kali.org/bin/build kali-meta 2020.3.10 amd64 kali-dev kalibui+ 32431 0.2 0.1 89316 33428 ?S13:28 0:00 \_ /usr/bin/perl /usr/bin/sbuild --no-source --run-lintian --lintian-opts=-I --debug --nolog --apt-update --apt-upgrade --no-apt-distupgrade --arch=amd64 -d kali-dev --arch-all /srv/build.kali.org/build/work/kali-meta_2020.3.10.dsc kalibui+ 32436 0.1 0.0 88388 30100 ?S13:28 0:00 \_ /usr/bin/perl /usr/bin/sbuild --no-source --run-lintian --lintian-opts=-I --debug --nolog --apt-update --apt-upgrade --no-apt-distupgrade --arch=amd64 -d kali-dev --arch-all /srv/build.kali.org/build/work/kali-meta_2020.3.10.dsc root 4007 0.0 0.0 66528 6480 ?S13:28 0:00 \_ schroot -d /build/kali-meta-E2qWUi -c kali-dev-amd64-sbuild-a3951a2c-b417-47f2-915c-bb7f546b39ff --run-session -q -u kalibuild -p -- lintian -I --debug kali-meta_2020.3.10_amd64.changes kali-meta_2020.3.10.dsc kalibui+ 4008 3.3 0.2 123596 76080 ?S13:28 0:03 \_ lintian -I --debug kali-meta_2020.3.10_amd64.changes kali-meta_2020.3.10.dsc kalibui+ 5628 0.0 0.2 123732 69692 ?S13:28 0:00 \_ lintian -I --debug kali-meta_2020.3.10_amd64.changes kali-meta_2020.3.10.dsc The open files are like this: # ls -al /proc/4008/fd /proc/5628/fd /proc/4008/fd: total 0 dr-x-- 2 kalibuild kalibuild 0 Jul 27 13:38 . dr-xr-xr-x 8 kalibuild kalibuild 0 Jul 27 13:28 .. lrwx-- 1 kalibuild kalibuild 64 Jul 27 13:38 0 -> /dev/null l-wx-- 1 kalibuild kalibuild 64 Jul 27 13:38 1 -> pipe:[689890348] lr-x-- 1 kalibuild kalibuild 64 Jul 27 13:38 11 -> pipe:[689938177] l-wx-- 1 kalibuild kalibuild 64 Jul 27 13:38 13 -> /srv/build.kali.org/build/logs/i3-gaps_4.18.1-0kali2-kali-dev-i386-20200724-200857.3199.log l-wx-- 1 kalibuild kalibuild 64 Jul 27 13:38 2 -> pipe:[689890348] l-wx-- 1 kalibuild kalibuild 64 Jul 27 13:38 3 -> /srv/build.kali.org/db/rebuildd.log l-wx-- 1 kalibuild kalibuild 64 Jul 27 13:38 4 -> /srv/build.kali.org/db/rebuildd.log lrwx-- 1 kalibuild kalibuild 64 Jul 27 13:38 5 -> socket:[8970131] lrwx-- 1 kalibuild kalibuild 64 Jul 27 13:38 6 -> anon_inode:[eventpoll] l-wx-- 1 kalibuild kalibuild 64 Jul 27 13:38 7 -> /run/schroot/mount/kali-dev-amd64-sbuild-a3951a2c-b417-47f2-915c-bb7f546b39ff/dev/null lr-x-- 1 kalibuild kalibuild 64 Jul 27 13:38 8 -> pipe:[689938176] lrwx-- 1 kalibuild kalibuild 64 Jul 27 13:38 9 -> socket:[528586941] /proc/5628/fd: total 0 dr-x-- 2 kalibuild kalibuild 0 Jul 27 13:28 . dr-xr-xr-x 8 kalibuild kalibuild 0 Jul 27 13:28 .. lrwx-- 1 kalibuild kalibuild 64 Jul 27 13:28 0 -> /dev/null l-wx-- 1 kalibuild kalibuild 64 Jul 27 13:28 1 -> pipe:[689890348] l-wx-- 1 kalibuild kalibuild 64 Jul 27 13:28 10 -> pipe:[689938176] l-wx-- 1 kalibuild kalibuild 64 Jul 27 13:28 12 -> pipe:[689938177] l-wx-- 1 kalibuild kalibuild 64 Jul 27 13:28 2 -> pipe:[689890348] lrwx-- 1 kalibuild kalibuild 64 Jul 27 13:28 3 -> anon_inode:[eventpoll] lr-x-- 1 kalibuild kalibuild 64 Jul 27 13:28 6 -> pipe:[689942617] l-wx-- 1 kalibuild kalibuild 64 Jul 27 13:28 7 -> pipe:[689942617] lr-x-- 1 kalibuild kalibuild 64 Jul 27 13:28 8 -> pipe:[689942618] And the strace output is like this: # strace -p 4008 -p 5628 strace: Process 4008 attached strace: Process 5628 attached [pid 5628] getpid( [pid 4008] getpid( [pid 5628] <... getpid resumed> ) = 5628 [pid 4008] <... getpid resumed> ) = 4008 [pid
