From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/DTS Bug 1755] Re-evaluate the link requirement decorators on all testsuites/testcases
Date: Fri, 18 Jul 2025 16:54:53 +0000 [thread overview]
Message-ID: <bug-1755-3@https.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1755
Bug ID: 1755
Summary: Re-evaluate the link requirement decorators on all
testsuites/testcases
Product: DPDK
Version: 25.03
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 are currently some testsuites/testcases that are decorated with
"requires_2_links" but in reality there is no logic associated with having 2
physical ports on the SUT. These testsuites just configure the SUT ports (even
if it's just 1) according to the testsuite requirements, and then
ingress/egress based on topology.ingress_port and topology.egress_port. For
these testsuites/testcases, we should rewrite their decorator to
"requires_1_link."
So, assess the whole list of testcases and submit a patch rewriting their
decorators.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3168 bytes --]
reply other threads:[~2025-07-18 16:54 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-1755-3@https.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.