From: Simon Marchi <simark@simark.ca>
To: gdb-buildbot@sergiodj.net, gdb-patches@sourceware.org,
Alan Modra <amodra@gmail.com>
Subject: Re: Breakage on builder Fedora-x86_64-w64-mingw32, revision 9737e8af48e257f24e860fbf36af8c314e73076a
Date: Thu, 17 Oct 2019 19:41:00 -0000 [thread overview]
Message-ID: <5c62c651-23e6-c986-97ef-f85184944866@simark.ca> (raw)
In-Reply-To: <E1iLBRu-0003LF-Jf@gdb-buildbot.osci.io>
On 2019-10-17 3:28 p.m., gdb-buildbot@sergiodj.net wrote:
> Unfortunately it seems that there is a breakage on GDB.
>
> Commit title: 'PowerPC section flag tidy'
> Revision: 9737e8af48e257f24e860fbf36af8c314e73076a
>
> You can find more details below:
I've canceled all the build on this builder up to the commit that is expect to fix this error, so this should be the last one we get.
Simon
next prev parent reply other threads:[~2019-10-17 19:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 19:28 Oh dear. I regret to inform you that commit 9737e8af48e257f24e860fbf36af8c314e73076a might be unfortunate gdb-buildbot
2019-10-17 19:28 ` Breakage on builder Fedora-x86_64-w64-mingw32, revision 9737e8af48e257f24e860fbf36af8c314e73076a gdb-buildbot
2019-10-17 19:41 ` Simon Marchi [this message]
2019-10-17 19:46 ` 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=5c62c651-23e6-c986-97ef-f85184944866@simark.ca \
--to=simark@simark.ca \
--cc=amodra@gmail.com \
--cc=gdb-buildbot@sergiodj.net \
--cc=gdb-patches@sourceware.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