Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: ac131313@cygnus.com, drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa:testsuite} Overhaul sizeof.exp
Date: Wed, 20 Feb 2002 10:06:00 -0000	[thread overview]
Message-ID: <3C73E572.ECEEEF5E@redhat.com> (raw)
In-Reply-To: <200202201749.g1KHnlv04009@duracef.shout.net>

I can take a look at the KFAIL stuff this weekend if you want.

But if the ample majority wants to try again [2] and is willing to
work in establishing polices to try and make that work
this time and is willing to help enforcing those polices I would
agree with that.

So, I am for [3]->[2']->[0']

2' - [2] with extrict polices to prevent xfails to be forgotten.

0' - [0] but the tests are saved somewhere, so they are added
     when the fix goes in.

Fernando

Michael Elizabeth Chastain wrote:
> 
> It sounds like we understand the alternatives and everyone's got opinions
> about them.
> 
>   [0] Status quo
>   [1] FAIL the test
>   [2] XFAIL the test
>   [3] KFAIL the test
> 
> I'm concerned that for each alternative, someone will find a flaw, and
> therefore we'll stick with [0] and keep rejecting useful tests.
> 
> Fernando and Daniel and Andrew, I'd like to hold your feet to the fire:
> Can you please rank these in priority order and indicate how many of the
> high priority ones are acceptable.
> 
> Also there may very well be a [4] that I haven't heard of or thought of.
> 
> My rank is [2] > [1] > [3] > [0].  [2], [1], and [3] are acceptable to me.
> [0] is not.
> 
> Michael C

-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9


  reply	other threads:[~2002-02-20 18:06 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-20  9:49 Michael Elizabeth Chastain
2002-02-20 10:06 ` Fernando Nasser [this message]
2002-02-20 10:12   ` Daniel Jacobowitz
2002-02-20 10:07 ` Richard Earnshaw
2002-02-20 10:07 ` Daniel Jacobowitz
2002-02-20 10:18   ` Fernando Nasser
  -- strict thread matches above, loose matches on Subject: below --
2002-02-20 10:24 Michael Elizabeth Chastain
2002-02-20 11:48 ` Fernando Nasser
2002-02-20  9:17 Michael Elizabeth Chastain
2002-02-20  9:42 ` Fernando Nasser
2002-02-20 10:20 ` Andrew Cagney
2002-02-20  8:59 Michael Elizabeth Chastain
2002-02-19 20:57 Michael Elizabeth Chastain
2002-02-20  6:57 ` Andrew Cagney
2002-02-20  7:21   ` Andrew Cagney
2002-02-20  8:19     ` Fernando Nasser
2002-02-20 17:57       ` Andrew Cagney
2002-02-20  8:16   ` Fernando Nasser
2002-02-20  8:51     ` Daniel Jacobowitz
2002-02-20  9:24       ` Fernando Nasser
2002-02-21 14:04       ` Jim Blandy
2002-02-21 14:23         ` Daniel Jacobowitz
2002-02-19 20:43 Michael Elizabeth Chastain
2002-02-21 14:03 ` Jim Blandy
2002-02-19 15:46 Michael Elizabeth Chastain
2002-02-19 18:19 ` Andrew Cagney
2002-02-19 15:17 Andrew Cagney

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=3C73E572.ECEEEF5E@redhat.com \
    --to=fnasser@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mec@shout.net \
    /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