From: Diego Novillo <dnovillo@google.com>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: RFC: Improving support for known testsuite failures
Date: Thu, 08 Sep 2011 11:34:00 -0000 [thread overview]
Message-ID: <CAD_=9DR9tMJGwoErk-cB-byB84fv0z6DFpFir1p6k_iuQnF=Zg@mail.gmail.com> (raw)
In-Reply-To: <CAFiYyc3wDoCi4MM1Vdan=Ztv+EPgA4NTyvAYcUfcDedooc-4SA@mail.gmail.com>
On Thu, Sep 8, 2011 at 07:16, Richard Guenther
<richard.guenther@gmail.com> wrote:
> Well, you'd need to maintain a list of known XPASS/FAILs anyway.
Yes, of course. That's the manifest of things you expect to be broken.
> You can as well do it in the testcases themself (add XFAILs, remove
> XPASSes and open bugreports to not forget about this). Adding
> a separate filter or whatever just looks completely wrong to me.
The main motivation is precisely not have to deal with dejagnu's xfail
mechanisms. They are too cumbersome (details upthread).
Perhaps if there was a global marker that one could add, that would
solve my problem too. I think I'll start with a post-check filter in
contrib/
Diego.
next prev parent reply other threads:[~2011-09-08 11:34 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 [this message]
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
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='CAD_=9DR9tMJGwoErk-cB-byB84fv0z6DFpFir1p6k_iuQnF=Zg@mail.gmail.com' \
--to=dnovillo@google.com \
--cc=gcc@gcc.gnu.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).