public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "brobecker at gnat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/12505] New: test comments in gdb.python/py-breakpoint.exp should be unique
Date: Wed, 23 Feb 2011 03:42:00 -0000	[thread overview]
Message-ID: <bug-12505-4717@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=12505

           Summary: test comments in gdb.python/py-breakpoint.exp should
                    be unique
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: minor
          Priority: P2
         Component: testsuite
        AssignedTo: unassigned@sourceware.org
        ReportedBy: brobecker@gnat.com


There are several tests in this testcase that share the same comment (the label
that gets displayed besides the test result) with other tests in the same
testcase.

We should make each comment unique, to facilitate test identification, as well
as helping with testcase result analysis/comparison.

Example:
gdb_py_test_silent_cmd "python blist = gdb.breakpoints()" "Get Breakpoint List"
0
[a few lines later...]
gdb_py_test_silent_cmd "python blist = gdb.breakpoints()" "Get Breakpoint List"
0

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2011-02-23  3:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-23  3:42 brobecker at gnat dot com [this message]
2022-05-16 18:15 ` [Bug testsuite/12505] " tromey at sourceware dot org

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=bug-12505-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).