public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gmail.com>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: Dominique Dhumieres <dominiq@lps.ens.fr>,
	 "richard.guenther@gmail.com" <richard.guenther@gmail.com>,
	 "geoffk@geoffk.org" <geoffk@geoffk.org>,
	 "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
	 "charlet@adacore.com" <charlet@adacore.com>
Subject: Re: GCC build failure, HEAD@149166 on native
Date: Thu, 02 Jul 2009 15:33:00 -0000	[thread overview]
Message-ID: <9F246854-58B4-4CEE-9BEF-D498161D171B@gmail.com> (raw)
In-Reply-To: <4A4C9785.505@gnu.org>



Sent from my iPhone

On Jul 2, 2009, at 4:18 AM, Paolo Bonzini <bonzini@gnu.org> wrote:

> On 07/02/2009 12:06 PM, Dominique Dhumieres wrote:
>> Andrew Haley wrote
>>> Is this really a good idea?  Surely the solution is to fix the
>>> failures on Darwin.
>>
>> I don't this is a good idea. As noted by Andrew Pinski, one failure
>> was Darwin specific and is now fixed, two others are powerpc ones.
>> When they will be fixed on trunk the annoying mails will  
>> automatically
>> disappear.
>
> However, this does not mean that tuning the regression tester to not  
> sending more than 6 emails a day (one every 4 hours) would be a bad  
> idea.

It is once every commit until it is fixed which seems like the correct  
way of doing it really. We really should be frozen during the period  
it is broken. Otherwise more things break like what happened here.

--Pinski

>
> Paolo

  parent reply	other threads:[~2009-07-02 15:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02  9:20 Dominique Dhumieres
2009-07-02  9:36 ` Richard Guenther
2009-07-02  9:40   ` Andrew Haley
2009-07-02  9:41   ` Andrew Pinski
2009-07-02  9:42     ` Andrew Pinski
2009-07-02 10:08   ` Dominique Dhumieres
2009-07-02 11:18     ` Paolo Bonzini
2009-07-02 13:11       ` Dominique Dhumieres
2009-07-02 13:37         ` Paolo Bonzini
2009-07-02 15:33       ` Andrew Pinski [this message]
2009-07-02 21:10   ` Geoff Keating
2009-07-02 21:23     ` Paolo Bonzini
2009-07-03  5:29       ` Eric Botcazou
2009-07-03  5:43         ` Paolo Bonzini
2009-07-03 13:58           ` Laurent GUERBY
2009-07-03 15:31             ` Dodji Seketeli
2009-07-03 11:37       ` David Edelsohn
2009-07-03 11:47         ` Paolo Bonzini

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=9F246854-58B4-4CEE-9BEF-D498161D171B@gmail.com \
    --to=pinskia@gmail.com \
    --cc=bonzini@gnu.org \
    --cc=charlet@adacore.com \
    --cc=dominiq@lps.ens.fr \
    --cc=gcc@gcc.gnu.org \
    --cc=geoffk@geoffk.org \
    --cc=richard.guenther@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).