From: Keith Seitz <keiths@redhat.com>
To: bunsen@sourceware.org
Subject: [PATCH 3/4] Add new outcomes to summarize script
Date: Wed, 18 Aug 2021 12:26:38 -0700 [thread overview]
Message-ID: <20210818192639.2362335-4-keiths@redhat.com> (raw)
In-Reply-To: <20210818192639.2362335-1-keiths@redhat.com>
GDB has a number of custom test outcomes which occasionally appear
in test results. This patch adds the appropriate DejaGNU output string
for these outcomes.
This patch also outputs a footnote whenever the DUPLICATE outcome
is seen. For GDB, this number will not be the same as the number
reported in gdb.sum, since that reported number is the number
of unique duplicates. The number we record in Bunsen is the
total number of tests that have the DUPLICATE outcome.
$ grep "of duplicate test names" gdb.sum
# of duplicate test names 357
vs
$ grep ^DUPLICATE gdb.log | wc -l
428
It is this last number that the script reports.
---
scripts-main/summarize.py | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/scripts-main/summarize.py b/scripts-main/summarize.py
index 1e30135..f338b53 100755
--- a/scripts-main/summarize.py
+++ b/scripts-main/summarize.py
@@ -30,6 +30,8 @@ outcome_labels = {
'UNTESTED' : 'untested testcases',
'UNRESOLVED' : 'unresolved testcases',
'UNSUPPORTED' : 'unsupported tests',
+ 'PATH' : "paths in test names",
+ 'DUPLICATE' : "duplicate test names",
'ERROR' : 'errors',
'WARNING' : 'warnings'
}
@@ -72,6 +74,12 @@ if __name__ == '__main__':
# us the same output order as DejaGNU itself.
for l in outcome_labels:
if c[l] != 0:
- print('# of %-26s %d' % (outcome_labels[l], c[l]))
+ print('# of %-26s %d' % (outcome_labels[l], c[l]), "*" if l == 'DUPLICATE' else "")
+
+ # Output the footnote explaining that reported DUPLICATE numbers are different than
+ # what GDB reports.
+ if c['DUPLICATE'] != 0:
+ print("\n* This number is the total number of tests with duplicate names, not")
+ print(" the number of unique duplicate names seen.")
else:
print(f'found no tests matching \"{opts.tests}\"')
--
2.31.1
next prev parent reply other threads:[~2021-08-18 19:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 19:26 Fix GDB data imports Keith Seitz
2021-08-18 19:26 ` [PATCH 1/4] Rewrite gdb.parse_dejagnu_sum Keith Seitz
2021-08-19 12:40 ` Serhei Makarov
2021-08-19 15:33 ` Keith Seitz
2021-08-18 19:26 ` [PATCH 2/4] Add verbose option to +summarize Keith Seitz
2021-08-18 19:26 ` Keith Seitz [this message]
2021-08-18 19:26 ` [PATCH 4/4] Add support for reading the target_board Keith Seitz
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=20210818192639.2362335-4-keiths@redhat.com \
--to=keiths@redhat.com \
--cc=bunsen@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).