patches for DPDK stable branches
 help / color / Atom feed
From: "Pattan, Reshma" <reshma.pattan@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"stable@dpdk.org" <stable@dpdk.org>,
	"Rao,  Nikhil" <nikhil.rao@intel.com>,
	Chas Williams <chas3@att.com>,
	"Stephen Hemminger" <stephen@networkplumber.org>
Subject: Re: [dpdk-stable] [PATCH v4] app/test: fix build when ring PMD is disabled
Date: Wed, 18 Dec 2019 16:23:18 +0000
Message-ID: <BL0PR11MB312413DE162DD508F928FBBEFF530@BL0PR11MB3124.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20191218160758.GA474@bricha3-MOBL.ger.corp.intel.com>



> -----Original Message-----
> From: Bruce Richardson <bruce.richardson@intel.com>

<snip>

> 
> >  foreach arg : fast_test_names
> > +	if (get_option('default_library') == 'shared' and
> > +		arg == 'event_eth_tx_adapter_autotest')
> > +		foreach drv:dpdk_drivers
> > +			test_args += ['-d', drv.full_path().split('.a')[0] + '.so']
> > +		endforeach
> > +	endif
> 
> Does this need to be limited to just this one test? Why not just set the test args
> outside the loop to always include all drivers if it is a shared build?
> 

I was seeing  couple of other UTs failing when I set the testargs commonly for all tests.
I am not sure about why, so enabling only for that particular UT which actually needed them.

APP: HPET is not enabled, using TSC as default timer
RTE>>alarm_autotest^M
check if the callback will be called
Callback not called
Test Failed
RTE>>

RTE>>interrupt_autotest^M
Check unknown valid interrupt full path
callback has not been called
failure occurred during checking unknown valid interrupt full path
Clearing for interrupt tests
Test Failed
RTE>>

Thanks,
Reshma
 

  reply index

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
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 [this message]
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 publically 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=BL0PR11MB312413DE162DD508F928FBBEFF530@BL0PR11MB3124.namprd11.prod.outlook.com \
    --to=reshma.pattan@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=chas3@att.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

patches for DPDK stable branches

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/stable/0 stable/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 stable stable/ http://inbox.dpdk.org/stable \
		stable@dpdk.org
	public-inbox-index stable


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.stable


AGPL code for this site: git clone https://public-inbox.org/ public-inbox