DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: aconole@redhat.com
Subject: [dpdk-dev] [PATCH 1/2] test: create a list of extra tests
Date: Wed, 27 Oct 2021 16:04:57 +0200	[thread overview]
Message-ID: <20211027140458.2502-1-david.marchand@redhat.com> (raw)

We removed some tests from the "CI" (fast-tests) list because they
were not reliable enough or did not make sense as non regression tests.
Since we still build those tests code, leave an option for users to call
them.
This list can also serve as a point where to document why test X is not
suitable for the "CI" list.

Signed-off-by: David Marchand <david.marchand@redhat.com>
---
 app/test/meson.build | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/app/test/meson.build b/app/test/meson.build
index 20f36a1803..200790eda0 100644
--- a/app/test/meson.build
+++ b/app/test/meson.build
@@ -287,6 +287,14 @@ fast_tests = [
         ['trace_autotest', true],
 ]
 
+# Tests known to have issues or which don't belong in other tests lists.
+extra_test_names = [
+        # ee00af60170b ("test: remove strict timing requirements some tests")
+        'alarm_autotest',
+        'cycles_autotest',
+        'delay_us_sleep_autotest',
+]
+
 perf_test_names = [
         'ring_perf_autotest',
         'mempool_perf_autotest',
@@ -525,3 +533,11 @@ foreach arg : dump_test_names
             is_parallel : false,
             suite : 'debug-tests')
 endforeach
+
+foreach arg : extra_test_names
+    test(arg, dpdk_test,
+            env : ['DPDK_TEST=' + arg],
+            timeout : timeout_seconds,
+            is_parallel : false,
+            suite : 'extra-tests')
+endforeach
-- 
2.23.0


             reply	other threads:[~2021-10-27 14:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-27 14:04 David Marchand [this message]
2021-10-27 14:04 ` [dpdk-dev] [PATCH 2/2] test: move RED to extra tests list David Marchand
2021-11-16 15:38   ` David Marchand

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=20211027140458.2502-1-david.marchand@redhat.com \
    --to=david.marchand@redhat.com \
    --cc=aconole@redhat.com \
    --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).