[dts] Clarifications on setting up DUT

[Ravi Kerur]

Hi Michael,

I got 2 systems assembled which had I217 and I218 chipsets on the
motherboard and I  was not quite satisfied with the testing I did to claim
support for these chipsets (primarily used testpmd for testing) so looked
at DTS to complement the testing I did.

More Inline <rk>

On Sun, Jan 18, 2015 at 5:19 PM, Qiu, Michael <michael.qiu at intel.com> wrote:

> On 2015/1/17 5:09, Ravi Kerur wrote:
> > 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?
>
> As I know currently not, but any patches are welcome :)
> Do you guys wants to use it in test env?
>

<rk> I want to use it for development testing.

>
> I know that it would be helpful in development, but for testing, it
> would be have a remote access to DUT.
>
> >  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.
>
> As I said, it only happens in develop mode, while for automation
> testing, it would be unacceptable to have no other NIC for control patch.
>
> Or it would be reasonable to add one serial port to control it in
> testing mode.
>
> >
> > 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.
>
> I have a patch send out maybe can solve this, but I have not checked yet
>

<rk> I will test the patch and let you know.

>
> > *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*
>
> This failure maybe because you only have one NIC port :), but two needs.
>

<rk> Issue was primarily with delay to acquire v6 address after link up.
There are some test cases in DTS for 1 port and I am testing with them
right now.

Thanks,
Ravi

>
> Thanks,
> Michael
> > *    raise VerifyFailure(description)*
> >
> > *VerifyFailure: 'Insufficient ports'*
> >
> >
> >
> > *16/01/2015 12:58:23                 INFO:*
> >
> > *TEST SUITE ENDED: TestWhitelist*
> >
> >
> > Thanks,
> >
> > Ravi
> >
>
>