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/29772] [gdb/testsuite] Detect duplicates for "FAIL: foo" and "FAIL: foo (timeout)"
Date: Sun, 22 Jan 2023 17:58:49 +0000 [thread overview]
Message-ID: <bug-29772-4717-Ty1GgtJnsK@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29772-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29772
Tom Tromey <tromey at sourceware dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tromey at sourceware dot org
--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
I tried this and ugh... I wonder if it would be simpler to
change the suffix for auxiliary information. Really it
would be nicer if this were a dejagnu feature, like
fail -reason Text testname
... but meanwhile what if we made it something unlikely to appear
in real syntax, like fail "testname <<<timeout>>>"
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-01-22 17:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 10:57 [Bug testsuite/29772] New: " vries at gcc dot gnu.org
2022-11-10 12:53 ` [Bug testsuite/29772] " vries at gcc dot gnu.org
2022-12-06 18:45 ` pedro at palves dot net
2023-01-22 17:58 ` tromey at sourceware dot org [this message]
2023-01-22 21:53 ` tromey at sourceware dot org
2024-07-16 13:02 ` vries at gcc dot gnu.org
2024-07-31 13:04 ` cvs-commit at gcc dot gnu.org
2024-07-31 13:04 ` vries at gcc dot gnu.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-29772-4717-Ty1GgtJnsK@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).