From: Patrick Robb <probb@iol.unh.edu>
To: Paul.Szczepanek@arm.com
Cc: probb@iol.unh.edu, Luca.Vizzarro@arm.com, dev@dpdk.org,
dmarx@iol.unh.edu, npratte@iol.unh.edu
Subject: [PATCH 3/4] dts: default smoke tests to off
Date: Wed, 9 Apr 2025 18:38:24 -0400 [thread overview]
Message-ID: <20250409223825.1579256-4-probb@iol.unh.edu> (raw)
In-Reply-To: <20250409223825.1579256-1-probb@iol.unh.edu>
Set smoke tests to false in the example config so that
users will have to consciously decide whether the
smoke tests will be run or not.
Signed-off-by: Patrick Robb <probb@iol.unh.edu>
---
dts/test_run.example.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dts/test_run.example.yaml b/dts/test_run.example.yaml
index 330a31bb18..1bc436eed1 100644
--- a/dts/test_run.example.yaml
+++ b/dts/test_run.example.yaml
@@ -27,7 +27,7 @@ traffic_generator:
type: SCAPY
perf: false # disable performance testing
func: true # enable functional testing
-skip_smoke_tests: false # optional
+skip_smoke_tests: true # optional
# by removing the `test_suites` field, this test run will run every test suite available
test_suites: # the following test suites will be run in their entirety
- hello_world
--
2.48.1
next prev parent reply other threads:[~2025-04-09 22:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 2:30 [PATCH 0/2] dts: smoke test bugfixes Patrick Robb
2025-04-03 2:30 ` [PATCH 1/2] dts: include smoke tests in tests config Patrick Robb
2025-04-03 13:45 ` Luca Vizzarro
2025-04-03 13:42 ` Patrick Robb
2025-04-03 2:30 ` [PATCH 2/2] dts: update dpdk-devbind script regex Patrick Robb
2025-04-03 13:45 ` Luca Vizzarro
2025-04-09 22:38 ` [PATCH 0/4] dts: smoke test bugfixes Patrick Robb
2025-04-09 22:38 ` [PATCH 1/4] dts: include smoke tests in tests config Patrick Robb
2025-04-09 22:38 ` [PATCH 2/4] dts: update dpdk-devbind script regex Patrick Robb
2025-04-09 22:38 ` Patrick Robb [this message]
2025-04-09 22:38 ` [PATCH 4/4] dts: extend meson fast tests timeout Patrick Robb
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=20250409223825.1579256-4-probb@iol.unh.edu \
--to=probb@iol.unh.edu \
--cc=Luca.Vizzarro@arm.com \
--cc=Paul.Szczepanek@arm.com \
--cc=dev@dpdk.org \
--cc=dmarx@iol.unh.edu \
--cc=npratte@iol.unh.edu \
/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).