Last updated on 2024-03-27 10:09:23 CET.
Flavor | Version | Tinstall | Tcheck | Ttotal | Status | Flags |
---|---|---|---|---|---|---|
r-devel-linux-x86_64-debian-clang | 0.1.7 | 4.49 | 125.31 | 129.80 | NOTE | |
r-devel-linux-x86_64-debian-gcc | 0.1.7 | 4.83 | 94.72 | 99.55 | NOTE | |
r-devel-linux-x86_64-fedora-clang | 0.1.7 | 167.86 | NOTE | |||
r-devel-linux-x86_64-fedora-gcc | 0.1.7 | 177.01 | NOTE | |||
r-devel-windows-x86_64 | 0.1.7 | 7.00 | 113.00 | 120.00 | NOTE | |
r-patched-linux-x86_64 | 0.1.7 | 8.03 | 119.95 | 127.98 | OK | |
r-release-linux-x86_64 | 0.1.7 | 4.38 | 117.32 | 121.70 | OK | |
r-release-macos-arm64 | 0.1.7 | 72.00 | OK | |||
r-release-macos-x86_64 | 0.1.7 | 115.00 | OK | |||
r-release-windows-x86_64 | 0.1.7 | 8.00 | 137.00 | 145.00 | OK | |
r-oldrel-macos-arm64 | 0.1.7 | 62.00 | OK | |||
r-oldrel-windows-x86_64 | 0.1.7 | 9.00 | 144.00 | 153.00 | OK |
Version: 0.1.7
Check: Rd files
Result: NOTE
checkRd: (-1) mock-db-methods.Rd:139: Lost braces; missing escapes or markup?
139 | how {dittodb} works.
| ^
checkRd: (-1) mockdb.Rd:27: Lost braces; missing escapes or markup?
27 | remember to stop the mocking. When testing with {dittodb}, it will look for
| ^
checkRd: (-1) mockdb.Rd:41: Lost braces; missing escapes or markup?
41 | that function because {dittodb} uses the database name (given in \code{dbname} or
| ^
checkRd: (-1) nycflights_sqlite.Rd:13: Lost braces; missing escapes or markup?
13 | Included with {dittodb} is a small subset of
| ^
checkRd: (-1) nycflights_sqlite.Rd:18: Lost braces; missing escapes or markup?
18 | This database is helpful for getting to know {dittodb} and running example
| ^
checkRd: (-1) redact_columns.Rd:24: Lost braces; missing escapes or markup?
24 | \code{data} using {dittodb}'s standard redactors.
| ^
checkRd: (-1) sanitize_table_id.Rd:20: Lost braces; missing escapes or markup?
20 | drivers. For the purposes of {dittodb}, the details are less important since
| ^
checkRd: (-1) set_dittodb_debug_level.Rd:5: Lost braces; missing escapes or markup?
5 | \title{Set {dittodb}'s debug level}
| ^
checkRd: (-1) set_dittodb_debug_level.Rd:16: Lost braces; missing escapes or markup?
16 | It can be helpful to see what's going on by increasing {dittodb}'s verbosity
| ^
checkRd: (-1) set_dittodb_debug_level.Rd:24: Lost braces; missing escapes or markup?
24 | silent. The higher the level, the more verbose {dittodb} will be.
| ^
checkRd: (-1) set_dittodb_debug_level.Rd:26: Lost braces; missing escapes or markup?
26 | Currently, {dittodb} only has one level of debugging (any value 1 or
| ^
checkRd: (-1) use_dittodb.Rd:5: Lost braces; missing escapes or markup?
5 | \title{Use {dittodb} in your tests}
| ^
checkRd: (-1) use_dittodb.Rd:16: Lost braces; missing escapes or markup?
16 | If you would like to use {dittodb} in your package, and you are already using
| ^
checkRd: (-1) use_dittodb.Rd:18: Lost braces; missing escapes or markup?
18 | add {dittodb} to Suggests in the package DESCRIPTION and loads it in
| ^
checkRd: (-1) use_dittodb.Rd:24: Lost braces; missing escapes or markup?
24 | \code{path} argument. The function is idempotent: if {dittodb} is already added to
| ^
checkRd: (-1) use_dittodb.Rd:29: Lost braces; missing escapes or markup?
29 | \item add {dittodb} to the \code{Suggests} field of the DESCRIPTION file in the
| ^
checkRd: (-1) with_mock_path.Rd:23: Lost braces; missing escapes or markup?
23 | database fixtures located in other directories. {dittodb} will look for
| ^
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc, r-devel-windows-x86_64