DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: <dev@dpdk.org>
Cc: Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
	Olivier Matz <olivier.matz@6wind.com>,
	Fan Zhang <fanzhang.oss@gmail.com>,
	Ashish Gupta <ashish.gupta@marvell.com>,
	Akhil Goyal <gakhil@marvell.com>,
	"Abhinandan Gujjar" <abhinandan.gujjar@intel.com>,
	Naga Harish K S V <s.v.naga.harish.k@intel.com>,
	Erik Gabriel Carrillo <erik.g.carrillo@intel.com>,
	Jerin Jacob <jerinj@marvell.com>,
	"Anatoly Burakov" <anatoly.burakov@intel.com>,
	Kiran Kumar K <kirankumark@marvell.com>,
	Nithin Dabilpuram <ndabilpuram@marvell.com>,
	Zhirun Yan <zhirun.yan@intel.com>,
	Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
	Vladimir Medvedkin <vladimir.medvedkin@intel.com>,
	Reshma Pattan <reshma.pattan@intel.com>,
	Chas Williams <chas3@att.com>,
	"Min Hu (Connor)" <humin29@huawei.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	"Anoob Joseph" <anoobj@marvell.com>,
	Volodymyr Fialko <vfialko@marvell.com>,
	"Bruce Richardson" <bruce.richardson@intel.com>,
	David Hunt <david.hunt@intel.com>,
	Sachin Saxena <sachin.saxena@nxp.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Subject: Unit tests not defined in any test suite
Date: Thu, 14 Sep 2023 17:07:28 +0100	[thread overview]
Message-ID: <ZQMvwG1mcZql3msN@bricha3-MOBL.ger.corp.intel.com> (raw)

Hi all,

As part of the recent rework of the build of our unit test binary
(dpdk-test), the individual autotests were updated in the source code to
specify the test suite they belong to. The replacement of the
registration macro was done automatically using the existing suite lists
in the meson.build file, but following the replacement, it appears that
there are quite a number of test cases which are not in any test suite -
and as such as not being run automatically for patches in the IOL test
lab.

Below is a list of these test cases, and the files each is defined in.
We should endeavour to ensure each test case is in a suite. Currently we
have 3 suites - fast-test, perf-test, and driver-test, but more suites
can be added as necessary.

I've attempted to automatically identify the maintainers of the various
tests using "get-maintainers" script - hence the list of those on CC. If
possible, can each of you identify what test cases you may be maintainer
for, and add them to a test suite, to help improve our test coverage.
[Apologies for any mis-identifications]

Thanks,
/Bruce

alarm_autotest (test_alarm.c)
bitratestats_autotest (test_bitratestats.c)
cfgfile_autotest (test_cfgfile.c)
cksum_perf_autotest (test_cksum_perf.c)
compressdev_autotest (test_compressdev.c)
cryptodev_scheduler_autotest (test_cryptodev.c)
cryptodev_dpaa2_sec_raw_api_autotest (test_cryptodev.c)
cryptodev_dpaa_sec_raw_api_autotest (test_cryptodev.c)
cryptodev_mlx5_autotest (test_cryptodev.c)
cryptodev_ccp_autotest (test_cryptodev.c)
cryptodev_virtio_autotest (test_cryptodev.c)
cryptodev_octeontx_autotest (test_cryptodev.c)
cryptodev_caam_jr_autotest (test_cryptodev.c)
cryptodev_nitrox_autotest (test_cryptodev.c)
cryptodev_bcmfs_autotest (test_cryptodev.c)
cryptodev_openssl_asym_autotest (test_cryptodev_asym.c)
cryptodev_octeontx_asym_autotest (test_cryptodev_asym.c)
cryptodev_cn9k_asym_autotest (test_cryptodev_asym.c)
cryptodev_cn10k_asym_autotest (test_cryptodev_asym.c)
cryptodev_crosscheck (test_cryptodev_crosscheck.c)
event_crypto_adapter_autotest (test_event_crypto_adapter.c)
event_eth_rx_adapter_autotest (test_event_eth_rx_adapter.c)
event_eth_rx_intr_adapter_autotest (test_event_eth_rx_adapter.c)
event_eth_tx_adapter_autotest (test_event_eth_tx_adapter.c)
event_timer_adapter_test (test_event_timer_adapter.c)
eventdev_selftest_sw (test_eventdev.c)
eventdev_selftest_octeontx (test_eventdev.c)
eventdev_selftest_dpaa2 (test_eventdev.c)
eventdev_selftest_dlb2 (test_eventdev.c)
eventdev_selftest_cn9k (test_eventdev.c)
eventdev_selftest_cn10k (test_eventdev.c)
external_mem_autotest (test_external_mem.c)
graph_autotest (test_graph.c)
node_list_dump (test_graph.c)
graph_perf_autotest (test_graph_perf.c)
ipsec_sad_autotest (test_ipsec_sad.c)
latencystats_autotest (test_latencystats.c)
link_bonding_autotest (test_link_bonding.c)
link_bonding_mode4_autotest (test_link_bonding_mode4.c)
link_bonding_rssconf_autotest (test_link_bonding_rssconf.c)
metrics_autotest (test_metrics.c)
pcapng_autotest (test_pcapng.c)
pdcp_autotest (test_pdcp.c)
pdump_autotest (test_pdump.c)
ring_pmd_autotest (test_pmd_ring.c)
ring_pmd_perf_autotest (test_pmd_ring_perf.c)
power_caps_autotest (test_power_cpufreq.c)
rawdev_autotest (test_rawdev.c)
red_autotest (test_red.c)
resource_autotest (test_resource.c)
ring_stress_autotest (test_ring_stress.c)
inline_macsec_autotest (test_security_inline_macsec.c)
inline_ipsec_autotest (test_security_inline_proto.c)
inline_ipsec_sg_autotest (test_security_inline_proto.c)
event_inline_ipsec_autotest (test_security_inline_proto.c)
table_autotest (test_table.c)
timer_secondary_autotest (test_timer_secondary.c)
vdev_autotest (test_vdev.c)


             reply	other threads:[~2023-09-14 16:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-14 16:07 Bruce Richardson [this message]
2023-09-15  7:55 ` David Marchand
2023-09-15  8:21   ` Bruce Richardson

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=ZQMvwG1mcZql3msN@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=abhinandan.gujjar@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=anoobj@marvell.com \
    --cc=ashish.gupta@marvell.com \
    --cc=chas3@att.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=erik.g.carrillo@intel.com \
    --cc=fanzhang.oss@gmail.com \
    --cc=gakhil@marvell.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=humin29@huawei.com \
    --cc=jerinj@marvell.com \
    --cc=kirankumark@marvell.com \
    --cc=konstantin.v.ananyev@yandex.ru \
    --cc=ndabilpuram@marvell.com \
    --cc=olivier.matz@6wind.com \
    --cc=reshma.pattan@intel.com \
    --cc=s.v.naga.harish.k@intel.com \
    --cc=sachin.saxena@nxp.com \
    --cc=stephen@networkplumber.org \
    --cc=vfialko@marvell.com \
    --cc=vladimir.medvedkin@intel.com \
    --cc=zhirun.yan@intel.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).