Last updated on 2024-05-16 23:53:20 CEST.
| Package | ERROR | NOTE | OK |
|---|---|---|---|
| diffobj | 12 | ||
| fansi | 2 | 11 | |
| oshka | 12 | ||
| unitizer | 1 | 11 | |
| vetr | 5 | 7 |
Current CRAN status: OK: 12
Current CRAN status: ERROR: 2, OK: 11
Version: 1.0.6
Check: re-building of vignette outputs
Result: ERROR
Error(s) in re-building vignettes:
...
--- re-building ‘sgr-in-rmd.Rmd’ using rmarkdown
Error: processing vignette 'sgr-in-rmd.Rmd' failed with diagnostics:
there is no package called ‘R6’
--- failed re-building ‘sgr-in-rmd.Rmd’
SUMMARY: processing the following file failed:
‘sgr-in-rmd.Rmd’
Error: Vignette re-building failed.
Execution halted
Flavor: r-release-macos-arm64
Version: 1.0.6
Check: package dependencies
Result: WARN
Skipping vignette re-building
Packages suggested but not available for checking:
'unitizer', 'knitr', 'rmarkdown'
VignetteBuilder package required for checking but not installed: ‘knitr’
Flavor: r-release-macos-x86_64
Version: 1.0.6
Check: examples
Result: ERROR
Running examples in ‘fansi-Ex.R’ failed
The error occurred in:
R Under development (unstable) (2024-01-17 r85813) -- "Unsuffered Consequences"
Copyright (C) 2024 The R Foundation for Statistical Computing
Platform: x86_64-apple-darwin20
R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.
Natural language support but running in an English locale
R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.
Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.
> pkgname <- "fansi"
> source(file.path(R.home("share"), "R", "examples-header.R"))
Execution halted
Flavor: r-release-macos-x86_64
Version: 1.0.6
Check: package vignettes
Result: NOTE
Package has ‘vignettes’ subdirectory but apparently no vignettes.
Perhaps the ‘VignetteBuilder’ information is missing from the
DESCRIPTION file?
* checking PDF version of manual ...* using check arguments '--no-clean-on-error '
Flavor: r-release-macos-x86_64
Current CRAN status: NOTE: 12
Version: 0.1.2
Check: LazyData
Result: NOTE
'LazyData' is specified without a 'data' directory
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-windows-x86_64, r-oldrel-macos-arm64, r-oldrel-macos-x86_64, r-oldrel-windows-x86_64
Current CRAN status: ERROR: 1, OK: 11
Version: 1.4.20
Check: tests
Result: ERROR
Running ‘t-browser.R’ [2s/4s]
Comparing ‘t-browser.Rout’ to ‘t-browser.Rout.save’ ... OK
Running ‘t-capture.R’ [1s/2s]
Comparing ‘t-capture.Rout’ to ‘t-capture.Rout.save’ ... OK
Running ‘t-change.R’ [1s/1s]
Comparing ‘t-change.Rout’ to ‘t-change.Rout.save’ ... OK
Running ‘t-demo.R’ [15s/29s]
Comparing ‘t-demo.Rout’ to ‘t-demo.Rout.save’ ... OK
Running ‘t-error.R’ [1s/2s]
Comparing ‘t-error.Rout’ to ‘t-error.Rout.save’ ... OK
Running ‘t-exec.R’ [1s/2s]
Comparing ‘t-exec.Rout’ to ‘t-exec.Rout.save’ ... OK
Running ‘t-get.R’ [2s/4s]
Comparing ‘t-get.Rout’ to ‘t-get.Rout.save’ ... OK
Running ‘t-global.R’ [1s/2s]
Comparing ‘t-global.Rout’ to ‘t-global.Rout.save’ ... OK
Running ‘t-handledruns.R’ [2s/3s]
Comparing ‘t-handledruns.Rout’ to ‘t-handledruns.Rout.save’ ... OK
Running ‘t-ischecks.R’ [1s/2s]
Comparing ‘t-ischecks.Rout’ to ‘t-ischecks.Rout.save’ ... OK
Running ‘t-item.R’ [2s/4s]
Comparing ‘t-item.Rout’ to ‘t-item.Rout.save’ ... OK
Running ‘t-list.R’ [1s/2s]
Comparing ‘t-list.Rout’ to ‘t-list.Rout.save’ ... OK
Running ‘t-misc.R’ [1s/2s]
Comparing ‘t-misc.Rout’ to ‘t-misc.Rout.save’ ... OK
Running ‘t-nav.R’ [3s/7s]
Comparing ‘t-nav.Rout’ to ‘t-nav.Rout.save’ ... OK
Running ‘t-parse.R’ [1s/2s]
Comparing ‘t-parse.Rout’ to ‘t-parse.Rout.save’ ... OK
Running ‘t-prompt.R’ [1s/2s]
Comparing ‘t-prompt.Rout’ to ‘t-prompt.Rout.save’ ... OK
Running ‘t-random.R’ [2s/3s]
Comparing ‘t-random.Rout’ to ‘t-random.Rout.save’ ... OK
Running ‘t-rename.R’ [1s/1s]
Comparing ‘t-rename.Rout’ to ‘t-rename.Rout.save’ ... OK
Running ‘t-repairenvs.R’ [1s/2s]
Running ‘t-search.R’ [7s/13s]
Comparing ‘t-search.Rout’ to ‘t-search.Rout.save’ ... OK
Running ‘t-section.R’ [1s/2s]
Comparing ‘t-section.Rout’ to ‘t-section.Rout.save’ ... OK
Running ‘t-shim.R’ [6s/12s]
Comparing ‘t-shim.Rout’ to ‘t-shim.Rout.save’ ... OK
Running ‘t-state.R’ [1s/2s]
Comparing ‘t-state.Rout’ to ‘t-state.Rout.save’ ... OK
Running ‘t-text.R’ [1s/2s]
Comparing ‘t-text.Rout’ to ‘t-text.Rout.save’ ... OK
Running ‘t-translate.R’ [3s/6s]
Comparing ‘t-translate.Rout’ to ‘t-translate.Rout.save’ ... OK
Running ‘t-upgrade.R’ [4s/7s]
Comparing ‘t-upgrade.Rout’ to ‘t-upgrade.Rout.save’ ... OK
Running ‘t-utz1.R’ [31s/61s]
Comparing ‘t-utz1.Rout’ to ‘t-utz1.Rout.save’ ... OK
Running ‘t-utz2.R’ [16s/29s]
Comparing ‘t-utz2.Rout’ to ‘t-utz2.Rout.save’ ... OK
Running ‘zz-check.R’ [0s/1s]
Running the tests in ‘tests/t-repairenvs.R’ failed.
Complete output:
> source(file.path("_helper", "init.R"))
>
> exps <- expression(1 + 1, a <- 54, b <- 38, a + b, e <- 5 * a,
+ a^2, f <- e * a, matrix(rep(f, 20)))
> my.unitizer <- new("unitizer", id = 1, zero.env = new.env())
> # add ref.exps as new items
> coi(my.unitizer <- my.unitizer + exps)
> my.unitizer2 <- new("unitizer", id = 2, zero.env = new.env())
> # now convert them to reference items
> coi(my.unitizer2 <- my.unitizer2 + my.unitizer@items.new)
> # - "messed up env ancestry repair works" --------------------------------------
>
> # Purposefully mess up the environments
> parent.env(my.unitizer2@items.ref[[2]]@env) <- baseenv()
> x <- unitizer:::healEnvs(my.unitizer2@items.ref, my.unitizer2)
Error in parent.env(env) : the empty environment has no parent
Error in run_ls(env = x@env, stop.env = base.env, all.names = TRUE, store.env = ref.env.store) :
Specified `stop.env` does not appear to be in parent environments.
Warning in repairEnvs(items.final) :
Detected corrupted environment history; we will attempt to repair, but keep in mind that even when repaired the test environments may be missleading. For example, the objects other than `.new` or `.ref` when reviewing tests at the `unitzer` prompt may not be those you expect or those reported by `ls`. To fully restore environments re-unitize with `unitize(..., force.update=TRUE)`. If errors persist after an attempt to repair, please contact maintainer.
Error in `parent.env<-`(`*tmp*`, value = prev.par) :
cycles in parent chains are not allowed
> old.opt <- options(unitizer.max.env.depth = 20)
> res <- unitizer:::healEnvs(my.unitizer2@items.ref, my.unitizer2)
> is(res, "unitizerItems")
[1] TRUE
> ref.anc <- unitizer:::env_ancestry(x@base.env)
Error in x@base.env :
no applicable method for `@` applied to an object of class "try-error"
Execution halted
Running the tests in ‘tests/zz-check.R’ failed.
Complete output:
> source('aammrtf/check.R')
43: > lorem1 <- "Today, with Kiernan on the stand offering confirmation, Howard walked the jury through the enormous amount of data pulled from Ulbricht's computer. Defense lawyers haven't had a chance yet to respond to this evidence<e2><80><94>that will likely come tomorrow. The mountain they have to climb looks higher than ever, though. Last week, Ulbricht's lawyer outlined a defense in which Ulbricht walked away from the marketplace he created and was \"lured back.\" But what will explain the dozens of folders of data on this laptop, with data from the upper echelons of Silk Road management<e2><80><94>mixed with the most intimate details of Ulbricht's personal life?"
Error: .Rout files missing (failed?):
't-repairenvs.Rout'
In addition: Warning message:
In eval(ei, envir) : Some outputs contain non-ASCII:
't-text.Rout'
Execution halted
Flavor: r-devel-linux-x86_64-debian-gcc
Current CRAN status: NOTE: 5, OK: 7
Version: 0.2.16
Check: compiled code
Result: NOTE
File ‘vetr/libs/vetr.so’:
Found non-API call to R: ‘SETLENGTH’
Compiled code should not call non-API entry points in R.
See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual.
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
Version: 0.2.16
Check: compiled code
Result: NOTE
File 'vetr/libs/x64/vetr.dll':
Found non-API call to R: 'SETLENGTH'
Compiled code should not call non-API entry points in R.
See 'Writing portable packages' in the 'Writing R Extensions' manual.
Flavor: r-devel-windows-x86_64