From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/4] Automatic detection of test name problems
Date: Thu, 23 Apr 2020 18:53:54 +0100 [thread overview]
Message-ID: <cover.1587663712.git.andrew.burgess@embecosm.com> (raw)
This started as fixing some test names in
gdb.btrace/multi-inferior.exp, but then I wanted to try and prevent
these problems creeping back in again.
So, this series extends our testing framework so that Dejagnu will now
produce two new result types, these are:
# of paths in test names
# of duplicate test names
So, the test gdb.btrace/multi-inferior.exp (without the fix in this
series) would produce results like this:
=== gdb Summary ===
# of expected passes 10
# of paths in test names 2
This indicates that two test names include either the build or source
path, which should really be resolved.
Alternatively, the test gdb.ada/fun_overload_menu.exp currently
produces results like this:
=== gdb Summary ===
# of expected passes 8
# of duplicate test names 2
Indicating that two test names are duplicated.
It is expected that users will treat these new results just like
FAILs, they should never increase these numbers when adding new tests.
It's possible for a test run to include both of the new test result
types.
I've updated the dg-extract-results scripts so that the new result
types are merged over when running the tests in parallel. I know this
change needs to go through GCC, but I wanted to discuss these patches
here first, before posting the dg-extract-results changes to the gcc
list.
I'll merge the first patch in this series (the
gdb.btrace/multi-inferior.exp fix) relatively soon as obvious.
Feedback and thoughts welcome.
Thanks,
Andrew
--
Andrew Burgess (4):
gdb/testsuite: Remove build paths from test names
gdb/testsuite: Detect and warn if paths are used in test names
gdb/testsuite: Detect and warn about duplicate test names
contrib: Handle GDB specific test result types
contrib/ChangeLog | 5 +
contrib/dg-extract-results.py | 4 +-
contrib/dg-extract-results.sh | 10 ++
gdb/testsuite/ChangeLog | 17 +++
gdb/testsuite/gdb.btrace/multi-inferior.exp | 6 +-
gdb/testsuite/lib/check-test-names.exp | 108 ++++++++++++++++++++
gdb/testsuite/lib/gdb.exp | 1 +
7 files changed, 148 insertions(+), 3 deletions(-)
create mode 100644 gdb/testsuite/lib/check-test-names.exp
--
2.25.3
next reply other threads:[~2020-04-23 17:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 17:53 Andrew Burgess [this message]
2020-04-23 17:53 ` [PATCH 1/4] gdb/testsuite: Remove build paths from test names Andrew Burgess
2020-04-24 14:00 ` Simon Marchi
2020-04-23 17:53 ` [PATCH 2/4] gdb/testsuite: Detect and warn if paths are used in " Andrew Burgess
2020-04-23 20:26 ` Keith Seitz
2020-04-27 15:58 ` Andrew Burgess
2020-04-27 16:42 ` Keith Seitz
2020-04-27 19:06 ` Andrew Burgess
2020-04-23 17:53 ` [PATCH 3/4] gdb/testsuite: Detect and warn about duplicate " Andrew Burgess
2020-04-23 20:28 ` Keith Seitz
2020-04-23 17:53 ` [PATCH 4/4] contrib: Handle GDB specific test result types Andrew Burgess
2020-04-23 20:25 ` [PATCH 0/4] Automatic detection of test name problems Keith Seitz
2020-04-27 22:01 ` [PATCHv2 0/3] " Andrew Burgess
2020-04-27 22:01 ` [PATCHv2 1/3] gdb/testsuite: Detect and warn if paths are used in test names Andrew Burgess
2020-04-27 22:01 ` [PATCHv2 2/3] gdb/testsuite: Detect and warn about duplicate " Andrew Burgess
2020-04-27 22:01 ` [PATCHv2 3/3] contrib: Handle GDB specific test result types Andrew Burgess
2020-04-28 19:08 ` [PATCHv2 0/3] Automatic detection of test name problems Keith Seitz
2020-04-29 9:02 ` Andrew Burgess
2020-04-29 15:04 ` Simon Marchi
2020-04-29 15:38 ` Andrew Burgess
2020-04-29 16:03 ` Keith Seitz
2020-04-29 18:22 ` Simon Marchi
2020-04-30 11:20 ` [PATCHv3 " Andrew Burgess
2020-04-30 11:20 ` [PATCHv3 1/3] gdb/testsuite: Detect and warn if paths are used in test names Andrew Burgess
2020-04-30 11:20 ` [PATCHv3 2/3] gdb/testsuite: Detect and warn about duplicate " Andrew Burgess
2020-07-31 21:34 ` Simon Marchi
2020-08-03 10:02 ` Andrew Burgess
2020-08-03 12:18 ` Simon Marchi
2020-04-30 11:20 ` [PATCHv3 3/3] contrib: Handle GDB specific test result types Andrew Burgess
2020-04-30 18:01 ` [PATCHv3 0/3] Automatic detection of test name problems Tom Tromey
2020-05-11 21:30 ` Andrew Burgess
2020-05-12 16:48 ` Andrew Burgess
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=cover.1587663712.git.andrew.burgess@embecosm.com \
--to=andrew.burgess@embecosm.com \
--cc=gdb-patches@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