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

[Lucas Nussbaum]

Source: ruby-eventmachine
Version: 1.0.7-4
Severity: serious
Tags: stretch sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20170221 qa-ftbfs
Justification: FTBFS in stretch on amd64

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
>   test_errback:						.: (0.000197)
>   test_fail:						.: (0.000301)
>   test_late_defined_callbacks:				.: (0.000289)
>   test_latent_completion:				.: (0.000375)
>   test_recursive_callbacks:				.: (0.000213)
>   test_skip_completed_callbacks:			.: (0.000321)
>   test_state:						.: (0.000109)
>   test_stateback:					.: (0.000314)
>   test_succeed:						.: (0.000202)
>   test_timeout:						.: (0.000234)
>   test_timeout_gets_cancelled:				.: (0.000186)
> TestConnectionCount: 
>   test_idle_connection_count:				.: (0.000289)
>   test_num_close_scheduled:				.: (15.023029)
>   test_with_some_connections:				
> E: Build killed with signal TERM after 150 minutes of inactivity

The full build log is available from:
   http://aws-logs.debian.net/2017/02/21/ruby-eventmachine_1.0.7-4_testing.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.