DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Subject: [PATCH 1/2] test: add graph tests
Date: Mon, 19 Jun 2023 22:46:49 +0200	[thread overview]
Message-ID: <20230619204650.3348681-1-david.marchand@redhat.com> (raw)

We forgot to add graph unit tests to the CI testsuites.

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

diff --git a/app/test/meson.build b/app/test/meson.build
index d0fabcbb8b..35d6baeb22 100644
--- a/app/test/meson.build
+++ b/app/test/meson.build
@@ -250,6 +250,8 @@ fast_tests = [
         ['thash_autotest', true, true],
         ['threads_autotest', true, true],
         ['trace_autotest', true, true],
+        ['graph_autotest', true, true],
+        ['node_list_dump', true, true],
 ]
 
 # Tests known to have issues or which don't belong in other tests lists.
@@ -298,6 +300,7 @@ perf_test_names = [
         'trace_perf_autotest',
         'ipsec_perf_autotest',
         'thash_perf_autotest',
+        'graph_perf_autotest',
 ]
 
 driver_test_names = [
-- 
2.40.1


             reply	other threads:[~2023-06-19 20:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-19 20:46 David Marchand [this message]
2023-06-19 20:46 ` [PATCH 2/2] lib: make graph optional David Marchand
2023-06-20  6:56   ` Jerin Jacob
2023-06-20  7:09     ` David Marchand
2023-06-20  8:10   ` Bruce Richardson
2023-06-20  8:20     ` Jerin Jacob
2023-06-22 17:33       ` Thomas Monjalon
2023-06-20  6:45 ` [PATCH 1/2] test: add graph tests David Marchand
2023-06-20  6:50 ` Jerin Jacob
2023-06-20  6:56   ` David Marchand
2023-06-20 10:32     ` Kevin Traynor
2023-06-20 11:52       ` David Marchand
2023-06-20 13:06         ` Kevin Traynor

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