From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 831] Investigate unreferenced unit tests
Date: Wed, 20 Oct 2021 19:04:50 +0000 [thread overview]
Message-ID: <bug-831-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=831
Bug ID: 831
Summary: Investigate unreferenced unit tests
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: david.marchand@redhat.com
Target Milestone: ---
We currently have a lot of unit tests that are not referenced in meson, which
means the CI won't call them.
It might be done on purpose.
Another possibility is my grep contains false positives.
But creating this anyway bz as a request for investigation.
$ for test in $(git grep -h REGISTER_TEST_COMMAND app/test/ :^app/test/test.h |
sed -e 's/REGISTER_TEST_COMMAND(\(.*\),.*$/\1/'); do git grep -qw $test
app/test/meson.build || echo $test; done | sort
alarm_autotest
bitmap_test
bpf_autotest
cfgfile_autotest
cryptodev_bcmfs_autotest
cryptodev_caam_jr_autotest
cryptodev_ccp_autotest
cryptodev_cn10k_asym_autotest
cryptodev_cn9k_asym_autotest
cryptodev_cpu_aesni_gcm_autotest
cryptodev_cpu_aesni_mb_autotest
cryptodev_dpaa2_sec_raw_api_autotest
cryptodev_dpaa_sec_raw_api_autotest
cryptodev_mlx5_autotest
cryptodev_nitrox_autotest
cryptodev_octeontx2_asym_autotest
cryptodev_octeontx_asym_autotest
cryptodev_octeontx_autotest
cryptodev_qat_asym_autotest
cryptodev_qat_raw_api_autotest
cryptodev_virtio_autotest
eal_flags_autotest
event_crypto_adapter_autotest
eventdev_selftest_cn10k
eventdev_selftest_cn9k
eventdev_selftest_dlb2
eventdev_selftest_dpaa2
eventdev_selftest_octeontx2
event_eth_rx_adapter_autotest
event_eth_rx_intr_adapter_autotest
event_timer_adapter_test
external_mem_autotest
graph_autotest
graph_perf_autotest
ipsec_sad_autotest
node_list_dump
power_caps_autotest
resource_autotest
ring_stress_autotest
rwlock_autotest
timer_secondary_autotest
trace_dump
trace_metadata_dump
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2021-10-20 19:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-831-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.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).