1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
|
if (requireNamespace("tinytest", quietly=TRUE)) {
## if OMP_THREAD_LIMIT is set, and its value is 2, we have a good
## idea of where we are and we likely do not want to run all tests
if (Sys.getenv("OMP_THREAD_LIMIT", unset="") == "2") { # set and 2
if (Sys.getenv("RunAllRcppTests", "") != "") { # if unset
Sys.setenv("RunAllRcppTests"="no")
}
if (Sys.getenv("RunVerboseRcppTests", "") != "") { # if unset
Sys.setenv("RunVerboseRcppTests"="no")
}
}
## Force tests to be executed if in dev release which we define as
## having a sub-release, eg 0.9.15.5 is one whereas 0.9.16 is not
if (length(strsplit(format(packageVersion("Rcpp")), "\\.")[[1]]) > 3) { # dev rel, and
if (Sys.getenv("RunAllRcppTests") != "no") { # if env.var not yet set
message("Setting \"RunAllRcppTests\"=\"yes\" for development release")
Sys.setenv("RunAllRcppTests"="yes")
}
if (Sys.getenv("RunVerboseRcppTests") != "no") { # if env.var not yet set
message("Setting \"RunVerboseRcppTests\"=\"yes\" for development release")
Sys.setenv("RunVerboseRcppTests"="yes")
}
}
## On Travis also always set tests; see
## https://docs.travis-ci.com/user/environment-variables/#default-environment-variables
## GitHub Action also set CI variable; see
## https://docs.github.com/en/actions/reference/environment-variables
## And we set it in 'docker run' call
## Ensure Codecov runs full tests too
if ((Sys.getenv("CI") == "true") ||
(Sys.getenv("TRAVIS") == "true") ||
(Sys.getenv("CONTINUOUS_INTEGRATION") == "true") ||
(Sys.getenv("CODECOV_TOKEN") != "")) {
if (Sys.getenv("RunAllRcppTests") != "no") { # if env.var not yet set
message("Always enabling \"RunAllRcppTests\"=\"yes\" in CI\n")
Sys.setenv("RunAllRcppTests"="yes")
}
if (Sys.getenv("RunVerboseRcppTests") != "no") { # if env.var not yet set
message("Always enabling \"RunVerboseRcppTests\"=\"yes\" in CI\n")
Sys.setenv("RunVerboseRcppTests"="yes")
}
}
## there are several more granular ways to test files in a tinytest directory,
## see its package vignette; tests can also run once the package is installed
## using the same command `test_package(pkgName)`, or by director or file
tinytest::test_package("Rcpp")
}
|
