NetBSD/tests
skrll 4bb9965c48 Sprinkle "-static" when using "-pg" as profiling only works with static and
the gcc specs are currently broken.

PR/56876: hppa: "cc -pg" fails with "undefined reference to `mprotect'"
2022-06-12 08:55:36 +00:00
..
bin tests/dd: add more test cases for swapping bytes 2022-05-24 21:42:37 +00:00
crypto PR 56875: Bump timeout for the bignumber test to 2h, as suggested 2022-06-10 05:59:12 +00:00
dev fix various typos in comments, documentation and messages. 2022-05-31 08:43:13 +00:00
fs build system: Revert all the recent additions of MK[...] knobs that 2022-06-06 10:56:27 +00:00
games
include
ipf s/endianess/endianness/ 2021-11-10 17:19:29 +00:00
kernel fix various typos in comment, documentation and log messages. 2022-05-24 20:50:17 +00:00
lib There are two hard problems in computer science cache invalidation, naming 2022-06-09 17:39:21 +00:00
libexec Trailing whitespace 2022-01-14 07:34:07 +00:00
modules
net Add tests for MTU of lagg(4) 2022-03-31 03:26:33 +00:00
rump fix various typos in comments, docs and log messages. 2022-05-24 06:27:59 +00:00
sbin Delete trailing whitespace 2021-10-30 13:50:12 +00:00
share
sys Mark randomly failing test cases as expected failures with a reference 2022-02-26 16:21:59 +00:00
usr.bin Sprinkle "-static" when using "-pg" as profiling only works with static and 2022-06-12 08:55:36 +00:00
usr.sbin fix warnings 2021-09-01 06:12:50 +00:00
Makefile
Makefile.inc
README
h_macros.h

README

$NetBSD: README,v 1.4 2012/05/18 15:36:21 jruoho Exp $

When adding new tests, please try to follow the following conventions.

1. For library routines, including system calls, the directory structure of
   the tests should follow the directory structure of the real source tree.
   For instance, interfaces available via the C library should follow:

	src/lib/libc/gen -> src/tests/lib/libc/gen
	src/lib/libc/sys -> src/tests/lib/libc/sys
	...

2. Equivalently, all tests for userland utilities should try to follow their
   location in the source tree. If this can not be satisfied, the tests for
   a utility should be located under the directory to which the utility is
   installed. Thus, a test for env(1) should go to src/tests/usr.bin/env.
   Likewise, a test for tcpdump(8) should be in src/tests/usr.sbin/tcpdump,
   even though the source code for the program is located under src/external.

3. Otherwise use your own discretion.