On Thu, Aug 17, 2023 at 3:28 AM David Marchand <david.march...@redhat.com> wrote:
> It is possible to list tests from meson. > Why not simply list the existing tests and filter the non working one? > > $ meson test -C <build_dir> --suite fast-tests --list > $ meson test -C <build_dir> <explicit list> --test-args ... > > That requires no change in DPDK. > > > Thanks. I am seeing now that this is possible. So, we could easily solve this problem using this approach. Thank you David. At the same time, I do like Bruce's new RFC patch for excluding tests with env variables. It is a bit cleaner on the testing experience side (I don't have to list 100 tests in the command) and it makes clear in the logs what is being skipped which typically would be run. Making that info visible could be valuable in some cases. Ultimately, we can proceed on the Community Lab side either way. I guess the maintainers must decide whether adding in the extra complexity to the test app is justified in this case. Also, Bruce, I do see that the symlink you used is working for the case where we have to (for now) directly use the dpdk-test app. I'm sorry I didn't have that info on hand this morning during the ci meeting.
