From: Diego Novillo <dnovillo@google.com>
To: gcc@gcc.gnu.org, Lawrence Crowl <crowl@google.com>
Subject: [pph] Merge from trunk
Date: Wed, 21 Sep 2011 20:22:00 -0000 [thread overview]
Message-ID: <20110921202159.GA23146@google.com> (raw)
Lawrence,
This merge brings the testsuite validation script. You can use
it after builds with:
$ cd <top-bld-dir>
$ <src>/contrib/testsuite-management/validate_failures.py
It will tell you what new failures you have in the build.
Tested on x86_64. Committed to branch.
Diego.
next reply other threads:[~2011-09-21 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 20:22 Diego Novillo [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-04 18:26 Diego Novillo
2012-02-10 16:00 Diego Novillo
2011-12-15 15:21 Diego Novillo
2011-08-11 16:02 Diego Novillo
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=20110921202159.GA23146@google.com \
--to=dnovillo@google.com \
--cc=crowl@google.com \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).