All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 205] make test fails with DPDK 19.02 (KeyError: 'Command')
Date: Mon, 11 Feb 2019 17:58:47 +0000	[thread overview]
Message-ID: <bug-205-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=205

            Bug ID: 205
           Summary: make test fails with DPDK 19.02 (KeyError: 'Command')
           Product: DPDK
           Version: 19.02
          Hardware: x86
                OS: Linux
            Status: CONFIRMED
          Severity: normal
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: ramirose@gmail.com
  Target Milestone: ---

With DPDK 19.02 release, When running: 

make config T=x86_64-native-linuxapp-gcc
make
make test
I consistently get the following error message:
...

 INSTALL-MAP test.map
/work/src/dpdk-19.02/build/app/test -c f -n 4
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'
make[1]: *** [/work/src/dpdk-19.02/mk/rte.sdktest.mk:49: test] Error 1
make: *** [/work/src/dpdk-19.02/mk/rte.sdkroot.mk:73: test] Error 2
...

Regards,
Rami Rosen

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2019-02-11 17:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-11 17:58 bugzilla [this message]
2019-03-09 11:32 ` [Bug 205] make test fails with DPDK 19.02 (KeyError: 'Command') bugzilla

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=bug-205-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.