Hi Lijuan,
Thanks for the quick response, your replies clarifies everything now!

And Indeed:
git checkout next
Switched to branch 'next'

git grep nic_single_core_perf
doc/dts_gsg/trex.rst:This is supported for the ``nic_single_core_per
framework/etgen.py:        This function is set only for function se
framework/etgen.py:        Note that this function is only set for t
test_plans/nic_single_core_perf_test_plan.rst:    1) nic_single_core
test_plans/nic_single_core_perf_test_plan.rst:    3) nic_single_core
tests/TestSuite_nic_single_core_perf.py:    def test_nic_single_core

Regards,
Rami Rosen



On Tue, Jan 8, 2019 at 9:06 AM Tu, Lijuan <lijuan.tu@intel.com> wrote:

> Hi Rami,
>
>
>
> nic_single_core_perf_test is in the next branch of dts, so it can’t be
> found in the master branch.
>
> Since next branch is to rework packet generator module to support a
> software packet generator called TREX.
>
> A software packet generator is easily to set up with little resources
> comparing with hardware packet generator, IXIA.
>
>
>
>
>
>
>
> *From:* ci [mailto:ci-bounces@dpdk.org] *On Behalf Of *Rami Rosen
> *Sent:* Tuesday, January 8, 2019 2:40 PM
> *To:* Jeremy Plsek <jplsek@iol.unh.edu>
> *Cc:* ci@dpdk.org
> *Subject:* Re: [dpdk-ci] Question about performance test
>
>
>
> Hi Jeremy,
>
> >At the moment, we only run performance tests. Specifically the
> nic_single_core_perf_test from the DPDK Test Suite
>
>
>
> I had looked at the latest DTS repo from today:
>
>
>
> git grep nic_single_core_perf_test
>
> gives nothing.
>
>
>
> Can you be more specific about exactly which *.py module from under
> "tests" folder is used ?
>
>
>
> Regards,
>
> Rami Rosen
>
>
>
>
>


-- 
regards,
Rami Rosen