From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/DTS Bug 1872] Introduce "fast tests" concept to DTS
Date: Tue, 27 Jan 2026 17:37:00 +0000 [thread overview]
Message-ID: <bug-1872-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1872
Bug ID: 1872
Summary: Introduce "fast tests" concept to DTS
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: minor
Priority: Normal
Component: DTS
Assignee: dev@dpdk.org
Reporter: probb@iol.unh.edu
CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu
Target Milestone: ---
We currently have a new rte_flow testsuite under review. It creates 1000+ rules
and validates them with real traffic. So, the testsuite takes a while to run
(approx 10 minutes) which is very different from most testsuites (run in
seconds or low tens of seconds).
People may want to run "fast tests" as a part of their development workflow
when making new DPDK patches, but may want to run the "long tests" like the
comprehensive rte_flow testsuite less frequently, or only on CI systems.
Perhaps it would make sense for us to add a "long tests" decorator or similar,
and a "fast-tests-only" boolean config value to test_run.yaml which defaults to
true.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2026-01-27 17:37 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-1872-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