Aren
/
NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
NetBSD/tests
History
riastradh ddb0a7e7a7 swab(3): Rewrite this to be understandable. 
And make the tests work, and exercise all lengths up to 100.

Evidently the previous definition, presumably tightly optimized for
1980s-era compilers and CPUs, was too hard to understand, because it
was incorrectly tested for two decades and broken for years.

PR lib/57141

XXX pullup-8
XXX pullup-9
XXX pullup-10
 		2022-12-28 15:34:19 +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 Avoid explicitly naming the raw part device with a partition letter - use 2022-11-30 17:49:59 +00:00
fs Avoid explicitly naming the raw part device with a partition letter - use 2022-11-30 17:49:59 +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 swab(3): Rewrite this to be understandable. 2022-12-28 15:34:19 +00:00
libexec sort; it is the same list as in h_ifunc_static.c; perhaps it should be 2022-06-21 16:24:37 +00:00
modules requires pmap_private.h now. 2022-08-21 14:06:42 +00:00
net tests: fix Makefile and lists for MKRUMP=no 2022-12-01 04:24:37 +00:00
rump fix various typos in comments, docs and log messages. 2022-05-24 06:27:59 +00:00
sbin Simplify: avoid use of the explicit raw partition, MAKDEV does 2022-11-30 07:20:36 +00:00
share
…
sys s/fucntion/function/ in comments. 2022-07-26 19:49:32 +00:00
usr.bin tests/lint: add more examples for 'extra bits set to 0' 2022-10-15 21:19:15 +00:00
usr.sbin fix warnings 2021-09-01 06:12:50 +00:00
Makefile
…
Makefile.inc Allow to set sanitizer flags for the rump build from the 2021-07-07 11:51:45 +00:00
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.