From: gdb-buildbot@sergiodj.net
To: Nick Clifton <nickc@redhat.com>, gdb-patches@sourceware.org
Subject: Breakage on builder Fedora-x86_64-cc-with-index, revision e0115a844607b280449986e661f551dff49a9031
Date: Wed, 01 Nov 2017 12:56:00 -0000 [thread overview]
Message-ID: <E1e9sZB-0007IC-7Z@kwanyin.sergiodj.net> (raw)
In-Reply-To: <e0115a844607b280449986e661f551dff49a9031-master-breakage@gdb-build>
Unfortunately it seems that there is a breakage on GDB.
Commit title: 'Update check for invalid values in pe_bfd_read_buildid function.'
Revision: e0115a844607b280449986e661f551dff49a9031
You can find more details below:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Buildslave:
fedora-x86-64-2
Full Build URL:
<http://gdb-build.sergiodj.net/builders/Fedora-x86_64-cc-with-index/builds/7760>
Commit(s) tested:
e0115a844607b280449986e661f551dff49a9031
Author(s) (in the same order as the commits):
Nick Clifton <nickc@redhat.com>
Subject:
Update check for invalid values in pe_bfd_read_buildid function.
Testsuite log (gdb.sum and gdb.log) URL(s):
<http://gdb-build.sergiodj.net/results/Fedora-x86_64-cc-with-index/e0/e0115a844607b280449986e661f551dff49a9031/>
*** Internal error on buildslave (no space left on device). ***
*** Please report this to the buildslave owner (see <http://gdb-build.sergiodj.net//buildslaves/fedora-x86-64-2>) ***
*** Failed to compiled GDB. ***
============================
checking for suffix of executables... Setting warning flags = -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Wstack-usage=262144 -Werror
checking for strings.h... Setting warning flags = -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Wstack-usage=262144 -Werror
============================
prev parent reply other threads:[~2017-11-01 12:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 12:56 Oh dear. I regret to inform you that commit e0115a844607b280449986e661f551dff49a9031 might be unfortunate gdb-buildbot
2017-11-01 12:56 ` gdb-buildbot [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=E1e9sZB-0007IC-7Z@kwanyin.sergiodj.net \
--to=gdb-buildbot@sergiodj.net \
--cc=gdb-patches@sourceware.org \
--cc=nickc@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