Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: fnasser@redhat.com
Cc: ac131313@redhat.com, drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: [patch/rfc] Remove all setup_xfail's from testsuite/gdb.mi/
Date: Fri, 17 Jan 2003 19:00:00 -0000	[thread overview]
Message-ID: <200301171900.h0HJ03A04642@duracef.shout.net> (raw)

Good morning xfail crew,

There are a lot of xfail's in the corpus, but the number is shrinking
steadily with time.

  % cd testsuite
  % grep -r setup_xfail gdb.* | wc

    5.2.1               649
    5.3                 577
    HEAD%20030115       517

After sleeping on the problem, I like Daniel J's path for a while.
Just keep banging on the test suite and reducing that "517" number with
no more machinery and no Andrew C Big Rip.  After we kill a bunch more
of them then we can do some kind of Big Rip or new visual markings for
the legitimate ones.

> Just one note: there are cases where the XFAIL is produced by a 'xfail'
> command inside a '-re' clause.

I count 26 of those in HEAD%20030115.

> The case for debugger format and compiler version is so common that I
> would feel tempted to have a special function for that.

The trouble is that you wind up with various boolean combinations,
such as a test that xfail's with either gcc v2 stabs or icc+blah.

I think the real issue is that we have to specify and document which
compilers that the gdb test suite supports.

Michael C


             reply	other threads:[~2003-01-17 19:00 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-17 19:00 Michael Elizabeth Chastain [this message]
2003-01-17 19:16 ` David Carlton
2003-01-17 19:20   ` David Carlton
2003-01-17 19:30     ` Daniel Jacobowitz
2003-01-17 19:28 ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2003-01-17 19:32 Michael Elizabeth Chastain
2003-01-17 19:28 Michael Elizabeth Chastain
2003-01-17 19:34 ` Daniel Jacobowitz
2003-01-16 20:06 Michael Elizabeth Chastain
2003-01-16 20:12 ` Daniel Jacobowitz
2003-01-17 14:12   ` Fernando Nasser
2003-01-17 16:05     ` Andrew Cagney
2003-01-17 14:26 ` Fernando Nasser
2003-01-16 17:12 Michael Elizabeth Chastain
2003-01-16 17:07 Michael Elizabeth Chastain
2003-01-15 17:44 Michael Elizabeth Chastain
2003-01-15 17:51 ` Daniel Jacobowitz
2003-01-16 14:27   ` Fernando Nasser
2003-01-16 14:30     ` Daniel Jacobowitz
2003-01-16 14:46       ` Fernando Nasser
2003-01-16 14:52         ` Daniel Jacobowitz
2003-01-16 15:46     ` Andrew Cagney
2003-01-16 14:20 ` Fernando Nasser
2002-10-24 11:41 Andrew Cagney
2002-10-24 12:09 ` Daniel Jacobowitz
2002-10-24 12:29   ` Andrew Cagney
2002-10-24 12:58     ` Daniel Jacobowitz
2002-10-24 14:22       ` Andrew Cagney
2002-10-24 14:26         ` Daniel Jacobowitz
2002-10-24 14:39           ` Michael Snyder
2002-10-24 16:31             ` Andrew Cagney
2002-10-24 16:36               ` Michael Snyder
2002-10-24 14:50           ` Andrew Cagney
2002-10-24 14:58             ` Michael Snyder
2002-10-24 15:31               ` Ben Elliston
2002-10-24 16:44               ` Andrew Cagney
2002-10-24 17:35                 ` Michael Snyder
2002-10-24 18:25                   ` Andrew Cagney
2002-10-24 14:18 ` Michael Snyder
2002-10-24 14:32   ` Andrew Cagney
2002-10-24 14:39 ` David Carlton
2002-10-24 14:57   ` Andrew Cagney
2002-10-24 15:00     ` Michael Snyder
2002-10-24 15:26     ` David Carlton
2002-10-24 15:36       ` Andrew Cagney
2003-01-15 15:55 ` Andrew Cagney
2003-01-15 17:25   ` Fernando Nasser
2003-01-16 16:53     ` Andrew Cagney
2003-01-16 17:05       ` Daniel Jacobowitz
2003-01-16 19:03         ` Andrew Cagney
2003-01-16 19:55           ` Daniel Jacobowitz

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=200301171900.h0HJ03A04642@duracef.shout.net \
    --to=mec@shout.net \
    --cc=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=fnasser@redhat.com \
    --cc=gdb-patches@sources.redhat.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