test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Liu, Yong" <yong.liu@intel.com>
To: Ravi Kerur <rkerur@gmail.com>
Cc: "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] Clarifications on setting up DUT
Date: Fri, 23 Jan 2015 14:18:44 +0000	[thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E10D52FAE@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <CAFb4SLALHJN2MbH+eBUN_DuMAg1UnvaH4M-f07WTg0Ti0i4KcA@mail.gmail.com>

Hi Ravi,
Your patch has been applied in DTS. Thanks a lot.

And we just sent out one patch set which support manually configure DUT ports.
We have done some basic tests on it and I think it can be helpful on your first question.

We have planned to support DUT and Tester use the same platform soon. This will further reduce the requirements of running DTS.

Again, thanks for your inputJ

From: Ravi Kerur [mailto:rkerur@gmail.com]
Sent: Tuesday, January 20, 2015 2:00 AM
To: Liu, Yong
Cc: dts@dpdk.org
Subject: Re: [dts] Clarifications on setting up DUT

Hi Yong,
Thanks for the inputs, inline <rk>

On Mon, Jan 19, 2015 at 4:43 AM, Liu, Yong <yong.liu@intel.com<mailto:yong.liu@intel.com>> wrote:
Hi Ravi,
DTS can support i218 and i218 chipsets by add codename in setting.py and restore function in crb.py.

For question 1, you can get system requirements from DTS getting started guide. Just enter folder doc/dts_gsg and then "make html" will generate it.
Now ssh session is the only way for DTS to communicate with DUT and Tester. Restore interface function will re-insmod all nic in configuration file.
We will support specified nic in near future.

<rk> I have made changes and done some basic testing which includes "1" port only. Getting more than 2 ports is a bit taxing to me as I am an individual  contributor and wanted to find a way to test with what I had. I have made additional changes esp. handling cases to avoid error messages seen in "dts.log" . Do you want me to send a patch to you along with support added for I217 and i218?

For question 2, the garbage message show that DTS not strip color. Here is one quick fix for it.

diff --git a/framework/crb.py b/framework/crb.py
index aca62c1..e5224c8 100644
--- a/framework/crb.py
+++ b/framework/crb.py
@@ -226,7 +226,7 @@ class Crb(object):
         """
         Get interface name of specified pci device on linux.
         """
-        command = 'ls /sys/bus/pci/devices/0000:%s:%s/net' % (bus_id, devfun_id)
+        command = 'ls --color=never /sys/bus/pci/devices/0000:%s:%s/net' % (bus_id, devfun_id)
         return self.send_expect(command, '# ')

<rk> I will apply this patch, test it and let you know.

     def get_interface_name_freebsd(self, bus_id, devfun_id):

For question 3, DTS not scan ports normally, so you can try after fix issue 2.

<rk> Issue here was more delay needed for I217 ports to acquire v6 addresses after link up. If you are ok I can send a patch for this.
Thanks,
Ravi


> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org<mailto:dts-bounces@dpdk.org>] On Behalf Of Ravi Kerur
> Sent: Saturday, January 17, 2015 5:09 AM
> To: dts@dpdk.org<mailto:dts@dpdk.org>
> Subject: [dts] Clarifications on setting up DUT
>
> DTS team,
>
> I am making changes to DTS to support i217, i218 chipsets to DTS and I
> have couple of questions
>
> 1. Any README on system pre-requisites? Can I run DTS natively on DUT
> without any SSH?
>
>  I have I217 and 82540EM NICs in a system running Ubuntu. I would like to
> use both NIC's for testing. If I use regular method of SSH, I will loose
> one NIC hence the question.
>
> 2. When I run DTS, for some of the commands I am getting garbage output.
> The problem is seen on 2 Ubuntu systems. When I run those commands
> manually commands work fine for e.g.
>
> *16/01/2015 12:58:00       DTS_TESTER_CMD: ls
> /sys/bus/pci/devices/0000:00:19.0/net*
>
> *16/01/2015 12:58:00    DTS_TESTER_OUTPUT: ^[[0m^[[01;34meth0^[[0m*
>
> *16/01/2015 12:58:00       DTS_TESTER_CMD: Tester: [000:00:19.0 8086:15a1]
> ^[[0m^[[01;34meth0^[[0m*
>
> *16/01/2015 12:58:00       DTS_TESTER_CMD: cat
> /sys/bus/pci/devices/0000:00:19.0/net/^[[0m^[[01;34meth0^[[0m/address*
>
> *16/01/2015 12:58:00    DTS_TESTER_OUTPUT: cat:
> /sys/bus/pci/devices/0000:00:19.0/net/m1: No such file or directory^M*
>
> *-bash: 34meth0m/address: No such file or directory*
>
> *16/01/2015 12:58:00       DTS_TESTER_CMD: ls
> /sys/bus/pci/devices/0000:04:02.0/net*
>
> *16/01/2015 12:58:00    DTS_TESTER_OUTPUT: ^[[0m^[[01;34meth1^[[0m*
>
> *16/01/2015 12:58:00       DTS_TESTER_CMD: Tester: [000:04:02.0 8086:100e]
> ^[[0m^[[01;34meth1^[[0m*
>
> *16/01/2015 12:58:00       DTS_TESTER_CMD: cat
> /sys/bus/pci/devices/0000:04:02.0/net/^[[0m^[[01;34meth1^[[0m/address*
>
>
> 3. Tests start failing with following msgs even though I217 NIC is
> recognized.
>
> *Traceback (most recent call last):*
>
> *  File "/home/rkerur/dpdk-dts/dts/framework/dts.py", line 527, in
> execute_test_setup_all*
>
> *    test_case.set_up_all()*
>
> *  File "../tests/TestSuite_whitelist.py", line 61, in set_up_all*
>
> *    self.verify(len(self.dutPorts) >= 1, "Insufficient ports")*
>
> *  File "/home/rkerur/dpdk-dts/dts/framework/test_case.py", line 62, in
> verify*
>
> *    raise VerifyFailure(description)*
>
> *VerifyFailure: 'Insufficient ports'*
>
>
>
> *16/01/2015 12:58:23                 INFO:*
>
> *TEST SUITE ENDED: TestWhitelist*
>
>
> Thanks,
>
> Ravi

  reply	other threads:[~2015-01-23 14:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-19 12:43 Liu, Yong
2015-01-19 15:17 ` Thomas Monjalon
2015-01-19 18:00 ` Ravi Kerur
2015-01-23 14:18   ` Liu, Yong [this message]
2015-01-24  0:58     ` Ravi Kerur
2015-01-25  0:45       ` Liu, Yong
2015-01-26 21:20         ` Ravi Kerur
2015-01-27  3:23   ` Qiu, Michael
  -- strict thread matches above, loose matches on Subject: below --
2015-01-16 21:09 Ravi Kerur
2015-01-19  1:19 ` Qiu, Michael
2015-01-19 19:07   ` Ravi Kerur
2015-01-22 16:43     ` Ravi Kerur

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=86228AFD5BCD8E4EBFD2B90117B5E81E10D52FAE@SHSMSX103.ccr.corp.intel.com \
    --to=yong.liu@intel.com \
    --cc=dts@dpdk.org \
    --cc=rkerur@gmail.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).