Groups > linux.debian.bugs.dist > #811853

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

From	Antonio Terceiro <terceiro@debian.org>
Newsgroups	linux.debian.bugs.dist
Subject	Bug#855931: ruby-eventmachine: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
Date	2017-03-08 10:00 +0100
Message-ID	<tiFBT-3WM-3@gated-at.bofh.it> (permalink)
References	<te1MJ-1Qh-1@gated-at.bofh.it> <te1MJ-1Qh-1@gated-at.bofh.it> <thciB-5BI-1@gated-at.bofh.it> <thZW2-880-15@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

On Mon, Mar 06, 2017 at 01:12:12PM +0100, Lucas Nussbaum wrote:
> On 04/03/17 at 12:49 +0530, Pirate Praveen wrote:
> > On Thu, 23 Feb 2017 14:28:20 +0100 Lucas Nussbaum <lucas@debian.org> wrote:
> > > During a rebuild of all packages in stretch (in a stretch chroot, not a
> > > sid chroot), your package failed to build on amd64.
> > 
> > I could not reproduce it on  a freshly created stretch chroot with sbuild.
> > 
> > sbuild -d stretch ruby-eventmachine_1.0.7-4.dsc
> 
> Hi,
> 
> Well, I just gave it another try, and I could reproduce it...

ruby-eventmachine is one the packages whose tests will go crazy on EC2,
probably due to some weirdness in how exactly EC2 VM's are configured.
Most likely something kernel-related.

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Bug#855931: ruby-eventmachine: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity Pirate Praveen <praveen@debian.org> - 2017-03-04 08:30 +0100
  Bug#855931: ruby-eventmachine: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity Lucas Nussbaum <lucas@debian.org> - 2017-03-06 13:30 +0100
    Bug#855931: ruby-eventmachine: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity Antonio Terceiro <terceiro@debian.org> - 2017-03-08 10:00 +0100

csiph-web