On Tue, Jul 19, 2016 at 1:29 PM, Lucas Nussbaum <lu...@debian.org> wrote: > Hi Aliaksey, > > On 16/07/16 at 12:28 +0200, Santiago Vila wrote: >> On Fri, 15 Jul 2016, Aliaksey Kandratsenka wrote: >> >> > Thanks for reporting the issue. I just tried to reproduce the problem >> > on my sid laptop in cleanly deboostrap-ed sid chroot and was unable to >> > hit this issue. This maybe indicates that kernel matters or maybe >> > there is something else in the host that is relevant. >> >> For the record: While checking for "dpkg-buildpackage -A", I was also >> able to reproduce this problem in the past: >> >> Running death test 0...make[2]: *** wait: No child processes. Stop. >> make[2]: *** Waiting for unfinished jobs.... >> make[2]: *** wait: No child processes. Stop. >> make[1]: *** wait: No child processes. Stop. >> make[1]: *** Waiting for unfinished jobs.... >> make[1]: *** wait: No child processes. Stop. >> make: *** wait: No child processes. Stop. >> make: *** Waiting for unfinished jobs.... >> make: *** wait: No child processes. Stop. >> Build killed with signal TERM after 150 minutes of inactivity >> >> I'm also using sbuild, triggered by a cron job. > > Do you still need help to reproduce the issue? Indeed it was the > equivalent of dpkg-buildpackage -A that triggered it.
I got sbuild set up on my box (via instructions at https://wiki.debian.org/sbuild) and even under sbuild I am unable to reproduce the problem. So maybe this is something with kernel? Should I try to get, say recent stable installed under KVM? I am running on fairly up-to-date unstable distro.
