Discussion:
Bug#963319: ruby-em-synchrony: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
Add Reply
Lucas Nussbaum
2020-06-21 20:10:11 UTC
Reply
Permalink
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.
/<<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.
Ivo De Decker
2021-02-12 21:50:02 UTC
Reply
Permalink
Hi,
Note that this seems very similar to #978251. As described in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978251#16
the issue is probably caused by running the tests under fakeroot.
It seems ruby-em-synchrony is only used as a build-dependency for
ruby-faraday. That build-dependency can be removed by disabling the
em-synchrony tests (and updating the coverage settings). Maybe that should be
done, to allow em-synchrony to be removed from bullseye?
Cheers,

Ivo
Debian Bug Tracking System
2021-02-22 20:40:02 UTC
Reply
Permalink
Your message dated Mon, 22 Feb 2021 20:34:13 +0000
with message-id <E1lEHuH-0008il-***@fasolo.debian.org>
and subject line Bug#963319: fixed in ruby-em-synchrony 1.0.5-3.1
has caused the Debian Bug report #963319,
regarding ruby-em-synchrony: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
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 ***@bugs.debian.org
immediately.)
--
963319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963319
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Loading...