Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #811058 > unrolled thread

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

Started byPirate Praveen <praveen@debian.org>
First post2017-03-04 08:30 +0100
Last post2017-03-08 10:00 +0100
Articles 3 — 3 participants

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  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

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

FromPirate Praveen <praveen@debian.org>
Date2017-03-04 08:30 +0100
SubjectBug#855931: ruby-eventmachine: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
Message-ID<thciB-5BI-1@gated-at.bofh.it>

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

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

[toc] | [next] | [standalone]


#811466

FromLucas Nussbaum <lucas@debian.org>
Date2017-03-06 13:30 +0100
Message-ID<thZW2-880-15@gated-at.bofh.it>
In reply to#811058
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...

Lucas

[toc] | [prev] | [next] | [standalone]


#811853

FromAntonio Terceiro <terceiro@debian.org>
Date2017-03-08 10:00 +0100
Message-ID<tiFBT-3WM-3@gated-at.bofh.it>
In reply to#811466

[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.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.bugs.dist


csiph-web