| is_cran {fritools} | R Documentation |
Is 'R' Running on CRAN?
Description
This is a verbatim copy of fda::CRAN of
fda version 5.1.9.
Usage
is_cran(cran_pattern, n_r_check4cran)
Arguments
cran_pattern |
A regular expressions to apply to the names of
|
n_r_check4cran |
Assume this is CRAN if at least n_R_CHECK4CRAN
elements of
|
Details
This function allows package developers to run tests themselves that should not run on CRAN or with
R CMD check --as-cran
because of compute time constraints with CRAN tests.
The "Writing R Extensions" manual says that R CMD check can be
customized "by setting environment variables _R_CHECK_*_:, as
described in" the Tools section of the "R Internals" manual.
R CMD check was tested with R 3.0.1 under Fedora 18 Linux and with
Rtools 3.0 from April 16, 2013 under Windows 7. With the
'--as-cran'
option, 7 matches were found; without it, only 3 were found. These numbers were unaffected by the presence or absence of the '–timings' parameter. On this basis, the default value of n_R_CHECK4CRAN was set at 5.
1. x. <- Sys.getenv()
2. Fix CRAN_pattern and n_R_CHECK4CRAN if missing.
3. Let i be the indices of x. whose names match all the patterns in the vector x.
4. Assume this is CRAN if length(i) >= n_R_CHECK4CRAN
Value
A logical scalar with attributes ‘'sys_getenv'’ containing the
results of Sys.getenv() and 'matches' containing i per step 3
above.
See Also
Other test helpers:
develop_test(),
get_boolean_envvar(),
get_run_r_tests(),
is_r_cmd_check(),
is_running_on_fvafrcu_machines(),
is_running_on_gitlab_com(),
run_r_tests_for_known_hosts(),
set_run_r_tests()
Other logical helpers:
get_run_r_tests(),
is_batch(),
is_false(),
is_force(),
is_installed(),
is_not_false(),
is_null_or_true(),
is_of_length_zero(),
is_r_cmd_check(),
is_r_package_installed(),
is_running_on_fvafrcu_machines(),
is_running_on_gitlab_com(),
is_success(),
is_version_sufficient(),
is_windows()
Examples
if (!is_cran()) {
message("Run your tests here.")
}