The R Project SVN R

Rev

Rev 53336 | Rev 65749 | Go to most recent revision | Show entire file | Ignore whitespace | Details | Blame | Last modification | View Log | RSS feed

Rev 53336 Rev 60900
Line 1... Line 1...
1 
There is a hierarchy of check targets:
 1 
There is a hierarchy of check targets:
2 
 
 2 
 
3 
make check
 3 
     make check
4 
 
 4 
 
5 
for all builders.  If this works one can be reasonably happy R is working
 5 
for all builders.  If this works one can be reasonably happy R is working
6 
and do `make install' (or the equivalent).
 6 
and do `make install' (or the equivalent).
7 
 
 7 
 
8 
make check-devel
 8 
    make check-devel
9 
 
 9 
 
10 
for people changing the code: this runs things like the demos and
 10 
for people changing the code: this runs things like the demos and
11 
no-segfault which might be broken by code changes, and checks on the
 11 
no-segfault which might be broken by code changes, and checks on the
12 
documentation (effectively R CMD check on each of the base packages).
 12 
documentation (effectively R CMD check on each of the base packages).
13 
 
 13 
 
14 
make check-all
 14 
    make check-all
15 
 
 15 
 
16 
runs all the checks, those in check-devel plus tests of the recommended
 16 
runs all the checks, those in check-devel plus tests of the recommended
17 
packages.
 17 
packages.
18 
 
 18 
 
19 
Note that for complete testing you will need a number of other
 19 
Note that for complete testing you will need a number of other
Line 21... Line 21...
21 
set R_LIBS (perhaps in ~/.R/check.Renviron) to include it before
 21 
set R_LIBS (perhaps in ~/.R/check.Renviron) to include it before
22 
running these tests.  For example, some of the tests on 'nlme' depend
 22 
running these tests.  For example, some of the tests on 'nlme' depend
23 
on 'Hmisc', and there are a number of cross references from help page
 23 
on 'Hmisc', and there are a number of cross references from help page
24 
to CRAN packages.
 24 
to CRAN packages.
25 
 
 25 
 
- 
 
 26 
If a check fails there will almost always be a .Rout.fail file with
- 
 
 27 
the problematic output, so looking at the tail of that file should
- 
 
 28 
help pinpoint the problem.
26 
 
 29 
 
- 
 
 30 
 
27 
		--- Historical Information ----
 31 
	---------- Historical Information -----------
28 
 
 32 
 
29 
In this directory, various tests on R are run automatically.
 33 
In this directory, various tests on R are run automatically.
30 
This is the recommended way to check if R has been built successfully on
 34 
This is the recommended way to check if R has been built successfully on
31 
your architecture.
 35 
your architecture.
32 
 
 36