DPDK patches and discussions
 help / color / mirror / Atom feed
From: Rami Rosen <ramirose@gmail.com>
To: dev@dpdk.org
Cc: naga.sureshx.somarowthu@intel.com, reshma.pattan@intel.com,
	Rami Rosen <ramirose@gmail.com>
Subject: [dpdk-dev] [PATCH] test: fix broken "make test"
Date: Mon, 11 Feb 2019 20:38:59 +0200	[thread overview]
Message-ID: <20190211183859.12314-1-ramirose@gmail.com> (raw)

This patch fixes a broken build; when running
make test
we get the following error:
...
Traceback (most recent call last):
  File "/work/src/dpdk-19.02/test/test/autotest.py", line 49, in <module>
    num_fails = runner.run_all_tests()
  File "/work/src/dpdk-19.02/test/test/autotest_runner.py", line 345, in
run_all_tests
    self.parallel_tests)
  File "/work/src/dpdk-19.02/test/test/autotest_runner.py", line 264, in
__filter_test
    test_cmd = test["Command"]
KeyError: 'Command'
...
The reason is that the pdump autotest entry uses "Comamnd"
instead of "Command"; this patch fixes it.

Bugzilla ID: 205
Fixes: 086eb64db39e ("test/pdump: add unit test for pdump library")
Signed-off-by: Rami Rosen <ramirose@gmail.com>
---
 test/test/autotest_data.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/test/test/autotest_data.py b/test/test/autotest_data.py
index 948a625b5..5f87bb94d 100644
--- a/test/test/autotest_data.py
+++ b/test/test/autotest_data.py
@@ -508,7 +508,7 @@
     },
     {
         "Name":    "Pdump autotest",
-        "Comamnd": "pdump_autotest",
+        "Command": "pdump_autotest",
         "Func":    default_autotest,
         "Report":  None,
     },
-- 
2.19.2

             reply	other threads:[~2019-02-11 18:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-11 18:38 Rami Rosen [this message]
2019-02-12  9:36 ` Ferruh Yigit
2019-02-12  9:59   ` David Marchand
2019-02-12 11:24   ` Thomas Monjalon
2019-02-12 17:52     ` Ferruh Yigit

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=20190211183859.12314-1-ramirose@gmail.com \
    --to=ramirose@gmail.com \
    --cc=dev@dpdk.org \
    --cc=naga.sureshx.somarowthu@intel.com \
    --cc=reshma.pattan@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).