From: Hans-Peter Nilsson <hp@bitrange.com>
To: Diego Novillo <dnovillo@google.com>
Cc: gcc@gcc.gnu.org
Subject: Re: RFC: Improving support for known testsuite failures
Date: Fri, 23 Sep 2011 00:07:00 -0000 [thread overview]
Message-ID: <alpine.BSF.2.00.1109221955140.80262@dair.pair.com> (raw)
In-Reply-To: <CAD_=9DQ7CaJc8HN9emsN7-7xiQBQFdwrbJ4mKevSWkHakBgrPw@mail.gmail.com>
On Thu, 8 Sep 2011, Diego Novillo wrote:
> On Thu, Sep 8, 2011 at 04:31, Richard Guenther
> <richard.guenther@gmail.com> wrote:
>
> > I think it would be more useful to have a script parse gcc-testresults@
> > postings from the various autotesters and produce a nice webpage
> > with revisions and known FAIL/XPASSes for the target triplets that
> > are tested.
>
> Sure, though that describes a different tool. I'm after a tool that
> will 'exit 0' if the testsuite finished with nominal results.
Not to stop you from (partly) reinventing the wheel, but that's
pretty much what contrib/regression/btest-gcc.sh already does,
though you have to feed it a baseline a set of processed .sum
files which could (for a calling script or a modified
btest-gcc.sh) live in, say, contrib/target-results/<target>.
It handles "duplicate" test names by marking it as failing if
any of them has failed. Works good enough.
brgds, H-P
next prev parent reply other threads:[~2011-09-23 0:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 15:28 Diego Novillo
2011-09-07 18:43 ` Andreas Jaeger
2011-09-07 19:57 ` Joseph S. Myers
2011-09-08 8:31 ` Richard Guenther
2011-09-08 11:05 ` Diego Novillo
2011-09-08 11:16 ` Richard Guenther
2011-09-08 11:34 ` Diego Novillo
2011-09-08 11:49 ` Richard Guenther
2011-09-08 12:14 ` Diego Novillo
2011-09-08 12:20 ` Richard Guenther
2011-09-08 12:26 ` Diego Novillo
2011-09-08 12:30 ` Richard Guenther
2011-09-08 12:33 ` Diego Novillo
2011-09-08 13:24 ` Richard Earnshaw
2011-09-08 13:55 ` Diego Novillo
2011-09-08 14:03 ` Richard Earnshaw
2011-09-08 16:41 ` Joseph S. Myers
2011-09-23 0:07 ` Hans-Peter Nilsson [this message]
2011-09-23 13:11 ` Diego Novillo
2011-09-08 16:39 ` Joseph S. Myers
2011-09-08 22:27 ` Michael Hope
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=alpine.BSF.2.00.1109221955140.80262@dair.pair.com \
--to=hp@bitrange.com \
--cc=dnovillo@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).