DPDK patches and discussions
 help / color / mirror / Atom feed
From: luca.boccassi@gmail.com
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] autotest: disable lcores_autotest on ppc
Date: Tue, 20 Apr 2021 12:45:08 +0100	[thread overview]
Message-ID: <20210420114508.397249-1-luca.boccassi@gmail.com> (raw)

From: Luca Boccassi <luca.boccassi@microsoft.com>

This test consistently times out on ppc64 builds. Disable it.

Cc: stable@dpdk.org

Signed-off-by: Luca Boccassi <luca.boccassi@microsoft.com>
---
It just times out, nothing useful in the verbose logs. Eg:

https://ci.debian.net/data/autopkgtest/unstable/ppc64el/d/dpdk/11755163/log.gz

 app/test/meson.build | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/app/test/meson.build b/app/test/meson.build
index bd50818f82..803a87dd4e 100644
--- a/app/test/meson.build
+++ b/app/test/meson.build
@@ -215,7 +215,6 @@ fast_tests = [
         ['hash_autotest', true],
         ['interrupt_autotest', true],
         ['ipfrag_autotest', false],
-        ['lcores_autotest', true],
         ['logs_autotest', true],
         ['lpm_autotest', true],
         ['lpm6_autotest', true],
@@ -422,6 +421,11 @@ if dpdk_conf.has('RTE_CRYPTO_SCHEDULER')
 	test_deps += 'crypto_scheduler'
 endif
 
+# This test consistently times out on ppc64
+if arch_subdir != 'ppc'
+	fast_tests += [['lcores_autotest', true]]
+endif
+
 foreach d:test_deps
 	def_lib = get_option('default_library')
 	test_dep_objs += get_variable(def_lib + '_rte_' + d)
-- 
2.29.2


             reply	other threads:[~2021-04-20 11:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20 11:45 luca.boccassi [this message]
2021-04-21 15:06 ` Thomas Monjalon
2021-04-22 10:26   ` Luca Boccassi
2021-04-22 11:01     ` Thomas Monjalon
2021-04-22 12:36       ` Luca Boccassi
2021-04-22 12:43         ` Thomas Monjalon
2021-04-22 13:45           ` Luca Boccassi
2021-04-27 17:38             ` David Christensen
2021-04-27 18:14 ` David Christensen
2021-04-28 19:36 ` David Christensen

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=20210420114508.397249-1-luca.boccassi@gmail.com \
    --to=luca.boccassi@gmail.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).