linux/tools/testing
Thomas Weißschuh a782d45c86 selftests/nolibc: stop testing constructor order
The execution order of constructors in undefined and depends on the
toolchain.  While recent toolchains seems to have a stable order, it
doesn't work for older ones and may also change at any time.

Stop validating the order and instead only validate that all
constructors are executed.

Reported-by: Willy Tarreau <w@1wt.eu>
Closes: https://lore.kernel.org/lkml/20250301110735.GA18621@1wt.eu/
Link: https://lore.kernel.org/r/20250306-nolibc-constructor-order-v1-1-68fd161cc5ec@weissschuh.net
Acked-by: Willy Tarreau <w@1wt.eu>
Signed-off-by: Thomas Weißschuh <linux@weissschuh.net>
2025-03-07 07:34:12 +01:00
..
crypto/chacha20-s390
cxl cxl changes for v6.14 2025-01-29 11:23:22 -08:00
fault-injection
ktest ktest.pl: Fix typo "accesing" 2024-12-18 16:51:50 -05:00
kunit The various patchsets are summarized below. Plus of course many 2025-01-26 18:36:23 -08:00
memblock
nvdimm Get rid of 'remove_new' relic from platform driver struct 2024-12-01 15:12:43 -08:00
radix-tree Xarray: do not return sibling entries from xas_find_marked() 2025-01-24 22:47:27 -08:00
scatterlist
selftests selftests/nolibc: stop testing constructor order 2025-03-07 07:34:12 +01:00
shared tools: fix atomic_set() definition to set the value correctly 2025-01-12 19:03:35 -08:00
vma tools: add VM_WARN_ON_VMG definition 2025-01-25 20:22:46 -08:00
vsock vsock/test: Add test for connect() retries 2025-01-29 18:50:37 -08:00