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