From: Ke Xu <ke1.xu@intel.com>
To: dts@dpdk.org
Cc: lijuan.tu@intel.com, ke1.xu@intel.com
Subject: [DTS][PATCH V1 0/2] fix result output overwriting when using multiple lines in execution configuration for one suite.
Date: Tue, 14 Mar 2023 17:01:05 +0800 [thread overview]
Message-ID: <20230314090107.669640-1-ke1.xu@intel.com> (raw)
In execution config, multi-run suites and cases are grammarly allowed.
When we call for a suite multiple times, the new result will overwrite
the old result totally.
Here we introduces two fixes.
1. We fix framework/test_result.Result.__set_test_case method for the non-checking appending.
2. We fix framework/dts.dts_parse_config method for de-duplicating suites and cases.
Ke Xu (2):
framework/test_result: fix unsafe __set_test_case
framework/dts: fix result setting by overwriting old result
with new result
framework/dts.py | 25 ++++++++++++++++++++++++-
framework/test_result.py | 5 +++--
2 files changed, 27 insertions(+), 3 deletions(-)
--
2.25.1
next reply other threads:[~2023-03-14 9:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 9:01 Ke Xu [this message]
2023-03-14 9:01 ` [DTS][PATCH V1 1/2] framework/test_result: fix unsafe __set_test_case Ke Xu
2023-03-14 9:01 ` [DTS][PATCH V1 2/2] framework/dts: fix result output by merging cases when parsing execution requirements Ke Xu
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=20230314090107.669640-1-ke1.xu@intel.com \
--to=ke1.xu@intel.com \
--cc=dts@dpdk.org \
--cc=lijuan.tu@intel.com \
/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 NNTP newsgroup(s).