NetBSD

History

gson d34c9aa571 Add -lrumpnet_netinet6 to the rump_server invocation, to stop rpc.rquotad from printing the error message "rpc.rquotad: _svc_tli_create: could not open connection for udp6: Address family not supported by protocol family". The error message currently ends up in /dev/null because it is printed to stderr after calling daemon() with noclose=0, but if the daemonization is moved to a later point to fix the race condition of PR misc/48282, it will actually appear on stderr and break the test, which is expecting stderr to be empty.		2014-03-13 12:45:14 +00:00
..
bin	Adjust default column test to the changed ps -s output.	2014-01-16 04:16:32 +00:00
crypto	Sprinkle in some UNCONST()	2014-01-19 13:40:59 +00:00
dev	The sh api calls it atf_expect_fail, while the c api calls it	2013-04-14 16:07:46 +00:00
fs	Add -lrumpnet_netinet6 to the rump_server invocation, to stop	2014-03-13 12:45:14 +00:00
games
include	Use compiler builtins instead of atf_arch and atf_machine.	2014-02-09 21:26:07 +00:00
ipf	Mark two more test case as only failing for BE	2013-05-16 07:43:02 +00:00
kernel	Make cleanup routines actually work.	2014-03-02 20:13:12 +00:00
lib	Avoid double constants out of range	2014-03-12 21:40:07 +00:00
libexec	ARM now works with integrated-as.	2014-02-14 20:33:32 +00:00
modules
net	ldpd wants inet6	2014-01-03 13:14:50 +00:00
rump	Move the "is arch capable of loading native kernel modules into	2014-03-10 22:38:53 +00:00
sbin	We now expect this test to succeed	2014-01-05 12:59:03 +00:00
share
sys
usr.bin	Pass the correct buffer size.	2014-02-06 14:57:16 +00:00
usr.sbin	adjust output now that we don't output size info for links and directories	2013-10-20 17:27:37 +00:00
h_macros.h	PR/47826: Garrett Cooper: Add <sys/types.h>. Really I am tempted to remove	2013-05-17 15:42:09 +00:00
Makefile
Makefile.inc
README

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.