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

[Lucas Nussbaum]

Source: ruby-em-synchrony
Version: 1.0.5-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> /<<PKGBUILDDIR>>/spec/connection_pool_spec.rb:4: warning: already initialized constant QUERY
> /<<PKGBUILDDIR>>/spec/activerecord_spec.rb:11: warning: previous definition of QUERY was here
> /<<PKGBUILDDIR>>/spec/http_spec.rb:5: warning: already initialized constant DELAY
> /<<PKGBUILDDIR>>/spec/connection_pool_spec.rb:3: warning: previous definition of DELAY was here
> /<<PKGBUILDDIR>>/spec/inlinesync_spec.rb:6: warning: already initialized constant URL
> /<<PKGBUILDDIR>>/spec/http_spec.rb:3: warning: previous definition of URL was here
> /<<PKGBUILDDIR>>/spec/inlinesync_spec.rb:7: warning: already initialized constant DELAY
> /<<PKGBUILDDIR>>/spec/http_spec.rb:5: warning: previous definition of DELAY was here
> /<<PKGBUILDDIR>>/spec/keyboard_spec.rb:4: warning: already initialized constant DELAY
> /<<PKGBUILDDIR>>/spec/inlinesync_spec.rb:7: warning: previous definition of DELAY was here
> /<<PKGBUILDDIR>>/spec/mysql2_spec.rb:6: warning: already initialized constant DELAY
> /<<PKGBUILDDIR>>/spec/keyboard_spec.rb:4: warning: previous definition of DELAY was here
> /<<PKGBUILDDIR>>/spec/mysql2_spec.rb:7: warning: already initialized constant QUERY
> /<<PKGBUILDDIR>>/spec/connection_pool_spec.rb:4: warning: previous definition of QUERY was here
> ******************....**********..FFF..F....
> E: Build killed with signal TERM after 150 minutes of inactivity

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/ruby-em-synchrony_1.0.5-3_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.