[DRE-maint] Bug#852896: ruby-parallel: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

[Lucas Nussbaum]

Source: ruby-parallel
Version: 1.9.0-1
Severity: serious
Tags: stretch sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20170128 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):
>     notifies when an item of work is dispatched to a worker process
>     notifies when an item of work is dispatched with 0 processes
>     notifies when an item of work is completed by a worker process
>     notifies when an item of work is completed with 0 processes
>     notifies when an item of work is dispatched to a threaded worker
>     notifies when an item of work is dispatched with 0 threads
>     notifies when an item of work is completed by a threaded worker
>     notifies when an item of work is completed with 0 threads
>     spits out a useful error when a worker dies before read
>     spits out a useful error when a worker dies before write
>     raises DeadWorker when using exit so people learn to not kill workers and do not crash main process
>     raises EOF (not DeadWorker) when a worker raises EOF in process
>     can be killed instantly (PENDING: Temporarily skipped with xit)
>     synchronizes :start and :finish
>     is equivalent to serial map
> E: Build killed with signal TERM after 150 minutes of inactivity

The full build log is available from:
   http://aws-logs.debian.net/2017/01/28/ruby-parallel_1.9.0-1_unstable.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.