1To run the tests:
2
3 $ make check
4
5Note that if your /bin/sh doesn't support shell functions, you'll
6have to try something like this, where "/bin/sh5" is replaced by the
7pathname of a shell which handles normal shell functions:
8
9 $ make SHELL=/bin/sh5 check
10
| 1To run the tests:
2
3 $ make check
4
5Note that if your /bin/sh doesn't support shell functions, you'll
6have to try something like this, where "/bin/sh5" is replaced by the
7pathname of a shell which handles normal shell functions:
8
9 $ make SHELL=/bin/sh5 check
10
|
| 11Also note that you must be logged in as a regular user, not root.
12
|
11WARNING: This test can take quite a while to run, esp. if your
12disks are slow or over-loaded.
13
14The tests work in /tmp/cvs-sanity (which the tests create) by default.
15If for some reason you want them to work in a different directory, you
16can set the TESTDIR environment variable to the desired location
17before running them.
18
| 13WARNING: This test can take quite a while to run, esp. if your
14disks are slow or over-loaded.
15
16The tests work in /tmp/cvs-sanity (which the tests create) by default.
17If for some reason you want them to work in a different directory, you
18can set the TESTDIR environment variable to the desired location
19before running them.
20
|
19You will probably need GNU expr, which is part of the GNU sh-utils
20package. This is just for running the tests; CVS itself doesn't
21require expr.
| 21The tests use a number of tools (awk, expr, id, tr, etc.) that are not
22required for running CVS itself. In most cases, the standard vendor-
23supplied versions of these tools work just fine, but there are some
24exceptions -- expr in particular is heavily used and many vendor
25versions are deficient in one way or another. Note that some vendors
26provide multiple versions of tools (typically an ancient, traditional
27version and a new, standards-conforming version), so you may already
28have a usable version even if the default version isn't. If you don't
29have a suitable tool, you can probably get one from the GNU Project (see
30http://www.gnu.org). expr and id are both part of the GNU shellutils
31package, tr is part of the GNU textutils package, and awk is part of the
32GNU gawk package. The test script tries to verify that the tools exist
33and are usable; if not, it tries to find the GNU versions and use them
34instead. If it can't find the GNU versions either, it will print an
35error message and, depending on the severity of the deficiency, it may
36exit.
|
22
| 37
|
23With CVS 1.10 people also had trouble with the Solaris sort program
24not behaving the way that the testsuite expects (with Solaris, lines
25starting with tabs sort before blank lines).
26
| |
27If there is some unexpected output, that is a failure which can be
28somewhat hard to track down. Finding out which test is producing the
29output is not always easy. The newer tests (that is, ones using
30dotest*) will not have this problem, but there are many old tests
31which have not been converted.
32
33If running the tests produces the output "FAIL:" followed by the name
34of the test that failed, then the details on the failure are in the
--- 118 unchanged lines hidden --- | 38If there is some unexpected output, that is a failure which can be
39somewhat hard to track down. Finding out which test is producing the
40output is not always easy. The newer tests (that is, ones using
41dotest*) will not have this problem, but there are many old tests
42which have not been converted.
43
44If running the tests produces the output "FAIL:" followed by the name
45of the test that failed, then the details on the failure are in the
--- 118 unchanged lines hidden --- |