patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Pattan, Reshma" <reshma.pattan@intel.com>
To: David Marchand <david.marchand@redhat.com>,
	"Rao, Nikhil" <nikhil.rao@intel.com>
Cc: dev <dev@dpdk.org>, dpdk stable <stable@dpdk.org>,
	Chas Williams <chas3@att.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>,
	"Stephen Hemminger" <stephen@networkplumber.org>
Subject: Re: [dpdk-stable] [PATCH v3] app/test: fix build when ring PMD is disabled
Date: Tue, 29 Oct 2019 09:36:00 +0000	[thread overview]
Message-ID: <3AEA2BF9852C6F48A459DA490692831F2A4E6F3D@irsmsx110.ger.corp.intel.com> (raw)
In-Reply-To: <CAJFAV8zLdXy6ny0b0VoPC+xougbfaZkQ1yHiNxiRyNvbqiZu4g@mail.gmail.com>



> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Sunday, October 27, 2019 8:48 AM
> To: Pattan, Reshma <reshma.pattan@intel.com>
> Cc: dev <dev@dpdk.org>; dpdk stable <stable@dpdk.org>; Rao, Nikhil
> <nikhil.rao@intel.com>; Chas Williams <chas3@att.com>; Richardson, Bruce
> <bruce.richardson@intel.com>; Stephen Hemminger
> <stephen@networkplumber.org>
> Subject: Re: [dpdk-stable] [PATCH v3] app/test: fix build when ring PMD is
> disabled
> 
> On Fri, Oct 25, 2019 at 5:38 PM Reshma Pattan <reshma.pattan@intel.com>
> wrote:
> >
> > 1)pdump, latency, bitrate, ring PMD and test_event_eth_tx_adapter unit
> > tests are dependent on ring PMD, so compile those tests only when ring
> > PMD is enabled else ignore.
> >
> > 2)get rid of make file error which was added by bond unit test for
> > ring PMD disabled case which is not necessary.
> >
> > Fixes: 086eb64db3 ("test/pdump: add unit test for pdump library")
> > Fixes: fdeb30fa71 ("test/bitrate: add unit tests for bitrate library")
> > Fixes: 1e3676a06e ("test/latency: add unit tests for latencystats
> > library")
> > Fixes: 46cf97e4bb ("eventdev: add test for eth Tx adapter")
> > Fixes: d23e09e0ef ("app/test: link with ring pmd when needed")
> >
> > CC: stable@dpdk.org
> > CC: Nikhil Rao <nikhil.rao@intel.com>
> > CC: Chas Williams <chas3@att.com>
> > CC: Bruce Richardson <bruce.richardson@intel.com>
> > CC: Stephen Hemminger <stephen@networkplumber.org>
> >
> > Reported-by: Stephen Hemminger <stephen@networkplumber.org>
> > Signed-off-by: Reshma Pattan <reshma.pattan@intel.com>
> > ---
> > v3: add missing test event_eth_tx_adapter_autotest.
> 
> https://travis-ci.com/ovsrobot/dpdk/jobs/249598391
> 
> 79/83 DPDK:fast-tests / event_eth_tx_adapter_autotest  FAIL     0.12 s
> (exit status 255 or signal 127 SIGinvalid)
> --- command ---
> DPDK_TEST='event_eth_tx_adapter_autotest'
> /home/travis/build/ovsrobot/dpdk/build/app/test/dpdk-test -l 0-1 --file-
> prefix=event_eth_tx_adapter_autotest
> --- stdout ---
> EAL: Probing VFIO support...
> APP: HPET is not enabled, using TSC as default timer
> RTE>>event_eth_tx_adapter_autotest
>  + ------------------------------------------------------- +  + Test Suite : tx event eth
> adapter test suite Port 0 MAC: 00 00 00 00 00 00 Port 1 MAC: 00 00 00 00 00 00
> Failed to find a valid event device, testing with event_sw0 device  + ----------------
> --------------------------------------- +  + Test Suite Summary
>  + Tests Total :        5
>  + Tests Skipped :      0
>  + Tests Executed :     0
>  + Tests Unsupported:   0
>  + Tests Passed :       0
>  + Tests Failed :       5
>  + ------------------------------------------------------- + Test Failed
> 

Is this something that Nikhil should look into this as maintainer and fix in separate patch, I am afraid this is not my area of expertise.

Thanks,
Reshma


  reply	other threads:[~2019-10-29  9:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-17  9:41 [dpdk-stable] [PATCH 1/2] app/test: fix make " Reshma Pattan
2019-10-17  9:41 ` [dpdk-stable] [PATCH 2/2] app/test: fix meson " Reshma Pattan
2019-10-17  9:51   ` [dpdk-stable] [dpdk-dev] " Bruce Richardson
2019-10-17  9:54   ` [dpdk-stable] " David Marchand
2019-10-17  9:48 ` [dpdk-stable] [PATCH 1/2] app/test: fix make " Bruce Richardson
2019-10-17 11:16 ` [dpdk-stable] [PATCH v2] app/test: fix " Reshma Pattan
2019-10-17 13:46   ` Bruce Richardson
2019-10-25  8:11   ` [dpdk-stable] [dpdk-dev] " David Marchand
2019-10-25 15:40     ` Pattan, Reshma
2019-10-25 15:38   ` [dpdk-stable] [PATCH v3] " Reshma Pattan
2019-10-27  8:47     ` David Marchand
2019-10-29  9:36       ` Pattan, Reshma [this message]
2019-10-31  7:58         ` David Marchand
2019-10-31 10:18           ` Pattan, Reshma
2019-12-09 13:38           ` Pattan, Reshma
2019-12-09 16:54             ` Ferruh Yigit
2019-12-09 18:00               ` Aaron Conole
2019-12-18 11:58     ` [dpdk-stable] [PATCH v4] " Reshma Pattan
2019-12-18 16:07       ` Bruce Richardson
2019-12-18 16:23         ` Pattan, Reshma
2019-12-23  6:53       ` [dpdk-stable] [PATCH v5] " Reshma Pattan
2020-01-19 21:50         ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon
2020-01-20  9:55           ` Rao, Nikhil
2020-01-20 17:36         ` [dpdk-stable] " Bruce Richardson
2020-02-16 18:10           ` [dpdk-stable] [dpdk-dev] " Thomas Monjalon

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=3AEA2BF9852C6F48A459DA490692831F2A4E6F3D@irsmsx110.ger.corp.intel.com \
    --to=reshma.pattan@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=chas3@att.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=nikhil.rao@intel.com \
    --cc=stable@dpdk.org \
    --cc=stephen@networkplumber.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).