test suite reviews and discussions
 help / color / mirror / Atom feed
From: Sandeep Sandy <sandy3589@gmail.com>
To: dts@dpdk.org
Subject: [dts] Failing to parse configuration file
Date: Wed, 31 May 2017 11:21:01 +0530	[thread overview]
Message-ID: <CAFMhpyDO7tgOUQ32PDRd66hc_=8v8pdjoZa5o+ZV8otixYdjyA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]

Hi All,

I am a naive user, The* following error is encountered* on triggering the
test suite.
kindly help me, am i missing something ?

--------------------------------------------------
Traceback (most recent call last):
  File "./main.py", line 159, in <module>
    args.debug, args.debugcase, args.commands)
  File "/root/sandeep/DPDK/dts/framework/dts.py", line 481, in run_all
    raise ConfigParseException(config_file)
exception.ConfigParseException: Faile to parse config file [execution.cfg]
------------------------------------------------------

*snap of execution.cfg file:*
-----------------------------------------------------
[root@hobbes dts]# cat executions/execution.cfg
[Execution1]
crbs=10.193.186.216
drivername=igb_uio
test_suites=cmdline,hello_world,multiprocess,timer
targets=x86_64-native-linuxapp-gcc
parameters=nic_type=cfg:func=true

[Execution2]
crbs=10.193.186.214
drivername=igb_uio
test_suites=l2fwd,l3fwd,pmd
targets=x86_64-native-linuxapp-gcc
parameters=nic_type=niantic:perf=true
-------------------------------------------------------------


*change set:*------------------------------------------
commit 924c30b603b61aa99f9a452a3220b41a87c2b4d7
Author: xu,huilong <huilongx.xu@intel.com>
Date:   Tue May 23 14:31:03 2017 +0800

Thanks
Sandeep

[-- Attachment #2: Type: text/html, Size: 1640 bytes --]

                 reply	other threads:[~2017-05-31  5:51 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='CAFMhpyDO7tgOUQ32PDRd66hc_=8v8pdjoZa5o+ZV8otixYdjyA@mail.gmail.com' \
    --to=sandy3589@gmail.com \
    --cc=dts@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).