From: Sergio Durigan Junior <sergiodj@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>, GDB <gdb-patches@sourceware.org>
Subject: Re: Oh dear. I regret to inform you that commit b1308d2c3749cc454f00b70768ee33724d919527 might be unfortunate
Date: Thu, 07 Sep 2017 19:54:00 -0000 [thread overview]
Message-ID: <87377ythbz.fsf@redhat.com> (raw)
In-Reply-To: <CAMe9rOqPmG0ywtOwPGp8Wffv45uscmnKRpYmcTpDgyfpzmxoQA@mail.gmail.com> (H. J. Lu's message of "Thu, 7 Sep 2017 12:51:55 -0700")
On Thursday, September 07 2017, H. J. Lu wrote:
> On Thu, Sep 7, 2017 at 12:41 PM, Sergio Durigan Junior
> <sergiodj@redhat.com> wrote:
>> On Thursday, September 07 2017, H. J. Lu wrote:
>>
>>> Does it build for a target for any new commits which are unrelated to the
>>> target? For example, when I make some changes to bfd/elfxx-x86.h,
>>> will it triggers a gdb build for Sparc?
>>
>> We don't have a Sparc buildslave, but every commit related to GDB that
>> touches a specific set of files:
>>
>> # Don't build commits touching only these directories
>> files_ignored_re = re.compile ("(binutils/|cpu/|elfcpp/|gas/|gold/|gprof/|ld/|texinfo/|gdb/doc/).*")
>>
>> will be built on *all* builders we have.
>
> When there is a build failure in sparc-nat.c, does a bfd/elfxx-x86.h change
> trigger a new build?
No.
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2017-09-07 19:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1dq0Uz-00056v-Ti@kwanyin.sergiodj.net>
2017-09-07 17:56 ` Palmer Dabbelt
2017-09-07 18:00 ` H.J. Lu
2017-09-07 18:57 ` Sergio Durigan Junior
2017-09-07 19:32 ` H.J. Lu
2017-09-07 19:41 ` Sergio Durigan Junior
2017-09-07 19:52 ` H.J. Lu
2017-09-07 19:54 ` Sergio Durigan Junior [this message]
2017-09-07 19:57 ` Sergio Durigan Junior
2017-09-07 23:35 ` Joel Brobecker
2017-09-08 2:10 ` H.J. Lu
2017-09-08 5:41 ` Sergio Durigan Junior
2017-09-07 18:52 ` Sergio Durigan Junior
2017-09-10 5:54 ` 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=87377ythbz.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=palmer@dabbelt.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