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. Can you please
share more details on how I can reproduce this? Also let me note once
again that 2.2.1 is much outdated and latest upstream is 2.4, although
I don't think we fixed anything related to death tests recently.


On Thu, Jul 14, 2016 at 3:06 AM, Lucas Nussbaum <lu...@debian.org> wrote:
> Source: google-perftools
> Version: 2.2.1-0.3
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> 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.
>

Reply via email to