Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: gdb-patches@sourceware.org
Subject: Re: Breakage on builder Fedora-s390x-m64, revision 97cbe998d0dd5c13a0317fbb24d745da367d8caa
Date: Mon, 04 Dec 2017 19:47:00 -0000	[thread overview]
Message-ID: <87a7yytgvp.fsf@redhat.com> (raw)
In-Reply-To: <20171202192712.GB13493@stream.lan> (Mark Wielaard's message of	"Sat, 2 Dec 2017 20:27:12 +0100")

On Saturday, December 02 2017, Mark Wielaard wrote:

> On Sat, Dec 02, 2017 at 12:58:44PM -0500, Sergio Durigan Junior wrote:
>> On Friday, December 01 2017, gdb-buildbot@sergiodj.net wrote:
>> 
>> > Unfortunately it seems that there is a breakage on GDB.
>> >
>> > Commit title: 'Add support for the readnever concept'
>> > Revision: 97cbe998d0dd5c13a0317fbb24d745da367d8caa
>> 
>> Hm, this build failed because of a timeout...  Mark, I know this is hard
>> to investigate, but could you take a look at this?  Not sure if the
>> machine is overloaded or not...
>
> Not at the moment:
>  19:16:14 up 4 days, 10:21,  2 users,  load average: 0.01, 0.02, 0.00
> But at times there are several projects doing builds on it besides gdb
> (valgrind has nightly builds, elfutils and libabigail have a buildbot
> that does builds like gdb does on each commit and there are others).
>
> Also I don't immediately see anything in the logs you attached to
> understand which command precisely timed out.

Thanks for taking a look, Mark.

> Note that the machine was recently upgraded from Fedora 25 to
> Fedora 26. Might that explain the issue?

I'd say that's unlikely.  I'd go with the "several projects doing builds
at once" explanation.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


      reply	other threads:[~2017-12-04 19:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-02  2:53 Oh dear. I regret to inform you that commit 97cbe998d0dd5c13a0317fbb24d745da367d8caa might be unfortunate gdb-buildbot
2017-12-02  2:53 ` Breakage on builder Fedora-s390x-m64, revision 97cbe998d0dd5c13a0317fbb24d745da367d8caa gdb-buildbot
2017-12-02 17:58   ` Sergio Durigan Junior
2017-12-02 19:27     ` Mark Wielaard
2017-12-04 19:47       ` Sergio Durigan Junior [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a7yytgvp.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=mark@klomp.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox