This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Breakage on builder Fedora-s390x-m64, revision 97cbe998d0dd5c13a0317fbb24d745da367d8caa
- From: Mark Wielaard <mark at klomp dot org>
- To: Sergio Durigan Junior <sergiodj at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Sat, 2 Dec 2017 20:27:12 +0100
- Subject: Re: Breakage on builder Fedora-s390x-m64, revision 97cbe998d0dd5c13a0317fbb24d745da367d8caa
- Authentication-results: sourceware.org; auth=none
- References: <E1eKxvJ-0006XB-Ve@kwanyin.sergiodj.net> <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