public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/29778] [gdb/testsuite] Revise untested usage
Date: Fri, 18 Nov 2022 15:51:54 +0000	[thread overview]
Message-ID: <bug-29778-4717-6UCIMYVPtM@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29778-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29778

--- Comment #7 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #4)
> (In reply to Simon Marchi from comment #3)
> > > And then there are the test-cases that use proc skip_ variants which largely seem happy to skip only doing "verbose $msg" or just silently.
> > 
> > I think all tests should at least record at least one untested or
> > unsupported, so that there's a trace in gdb.sum.
> 
> I think that's an ok principle, but once the volume grows the usefulness is
> reduced.
> 
> I think it's fine to avoid generating noise.  For instance, I would consider
> it noise to record that a ppc64-specific test is not run on x86_64.

And we could also avoid noise by emitting one untested/unsupported per skip
group.  I don't need to know that gdb.server/*.exp is skipped for each
test-case, if gdbserver is unavailable.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-11-18 15:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-12 10:42 [Bug testsuite/29778] New: " vries at gcc dot gnu.org
2022-11-15 10:53 ` [Bug testsuite/29778] " vries at gcc dot gnu.org
2022-11-15 11:49 ` vries at gcc dot gnu.org
2022-11-15 14:35 ` simon.marchi at polymtl dot ca
2022-11-18 15:33 ` vries at gcc dot gnu.org
2022-11-18 15:39 ` vries at gcc dot gnu.org
2022-11-18 15:41 ` vries at gcc dot gnu.org
2022-11-18 15:51 ` vries at gcc dot gnu.org [this message]
2023-01-18 19:02 ` tromey at sourceware dot org
2023-01-19  2:26 ` sam at gentoo dot org
2023-01-22 17:31 ` 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-29778-4717-6UCIMYVPtM@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).