From: Dodji Seketeli <dodji@redhat.com>
To: Laurent GUERBY <laurent@guerby.net>
Cc: Paolo Bonzini <paolo.bonzini@gmail.com>,
Eric Botcazou <ebotcazou@adacore.com>,
Paolo Bonzini <bonzini@gnu.org>,
gcc@gcc.gnu.org, Geoff Keating <geoffk@geoffk.org>,
Richard Guenther <richard.guenther@gmail.com>,
Dominique Dhumieres <dominiq@lps.ens.fr>,
"charlet@adacore.com" <charlet@adacore.com>
Subject: Re: GCC build failure, HEAD@149166 on native
Date: Fri, 03 Jul 2009 15:31:00 -0000 [thread overview]
Message-ID: <4A4E23D7.7020900@redhat.com> (raw)
In-Reply-To: <1246629526.10492.41.camel@localhost>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le 03/07/2009 15:58, Laurent GUERBY a écrit :
[...]
> Right now the bootstrap+check loops I run on the compile farm cover the
> following *-linux platforms with c,ada unless otherwise specified:
>
> gcc13 x86_64 trunk 3h30
> gcc15 x86_64 4.4 6h30 (-j 2)
> gcc40 powerpc64 trunk 6h00
> gcc50 armv5tel trunk 112h00 (c,c++,fortran)
> gcc51 mips64el trunk 21h00 tri ABI
> gcc53 powerpc trunk 8h00
> gcc54 sparc trunk 25h00
> gcc60 ia64 trunk 8h30
> gcc61 hppa trunk 22h00
> gcc62 sparc64 trunk 28h00
>
> Currently my script loops silently in case of bootstrap failure. I can
> make the script send a mail to gcc-regression@ when bootstrap state
> change (work then fail, and fail then work) if there's consensus it's
> useful (I don't know if people follow gcc-regression@).
It would certainly be useful to me at least as I check gcc-regression
before fetching new bits from the gcc repository.
Thanks.
- --
Dodji Seketeli
Red Hat, Inc.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAkpOI9cACgkQPejI7lrem2GVxQCgvQKX5RsDVfIcLhurKJSrk9Eh
dkMAnj2iRT1APLvnopyYaQMdF858wIhG
=M6Wz
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2009-07-03 15:31 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
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 [this message]
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=4A4E23D7.7020900@redhat.com \
--to=dodji@redhat.com \
--cc=bonzini@gnu.org \
--cc=charlet@adacore.com \
--cc=dominiq@lps.ens.fr \
--cc=ebotcazou@adacore.com \
--cc=gcc@gcc.gnu.org \
--cc=geoffk@geoffk.org \
--cc=laurent@guerby.net \
--cc=paolo.bonzini@gmail.com \
--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).