linux/tools/testing
Petr Machata 8ff2d7abfb selftests: forwarding: Add a test for testing lib.sh functionality
Rerunning various scenarios to make sure lib.sh changes do not impact the
observable behavior is no fun. Add a selftest at least for the bare basics
-- the mechanics of setting RET, retmsg, and EXIT_STATUS.

Since the selftest itself uses lib.sh, it would be possible to break lib.sh
in such a way that invalidates result of the selftest. Since the metatest
only uses the bare basics (just pass/fail), hopefully such fundamental
breakages would be noticed.

Signed-off-by: Petr Machata <petrm@nvidia.com>
Link: https://lore.kernel.org/r/6d25cedbf2d4b83614944809a34fe023fbe8db38.1711464583.git.petrm@nvidia.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
2024-03-28 18:03:43 -07:00
..
crypto/chacha20-s390
cxl cxl/test: Add support for qos_class checking 2024-02-16 23:20:34 -08:00
fault-injection
ktest ktest: force $buildonly = 1 for 'make_warnings_file' test type 2024-03-15 12:36:19 -04:00
kunit wireless fixes for v6.9-rc2 2024-03-27 15:39:18 -07:00
memblock mm, treewide: rename MAX_ORDER to MAX_PAGE_ORDER 2024-01-08 15:27:15 -08:00
nvdimm tools/testing/nvdimm: Disable "missing prototypes / declarations" warnings 2024-01-22 10:41:59 -08:00
radix-tree maple_tree: fix warning comparing pointer to 0 2023-12-20 14:48:12 -08:00
scatterlist
selftests selftests: forwarding: Add a test for testing lib.sh functionality 2024-03-28 18:03:43 -07:00
vsock vsock/test: print type for SOCK_SEQPACKET 2024-01-25 16:39:21 -08:00