From: Keith Seitz <keiths@redhat.com>
To: bunsen@sourceware.org
Subject: [PATCH 4/4] Add support for reading the target_board
Date: Wed, 18 Aug 2021 12:26:39 -0700 [thread overview]
Message-ID: <20210818192639.2362335-5-keiths@redhat.com> (raw)
In-Reply-To: <20210818192639.2362335-1-keiths@redhat.com>
The model has some minimal support for DejaGNU target_board already,
but it is not being recorded anywhere. This patch adds these missing
bits.
GDB testing regularly includes several target boards, e.g.,
unix/-m32, native-extended-gdbserver/-m64, and so on. The target
board is output to gdb.{log,sum} with the line
Running target TARGET_BOARD
Note that Bunsen can currently only handle one target board at a time.
This is not an attempt to fix that yet.
After this patch, +summarize should be able to output this information
(instead of the current "<unknown board>". To use this feature,
data must obviously be re-imported.
---
scripts-main/gdb/parse_dejagnu.py | 3 +++
1 file changed, 3 insertions(+)
diff --git a/scripts-main/gdb/parse_dejagnu.py b/scripts-main/gdb/parse_dejagnu.py
index fc6a30e..a23e74c 100755
--- a/scripts-main/gdb/parse_dejagnu.py
+++ b/scripts-main/gdb/parse_dejagnu.py
@@ -158,6 +158,9 @@ def parse_dejagnu_sum(testrun, sumfile, all_cases=None,
# We tried. Nothing else we can do.
print("WARNING: unknown expname/subtest in outcome line --", line, file=sys.stderr)
continue
+ elif line.startswith("Running target "):
+ testrun.target_board = line[len("Running target "):].strip()
+ continue
else:
continue
--
2.31.1
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 ` [PATCH 3/4] Add new outcomes to summarize script Keith Seitz
2021-08-18 19:26 ` Keith Seitz [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=20210818192639.2362335-5-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).