From: Jim Blandy <jimb@redhat.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: give store.exp tests unique names
Date: Thu, 06 Nov 2003 07:38:00 -0000 [thread overview]
Message-ID: <vt28ymuq75i.fsf@zenia.home> (raw)
In-Reply-To: <200311060644.hA66i7hx029405@duracef.shout.net>
Michael Elizabeth Chastain <mec@shout.net> writes:
> When my Crunch.pl sees a duplicate, it just renames the duplicate
> to "gdb.foo/bar {2}", and then "gdb.foo/bar {3}", and so on.
> Crunch.pl prints a count of duplicates on stdout but I don't
> even pay attention to that any more.
>
> Most of the duplicates are in tests that always PASS so it's
> low priority to get them cleaned up. Did this one in store.exp
> cause an actual problem? If it did, I'm all for stomping on it.
Yes, I've got a target where some of the tests are failing, and we
have an internal regression-tracking system that gets upset when the
names aren't unique.
> No comments on your specific patch, I'm too tired.
Well, fine. I won't comment on your lack of comments on my patch ---
because *I'm* too tired.
:)
next prev parent reply other threads:[~2003-11-06 7:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-06 6:44 Michael Elizabeth Chastain
2003-11-06 7:38 ` Jim Blandy [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-06 16:49 Michael Elizabeth Chastain
2003-11-06 4:57 Jim Blandy
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=vt28ymuq75i.fsf@zenia.home \
--to=jimb@redhat.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