Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: Brendan Kirby <brendan.kirby@imgtec.com>,
	       Peter Schauer <peterschauer@gmx.net>,
	       Simon Marchi <simon.marchi@ericsson.com>,
	gdb-patches@sourceware.org,
	       Matthew Fortune <Matthew.Fortune@imgtec.com>,
	       "Maciej W. Rozycki" <maciej.rozycki@imgtec.com>,
	       Rich Fuhler <rich.fuhler@imgtec.com>
Subject: Re: [PATCH obv/pushed] MIPS ptrace build fixes
Date: Mon, 24 Aug 2015 18:24:00 -0000	[thread overview]
Message-ID: <87wpwkbl3x.fsf@redhat.com> (raw)
In-Reply-To: <87egisczve.fsf@redhat.com> (Sergio Durigan Junior's message of	"Mon, 24 Aug 2015 14:20:21 -0400")

On Monday, August 24 2015, I wrote:

> On Monday, August 24 2015, Pedro Alves wrote:
>
>> On 08/24/2015 07:10 PM, Sergio Durigan Junior wrote:
>>> On Monday, August 24 2015, Pedro Alves wrote:
>>> 
>>>> FYI, this triggers quite often.  For the past couple weeks alone,
>>>> I got personally nagged with spurious build failures 5 times.  And
>>>> of course everyone else has been getting their share as well.
>>> 
>>> I'm looking for a way to disable e-mail notifications for this specific
>>> buildslave.  This is not trivial, but I'll see what I can do.
>>
>> I think we should also disable the test regressions
>> notifications too.  If building is unreliable, so must testing be.
>> Maybe it's simpler to disable the builder until this is sorted out?
>
> Yeah, I thought about that.  I'll disable it for now, then.

Done.  The buildslave is still connected to the BuildBot, but there are
no builders assigned to it, and therefore no e-mails will be generated
by it.

FWIW, I think I figure out a way to disable e-mail notifications
(entirely) from a builder, so if Brendan wants to test other machines to
see if the problem is solved, it can be done.

Cheers,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


  reply	other threads:[~2015-08-24 18:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29 21:19 Simon Marchi
2015-07-29 21:26 ` Simon Marchi
2015-07-29 21:59   ` Pedro Alves
2015-07-29 22:32     ` Sergio Durigan Junior
2015-07-30  9:14       ` Peter Schauer
2015-08-24 14:48         ` Pedro Alves
2015-08-24 14:59           ` Peter Schauer
2015-08-24 15:03             ` Pedro Alves
2015-08-24 17:52               ` Brendan Kirby
2015-08-24 18:04                 ` Pedro Alves
2015-08-24 18:10                   ` Sergio Durigan Junior
2015-08-24 18:17                     ` Pedro Alves
2015-08-24 18:20                       ` Sergio Durigan Junior
2015-08-24 18:24                         ` Sergio Durigan Junior [this message]
2015-08-24 18:30                           ` Brendan Kirby
2015-08-24 18:05                 ` 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=87wpwkbl3x.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=Matthew.Fortune@imgtec.com \
    --cc=brendan.kirby@imgtec.com \
    --cc=gdb-patches@sourceware.org \
    --cc=maciej.rozycki@imgtec.com \
    --cc=palves@redhat.com \
    --cc=peterschauer@gmx.net \
    --cc=rich.fuhler@imgtec.com \
    --cc=simon.marchi@ericsson.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