Your message dated Thu, 21 Jul 2016 11:16:28 +0200
with message-id <[email protected]>
and subject line Re: Bug#831240: google-perftools: FTBFS: Running death test 0
hangs
has caused the Debian Bug report #831240,
regarding google-perftools: FTBFS: Running death test 0 hangs
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.)
--
831240: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831240
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: google-perftools
Version: 2.2.1-0.3
Severity: serious
Tags: stretch sid
User: [email protected]
Usertags: qa-ftbfs-20160714 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> PASS: malloc_extension_debug_test
> PASS
> PASS: memalign_debug_unittest
> PASS
> PASS: realloc_debug_unittest
> 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.
> E: Caught signal ‘Terminated’: terminating immediately
> Running death test 0Build killed with signal TERM after 150 minutes of
> inactivity
The full build log is available from:
http://people.debian.org/~lucas/logs/2016/07/14/google-perftools_2.2.1-0.3_unstable_gcc5.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
On 20/07/16 at 15:43 -0700, Aliaksey Kandratsenka wrote:
> On Tue, Jul 19, 2016 at 1:29 PM, Lucas Nussbaum <[email protected]> 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.
Hi,
I recently discovered that the official Debian images on AWS EC2 include
some sysctl tunings (see
https://github.com/andsens/bootstrap-vz/pull/256/commits/06da309895f69573996a4c1ff027f999155b876b#diff-43081b58ccf1565f80325d26c36d7c57R18
)
It seems that one of those caused that failure, because, now that I have
them disabled, it does not fail anymore.
I'm closing this bug, sorry for the noise.
Lucas
--- End Message ---
