NetBSD/tests
martin cdc28dcfbd Pull up following revision(s) (requested by ozaki-r in ticket #1339):
sys/net/if.c: revision 1.458
	tests/net/if/t_ifconfig.sh: revision 1.21

Restore if_ioctl on error of ifc_destroy

Otherwise subsequence ioctls won't work.

Patch from Harold Gutch on PR kern/54434 (tweaked a bit by me)
tests: check if ifconfig (ioctl) works after a failure of ifconfig destroy

This is a test for PR kern/54434.
2019-08-19 14:27:16 +00:00
..
bin Paranoia: add a new test case testing that $(( )) results get split 2017-06-03 15:15:49 +00:00
crypto Remove MKCRYPTO option. 2017-05-21 15:28:36 +00:00
dev Remove MKCRYPTO option. 2017-05-21 15:28:36 +00:00
fs give it more time. 2017-05-24 15:29:51 +00:00
games
include Pull up following revision(s) (requested by pgoyette in ticket #296): 2017-10-02 13:21:40 +00:00
ipf
kernel Pull up following revision(s) (requested by kamil in ticket #1201): 2019-03-01 18:59:58 +00:00
lib Additionally pull up the following, requested by maya in ticket #892: 2018-07-10 15:06:25 +00:00
libexec Pull up following revision(s) (requested by joerg in ticket #253): 2017-09-01 08:43:22 +00:00
modules
net Pull up following revision(s) (requested by ozaki-r in ticket #1339): 2019-08-19 14:27:16 +00:00
rump Pull up following revision(s) (requested by ozaki-r in ticket #497): 2018-01-16 13:01:10 +00:00
sbin
share
sys
usr.bin Pull up following revision(s) (requested by martin in ticket #726): 2018-04-10 08:06:46 +00:00
usr.sbin
Makefile Remove MKCRYPTO option. 2017-05-21 15:28:36 +00:00
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.