| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Approved by: re (blanket `env')
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
using my own script to handle it. I wrote my own partially because
of all the quoting-issues involved with testing what I wanted to test,
and partially because this lets me commit one script and one data file,
instead of one-file-per-regression-test.
This suite was good enough for my initial testing (and it did help me
find a few bugs that would have otherwise been missed). I'm not sure
how well it will work in general use, but I figured I might as well
commit it. It won't *hurt* to have it available. At the worst, people
can just ignore it.
Approved by: re (blanket `env')
|
|
|
|
|
|
|
|
|
|
| |
o getsockopt(SO_ACCEPTFILTER) always returns success on listen socket
even we didn't install accept filter on the socket.
o Fix these bugs and add regression tests for them.
Submitted by: Igor Sysoev [1]
Reviewed by: alfred
MFC after: 2 weeks
|
| |
|
|
|
|
| |
because of a make bug that should be fixed.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
so that make(1) will run in an almost clean environment and enhance the
description of the test infrastructure.
Add the ability to have multiple tests carried out per test script.
Give some tests more meaningful names.
Fix the usage message from the test scripts.
Make it possible to pass several commands to the test scripts like:
'sh test.t setup run compare clean'.
|
|
|
|
|
| |
on the command line and really executes the shell instead of directly
executing the command.
|
|
|
|
|
|
| |
shell meta characters it is not passed to the shell, but the command
is executed directly (given that the line is not a shell builtin) and
that the line with a meta character is passed to the shell.
|
|
|
|
|
| |
make with another shell and set all its parameters (meta and builtins
not tested here).
|
|
|
|
| |
changing the path of a builtin shell.
|
|
|
|
| |
Update copyright.
|
|
|
|
| |
Update copyright.
|
|
|
|
| |
o -x option added.
|
|
|
|
| |
Reviewed by: sam
|
| |
|
|
|
|
| |
- enable -r option for regress target.
|
|
|
|
|
|
|
| |
- do service lookup.
- add options to use gethostbyname(3) or getipnodebyname(3) instead
of getaddrinfo(3).
- add option to do reverse lookup.
|
|\
| |
| |
| | |
which included commits to RCS files with non-trunk default branches.
|
|
|
|
| |
Obtained from: NetBSD
|
|
|
|
| |
Submitted by: Max Okumoto <okumotu@ucsd.edu> (partly, initial version)
|
| |
|
| |
|
|
|
|
|
| |
Tested by: njl
Reviewed by: silby, bde, sam (mentor)
|
| |
|
|
|
|
| |
instead of a directory that only exists on my machine.
|
| |
|
|
|
|
|
|
|
|
|
| |
Currently only performs basic tests against the library string routines,
and queries less important kernel state.
Obtained from: TrustedBSD Project
Sponsored by: SPAWAR, SPARTA
MFC after: 3 days
|
| |
|
| |
|
|
|
|
| |
the recent trouble msdosfs had.
|
| |
|
|
|
|
| |
remquo(), and remquof().
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
| |
fegetexcept().
- Add additional tests for the above.
- Output a separate success message for each of the 8 components of
this set of tests.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
intended to verify that SIGPIPE is delivered to a process writing or
sending on a socket that has been shut down for write. If available,
SO_NOSIGPIPE is also tested.
This regression test is currently passed by RELENG_4, but not by HEAD or
RELENG_5, due to a bug in the write() code for sockets. SO_NOSIGPIPE is not
present in RELENG_4, however, so is not tested there.
Reported by: Mikko Tyolajarvi <mbsd at pacbell dot net>
PR: 78478
|
| |
|
|
|
|
|
|
|
|
| |
and adjust the path in the Makefile for the upgrade_checks target.
These checks are really feature upgrade checks that should be fast
and just find out whether we need to build a new make before
proceeding with other targets like buildworld. This makes the
place free for a real regression test suite in the old place.
|
|
|
|
|
|
|
|
|
|
|
| |
http://www.ambrisko.com/doug/listio_kqueue/listio_kqueue.patch
Note: it is a good idea to run this against a physical drive to
exercise the physio fast path (ie. lio_kqueue /dev/<something safe>)
This will ensure op's counting per LIO request is correct. It is
currently broken the above patch fixes it.
Sponsored by: IronPort
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
against a disk as the argument. If you don't it will use a temp file.
The raw disk will use the kernel physio fast path method until the
max number of pending op's is reached then it will queue them. File
system op's are always queued. This is more important with LIO since
operation can get split across and accounting of op's is broken with LIO.
Note that this was broken when locking was added to kqueue (ie. 5.3)
My fix needs to be better integrated with FreeBSD.
Next is an LIO test and implementation.
Sponsored by: IronPort
|
|
|
|
|
|
|
|
|
|
|
| |
- Use fesetround() instead of fpsetround(), and add tests for
various rounding modes.
- Test that all NaNs generated are quiet.
Some of these tests won't pass until problems in vendor sources
(gdtoa and gcc) are fixed and new versions imported, but I
want to get these changes into the tree before I accidentally
blow them away again. :-(
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
tests. (Buy 10, get one free!) The separate categories were
already there; they just weren't labeled.
- Use fesetround() instead of fpsetround(), since the former is
standard and implemented on all supported architectures. Add
tests for each rounding mode.
- Add additional tests for subnormals.
Some of these tests won't pass until problems in vendor sources
(gdtoa and gcc) are fixed and new versions imported, but I
want to get these changes into the tree before I accidentally
blow them away.
|
|
|
|
|
|
| |
bind()/connect() system calls, which is intended to confirm that the
right successes and errors occur when rendezvousing via the file system
name space.
|
| |
|
|
|
|
|
|
| |
and LDLIBS to specify -ltap.
Submitted by: ru
|
|
|
|
|
| |
with calls to libtap::ok1(), and make sure the correct number of tests is
planned for, and that the exit code is correct.
|
|
|
|
|
|
|
|
|
| |
and as long as we're not compiling with IPA, gcc(1) won't optimize
the call away. The whole purpose of using memcpy(3) is to avoid
misaligned loads and stores when we need to read or write the value
in the unaligned memory location. But if gcc(1) optimizes the call
to memcpy(3) away, it will typically introduce misaligned loads and
stores. In this context that's not a good idea.
|
|
|
|
|
|
| |
in the number of tests. This way we avoid skipped tests for non-
existent memory access combinations. The number of tests dropped
from 60 to 48.
|
|
|
|
|
| |
too much about them. This prevents certain peephole optimizations
at -O that invalidate the tests.
|
|
|
|
|
|
| |
stopped pointing to the value the moment we wrote it due to the post
increment. So, grab the value for comparison out of the data structure
directly.
|