public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug testsuite/29778] [gdb/testsuite] Revise untested usage
Date: Sun, 22 Jan 2023 17:31:28 +0000	[thread overview]
Message-ID: <bug-29778-4717-w45svq60K0@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 #9 from Tom Tromey <tromey at sourceware dot org> ---
I found a case where the noisier output would be actively helpful.
For me, dw2-ranges.exp started silently doing nothing.
Investigating it:

/home/tromey/gdb/build/gdb/testsuite/../../../binutils-gdb/gdb/testsuite/gdb.dwarf2/dw2-ranges-3.c:
warning: STABS debugging information is obsolete and not supported anymore

So, a new compiler warning means we started skipping a test.

If every early return had some annotation that showed up in the .sum,
we could detect this scenario... not saying there's anything to do
about it, but it seems better to flag it an intentionally ignore
it than to have some tests simply silently stop running and never
really find out.

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

      parent reply	other threads:[~2023-01-22 17:31 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
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 [this message]

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-w45svq60K0@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).