From: Mark Wielaard <mark@klomp.org>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Breakage on builder Fedora-s390x-m64, revision 97cbe998d0dd5c13a0317fbb24d745da367d8caa
Date: Sat, 02 Dec 2017 19:27:00 -0000 [thread overview]
Message-ID: <20171202192712.GB13493@stream.lan> (raw)
In-Reply-To: <87vahp6mgb.fsf@redhat.com>
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.
Note that the machine was recently upgraded from Fedora 25 to
Fedora 26. Might that explain the issue?
Cheers,
Mark
next prev parent reply other threads:[~2017-12-02 19:27 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 [this message]
2017-12-04 19:47 ` Sergio Durigan Junior
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=20171202192712.GB13493@stream.lan \
--to=mark@klomp.org \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.com \
/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