From: Keith Seitz <keiths@redhat.com>
To: bunsen@sourceware.org
Subject: Unusual test_outcome_map keys
Date: Fri, 6 Aug 2021 12:35:56 -0700 [thread overview]
Message-ID: <b8b9518c-be0e-1862-38da-a09e8baa4009@redhat.com> (raw)
Hi,
While working on fixing up the gdb.sum parser, I've encountered
`test_outcome_map', defined in common/parse_dejagnu.py.
This is defined:
test_outcome_map = {'PASS':'PASS', 'XPASS':'XPASS', 'IPASS':'IPASS',
'FAIL':'FAIL', 'KFAIL':'KFAIL', 'XFAIL':'XFAIL',
'ERROR: tcl error sourcing':'ERROR',
'UNTESTED':'UNTESTED', 'UNSUPPORTED':'UNSUPPORTED',
'UNRESOLVED':'UNRESOLVED'}
Can you fill me in on these two unusual keys?
IPASS: This is not a standard DejaGNU test result. Is this supposed
to be KPASS (which is missing from the map)?
ERROR: tcl error sourcing: That's a pretty unusual definition of
ERROR. Was this added in order to specifically catch Tcl errors?
What about "normal" errors?
What's the preferred method for adding members to this map?
In GDB, we have a special "DUPLICATE" outcome, and right now my plan
is to simply add definitions for this (and any other additions) to our
own gdb.parse_dejagnu_sum function, e.g.,
test_outcome_map['DUPLICATE'] = 'DUPLICATE'
I'm not a huge fan of modifying global data like this, but since
Bunsen doesn't run over multiple tools at the same time, this shouldn't
be an issue.
Keith
next reply other threads:[~2021-08-06 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-06 19:35 Keith Seitz [this message]
2021-08-10 21:15 ` Serhei Makarov
2021-08-11 17:03 ` 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=b8b9518c-be0e-1862-38da-a09e8baa4009@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).