Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com
Cc: ac131313@cygnus.com, eliz@is.elta.co.il, fnasser@redhat.com,
	gdb-patches@sources.redhat.com, rob@welcomehome.org
Subject: Re: RFC: KFAIL DejaGnu patch
Date: Mon, 08 Apr 2002 11:56:00 -0000	[thread overview]
Message-ID: <200204081856.g38Iu6L14269@duracef.shout.net> (raw)

Daniel Jacobowitz writes:
> That would only be useful if we always marked all tests - which we're
> awful about.  continue {2} might be any number of different continue
> statements in the test.

Let me explain in more detail.

Right now there are tests with output like this:

  gdb.base/foo.exp: PASS: continue
  gdb.base/foo.exp: PASS: continue
  gdb.base/foo.exp: PASS: continue
  gdb.base/foo.exp: PASS: continue

I have to do something to make the test names unique.  So I behave
as if the input is this:

  gdb.base/foo.exp: PASS: continue
  gdb.base/foo.exp: PASS: continue {2}
  gdb.base/foo.exp: PASS: continue {3}
  gdb.base/foo.exp: PASS: continue {4}

This is flawed, because if someone adds or subtracts sections from
the test, the sequence numbers will get re-numbered, and I lose the
ability to compare across many runs.  As you point out, "continue {2}"
might be in different places depending on conditional execution and
so on.

But I have to do *something*.  If I just do "$hash{$name} = $result",
then the totals don't even add up correctly.

Michael C


             reply	other threads:[~2002-04-08 18:56 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-08 11:56 Michael Elizabeth Chastain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-09  9:13 Michael Elizabeth Chastain
2002-04-09  9:34 ` Rob Savoye
2002-04-08 10:34 Michael Elizabeth Chastain
2002-04-08 11:38 ` Daniel Jacobowitz
2002-04-09  7:50 ` Rob Savoye
2002-04-08  9:57 Michael Elizabeth Chastain
2002-04-07 18:41 Michael Elizabeth Chastain
2002-04-07  9:10 Michael Elizabeth Chastain
2002-04-06 14:40 Michael Elizabeth Chastain
2002-04-05 17:57 Michael Elizabeth Chastain
2002-04-05 16:51 Michael Elizabeth Chastain
2002-04-05  9:53 RFC: KFAILs [Was: [RFA/mi-testsuite] XFAIL mi*-console.exp] Michael Elizabeth Chastain
2002-04-05 16:32 ` RFC: KFAIL DejaGnu patch Fernando Nasser
2002-04-05 17:05   ` Andrew Cagney
2002-04-07 16:25     ` Rob Savoye
2002-04-05 17:10   ` Daniel Jacobowitz
2002-04-05 17:40     ` Andrew Cagney
2002-04-08  8:37     ` Fernando Nasser
2002-04-07 16:29   ` Rob Savoye
2002-04-07 22:05     ` Eli Zaretskii
2002-04-08  8:22       ` Rob Savoye
2002-04-08  8:52         ` Fernando Nasser
2002-04-08  9:01           ` Rob Savoye
2002-04-08  8:41     ` Fernando Nasser
2002-04-08  9:00       ` Rob Savoye
2002-04-08 13:55         ` Andrew Cagney
2002-04-08 16:21           ` Rob Savoye
2002-04-08 16:34             ` Andrew Cagney
2002-04-08 16:48               ` Rob Savoye
2002-04-08 16:58                 ` Andrew Cagney
2002-04-08 17:09                   ` Rob Savoye
2002-04-08 23:58                     ` Eli Zaretskii
2002-04-09  7:38                       ` Rob Savoye
2002-04-08 23:53               ` Eli Zaretskii
2002-04-09  7:06                 ` 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=200204081856.g38Iu6L14269@duracef.shout.net \
    --to=mec@shout.net \
    --cc=ac131313@cygnus.com \
    --cc=drow@mvista.com \
    --cc=eliz@is.elta.co.il \
    --cc=fnasser@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=rob@welcomehome.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