From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1351] Testbed capabilities for test case skipping
Date: Wed, 10 Jan 2024 09:38:21 +0000 [thread overview]
Message-ID: <bug-1351-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1439 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1351
Bug ID: 1351
Summary: Testbed capabilities for test case skipping
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: dts
Assignee: dev@dpdk.org
Reporter: juraj.linkes@pantheon.tech
CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu
Target Milestone: ---
The different hardware DPDK supports is not homogeneous and support a variety
of different features. A user-friendly solution would probe the hardware under
test and skip all test cases that cannot be executed due to missing features.
There are multiple dimensions to this task.
1. Device probing. We can leverage existing DPDK probing capabilities in a DPDK
app. A machine-readable output format must be defined, such as json. The fields
themselves must be well-defined.
2. Test case/suite marking with required capabilities. If a test case isn't
marked, it should run on all hardware. There could be different names for the
same feature across different hardware, in which case we should decide whether
we want to merge these under one DTS-defined name or we'll mark each test
case/suite with multiple names.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3383 bytes --]
reply other threads:[~2024-01-10 9:38 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-1351-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).