patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Xueming Li <xuemingl@nvidia.com>
Cc: Zhirun Yan <zhirun.yan@intel.com>,
	Luca Boccassi <bluca@debian.org>, <stable@dpdk.org>,
	<david.marchand@redhat.com>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Subject: [22.11] app/test: disable graph auto test for windows
Date: Wed, 13 Dec 2023 20:25:42 +0800	[thread overview]
Message-ID: <20231213122542.2048-1-xuemingl@nvidia.com> (raw)

To avoid windows CI failure, disable graph auto test only for windows.

Fixes: 5887a7d14dba ("test: add graph tests")
Cc: david.marchand@redhat.com
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Signed-off-by: Xueming Li <xuemingl@nvidia.com>
---
 app/test/meson.build | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/app/test/meson.build b/app/test/meson.build
index 96702c2078..23e1f9b749 100644
--- a/app/test/meson.build
+++ b/app/test/meson.build
@@ -190,7 +190,6 @@ fast_tests = [
         ['fib_autotest', true, true],
         ['fib6_autotest', true, true],
         ['func_reentrancy_autotest', false, true],
-        ['graph_autotest', true, true],
         ['hash_autotest', true, true],
         ['interrupt_autotest', true, true],
         ['ipfrag_autotest', false, true],
@@ -297,7 +296,6 @@ perf_test_names = [
         'trace_perf_autotest',
         'ipsec_perf_autotest',
         'thash_perf_autotest',
-        'graph_perf_autotest',
 ]
 
 driver_test_names = [
@@ -323,6 +321,10 @@ driver_test_names = [
 dump_test_names = []
 
 if not is_windows
+    fast_tests += 'graph_autotest'
+
+    perf_test_names += 'graph_perf_autotest'
+
     driver_test_names += [
             'cryptodev_openssl_asym_autotest',
             'eventdev_selftest_octeontx',
-- 
2.25.1


                 reply	other threads:[~2023-12-13 12:26 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=20231213122542.2048-1-xuemingl@nvidia.com \
    --to=xuemingl@nvidia.com \
    --cc=bluca@debian.org \
    --cc=david.marchand@redhat.com \
    --cc=jerinj@marvell.com \
    --cc=stable@dpdk.org \
    --cc=zhirun.yan@intel.com \
    /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).