From: Simon Marchi <simon.marchi@ericsson.com>
To: <gdb-patches@sourceware.org>,
Sergio Durigan Junior <sergiodj@redhat.com>
Subject: Re: Breakage on builder Fedora-x86_64-cc-with-index, revision 81b42bcab16f4462eb4c91db2cf09cd76e17402e
Date: Wed, 01 Nov 2017 15:44:00 -0000 [thread overview]
Message-ID: <664f122d-7ec2-7f55-ec7f-da2e61c20dc5@ericsson.com> (raw)
In-Reply-To: <E1e9v4x-000061-Up@kwanyin.sergiodj.net>
Hi Sergio,
These failures are caused by an x86-64 buildslave being out of disk space.
I guess it's one of the GCC compile farm machines, but I don't know which
one. Could you look into it, or tell which machine fedora-x86-64-1 maps to?
Thanks,
Simon
On 2017-11-01 11:37 AM, gdb-buildbot@sergiodj.net wrote:
> Unfortunately it seems that there is a breakage on GDB.
>
> Commit title: 'FT32B is a new FT32 family member. It has a code compression scheme, which requires the use of linker relaxations. The change is quite large, so submission is in several parts.'
> Revision: 81éb42bcab16f4462eb4c91db2cf09cd76e17402e
>
> You can find more details below:
>
> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
> Buildslave:
> fedora-x86-64-1
>
> Full Build URL:
> <http://gdb-build.sergiodj.net/builders/Fedora-x86_64-cc-with-index/builds/7762>
>
> Commit(s) tested:
> 81b42bcab16f4462eb4c91db2cf09cd76e17402e
>
> Author(s) (in the same order as the commits):
> James Bowman <james.bowman@ftdichip.com>
>
> Subject:
> FT32B is a new FT32 family member. It has a code compression scheme, which requires the use of linker relaxations. The change is quite large, so submission is in several parts.
>
> Testsuite log (gdb.sum and gdb.log) URL(s):
> <http://gdb-build.sergiodj.net/results/Fedora-x86_64-cc-with-index/81/81b42bcab16f4462eb4c91db2cf09cd76e17402e/>
>
> *** 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-1>) ***
>
> *** Failed to compiled GDB. ***
> ============================
> ../../binutils-gdb/readline/complete.c:701:12: warning: implicit declaration of function wcwidth; did you mean fnwidth? [-Wimplicit-function-declaration]
> ../../binutils-gdb/readline/display.c:768:15: warning: implicit declaration of function wcwidth [-Wimplicit-function-declaration]
> ../../binutils-gdb/readline/mbutil.c:122:12: warning: implicit declaration of function wcwidth [-Wimplicit-function-declaration]
> Setting warning flags = -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Wstack-usage=262144 -Werror
> Setting warning flags = -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow -Wstack-usage=262144 -Werror
> ============================
>
next prev parent reply other threads:[~2017-11-01 15:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 15:37 Oh dear. I regret to inform you that commit 81b42bcab16f4462eb4c91db2cf09cd76e17402e might be unfortunate gdb-buildbot
2017-11-01 15:37 ` Breakage on builder Fedora-x86_64-cc-with-index, revision 81b42bcab16f4462eb4c91db2cf09cd76e17402e gdb-buildbot
2017-11-01 15:44 ` Simon Marchi [this message]
2017-11-01 17:08 ` Sergio Durigan Junior
2017-11-01 17:30 ` Simon Marchi
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=664f122d-7ec2-7f55-ec7f-da2e61c20dc5@ericsson.com \
--to=simon.marchi@ericsson.com \
--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