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
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
| 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
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. In particular, using SGI's Irix 6, the tests
18will fail if TESTDIR is an XFS filesystem (which /tmp often is);
19you'll want to set TESTDIR to a non-XFS filesystem.
| 17before running them.
|
20
21You will probably need GNU expr, which is part of the GNU sh-utils
| 18
19You will probably need GNU expr, which is part of the GNU sh-utils
|
22package (this is just for running the tests; CVS itself doesn't use
23expr).
| 20package. You may also need sort from the GNU textutils; Solaris
21in particular has been reported to have a sort program which does not
22behave the way that the testsuite expects (with Solaris, lines
23starting with tabs sort before blank lines). These programs are just
24for running the tests; CVS itself doesn't require expr or sort.
|
24
25If there is some unexpected output, that is a failure which can be
26somewhat hard to track down. Finding out which test is producing the
27output is not always easy. The newer tests (that is, ones using
28dotest*) will not have this problem, but there are many old tests
29which have not been converted.
30
31If running the tests produces the output "FAIL:" followed by the name
--- 114 unchanged lines hidden --- | 25
26If there is some unexpected output, that is a failure which can be
27somewhat hard to track down. Finding out which test is producing the
28output is not always easy. The newer tests (that is, ones using
29dotest*) will not have this problem, but there are many old tests
30which have not been converted.
31
32If running the tests produces the output "FAIL:" followed by the name
--- 114 unchanged lines hidden --- |