Last updated on 2025-05-08 09:54:00 CEST.
Flavor | Version | Tinstall | Tcheck | Ttotal | Status | Flags |
---|---|---|---|---|---|---|
r-devel-linux-x86_64-debian-clang | 1.7-5 | 12.59 | 123.59 | 136.18 | NOTE | |
r-devel-linux-x86_64-debian-gcc | 1.7-5 | 7.87 | 87.04 | 94.91 | NOTE | |
r-devel-linux-x86_64-fedora-clang | 1.7-5 | 218.94 | NOTE | |||
r-devel-linux-x86_64-fedora-gcc | 1.7-5 | 217.61 | NOTE | |||
r-devel-windows-x86_64 | 1.7-5 | 11.00 | 166.00 | 177.00 | NOTE | |
r-patched-linux-x86_64 | 1.7-5 | 12.25 | 112.89 | 125.14 | NOTE | |
r-release-linux-x86_64 | 1.7-5 | 11.04 | 118.73 | 129.77 | NOTE | |
r-release-macos-arm64 | 1.7-5 | 68.00 | NOTE | |||
r-release-macos-x86_64 | 1.7-5 | 222.00 | NOTE | |||
r-release-windows-x86_64 | 1.7-5 | 11.00 | 0.00 | 11.00 | FAIL | |
r-oldrel-macos-arm64 | 1.7-5 | 71.00 | NOTE | |||
r-oldrel-macos-x86_64 | 1.7-5 | 111.00 | NOTE | |||
r-oldrel-windows-x86_64 | 1.7-5 | 15.00 | 188.00 | 203.00 | NOTE |
Version: 1.7-5
Check: Rd files
Result: NOTE
checkRd: (-1) NEWS.Rd:669: Lost braces; missing escapes or markup?
669 | parameters are rounded so they belong to one of {0, 0.5, 1}. (Simon)
| ^
checkRd: (-1) gradients.Rd:96-99: Lost braces in \itemize; meant \describe ?
checkRd: (-1) gradients.Rd:100-103: Lost braces in \itemize; meant \describe ?
checkRd: (-1) gradients.Rd:104-107: Lost braces in \itemize; meant \describe ?
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, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-macos-arm64, r-release-macos-x86_64, r-release-windows-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64
Version: 1.7-5
Check: Rd cross-references
Result: NOTE
Found the following Rd file(s) with Rd \link{} targets missing package
anchors:
readCoordsJS.Rd: fromJSON
readMappingsJS.Rd: fromJSON
Please provide package anchors for all Rd \link{} targets not in the
package itself and the base packages.
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-debian-gcc, r-devel-windows-x86_64, r-patched-linux-x86_64, r-release-linux-x86_64, r-release-windows-x86_64
Version: 1.7-5
Check: re-building of vignette outputs
Result: FAIL
Check process probably crashed or hung up for 20 minutes ... killed
Most likely this happened in the example checks (?),
if not, ignore the following last lines of example output:
> ##D gridSVGCoords(readCoordsJS("create-test.svg.coords.js"))
> ##D
> ##D # This should appear to be the same rect
> ##D grid.newpage()
> ##D pushViewport(viewportCreate("testVP.1"))
> ##D grid.rect()
> ##D
> ##D # Let's see if the scales are accurate, should be:
> ##D # xscale: [0, 20]
> ##D # yscale: [0, 10]
> ##D current.viewport()$xscale
> ##D current.viewport()$yscale
> ## End(Not run)
>
>
> ### * <FOOTER>
> ###
> cleanEx()
> options(digits = 7L)
> base::cat("Time elapsed: ", proc.time() - base::get("ptime", pos = 'CheckExEnv'),"\n")
Time elapsed: 0.53 0.05 0.57 NA NA
> grDevices::dev.off()
null device
1
> ###
> ### Local variables: ***
> ### mode: outline-minor ***
> ### outline-regexp: "\\(> \\)?### [*]+" ***
> ### End: ***
> quit('no')
======== End of example output (where/before crash/hang up occured ?) ========
Flavor: r-release-windows-x86_64