From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK Bug 1375] Make limited use of "per testsuite" conf files.
Date: Thu, 25 Jan 2024 20:00:56 +0000 [thread overview]
Message-ID: <bug-1375-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1450 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1375
Bug ID: 1375
Summary: Make limited use of "per testsuite" conf files.
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: dts
Assignee: dev@dpdk.org
Reporter: probb@iol.unh.edu
CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu
Target Milestone: ---
There will be examples of testsuite which require some divserse input on a per
testsuite or environment basis (setting expected baselines for a testsuite in
perf testing is one example). So, we are going to be doing this at some point
anyways, and I think it is okay to do so now with functional tests too if it
can help make testsuites more concise.
I don't want this suggestion to be conflated with our previous discussion about
building a YAML schema and intepreter for taking testsuite parameters and also
python functions and mapping that to a python testsuite. I think it's clear
based on our 1/24 meeting that we are not going in that direction. However, we
probably do need per-testsuite conf files for some (but not all) suites. I
think how we best leverage this can be a discussion point for next week's DTS
meeting.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3418 bytes --]
reply other threads:[~2024-01-25 20:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-1375-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.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 NNTP newsgroup(s).