#
259065 |
|
07-Dec-2013 |
gjb |
- Copy stable/10 (r259064) to releng/10.0 as part of the 10.0-RELEASE cycle. - Update __FreeBSD_version [1] - Set branch name to -RC1
[1] 10.0-CURRENT __FreeBSD_version value ended at '55', so start releng/10.0 at '100' so the branch is started with a value ending in zero.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
256281 |
|
10-Oct-2013 |
gjb |
Copy head (r256279) to stable/10 as part of the 10.0-RELEASE cycle.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation
|
#
223865 |
|
08-Jul-2011 |
jonathan |
Clarify the meaning of a test.
Rather than using err() if either of two failure conditions fires (which can produce spurious error messages), just use errx() if the one condition that really matters fires.
In practice, this single test is enough to detect the failure mode we're looking for (kqueue being inherited across fork).
Approved by: mentor (rwatson), re (Capsicum blanket) Sponsored by: Google Inc
|
#
223845 |
|
07-Jul-2011 |
jonathan |
Ensure that kqueue is not inherited across fork().
Modify the existing unit test (from libkqueue) which already exercises process events via fork() and kill(). Now, the child process simply checks that the 'kqfd' descriptor is invalid.
Some minor modifications were required to make err() work correctly. It seems that this test was imported using the output of a configure script, but config.h was not included in key places, nor was its syntax correct (need '#define HAVE_FOO 1' rather than '#define HAVE_FOO').
Finally, change main() to run the "proc" suite by default, but widened the '#if TODO' in proc.c to include the non-functioning test event_trigger().
Approved by: mentor (rwatson), re (Capsicum blanket) Sponsored by: Google Inc
|
#
200573 |
|
15-Dec-2009 |
rwatson |
Merge libkqueue test suite through r119
Submitted by: Mark Heily <mark@heily.com>
|
#
200483 |
|
13-Dec-2009 |
rwatson |
Add Mark Heily's libkqueue test suite as a general kqueue test suite to tools/regression. It tests a number of aspects of kqueue behavior, although not all currently pass (possibly bugs in the test suite?).
Submitted by: Mark Heily <mark at heily.com> Obtained from: svn://mark.heily.com/libkqueue/trunk/test (r114)
|