CRAN Package Check Results for Package funcharts

Last updated on 2025-12-04 21:49:39 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 1.7.0 45.59 291.19 336.78 OK
r-devel-linux-x86_64-debian-gcc 1.7.0 32.15 188.03 220.18 OK
r-devel-linux-x86_64-fedora-clang 1.7.0 112.00 427.52 539.52 OK
r-devel-linux-x86_64-fedora-gcc 1.7.0 102.00 425.01 527.01 OK
r-devel-windows-x86_64 1.7.0 53.00 286.00 339.00 OK
r-patched-linux-x86_64 1.7.0 51.08 270.12 321.20 OK
r-release-linux-x86_64 1.7.0 47.04 277.16 324.20 OK
r-release-macos-arm64 1.7.0 OK
r-release-macos-x86_64 1.7.0 55.00 275.00 330.00 OK
r-release-windows-x86_64 1.7.0 53.00 284.00 337.00 OK
r-oldrel-macos-arm64 1.7.0 OK
r-oldrel-macos-x86_64 1.7.0 56.00 236.00 292.00 OK
r-oldrel-windows-x86_64 1.7.0 68.00 373.00 441.00 ERROR

Check Details

Version: 1.7.0
Check: tests
Result: ERROR Running 'testthat.R' [65s] Running the tests in 'tests/testthat.R' failed. Complete output: > library(testthat) > library(funcharts) Loading required package: robustbase > > test_check("funcharts") Saving _problems/test_AMFCC-44.R [ FAIL 1 | WARN 0 | SKIP 3 | PASS 113 ] ══ Skipped tests (3) ═══════════════════════════════════════════════════════════ • On CRAN (1): 'test_FRTM.R:1:1' • empty test (2): , ══ Failed tests ════════════════════════════════════════════════════════════════ ── Error ('test_AMFCC.R:38:1'): (code run outside of `test_that()`) ──────────── Error in `bw.SJ(x, method = "ste")`: sample is too sparse to find TD Backtrace: ▆ 1. └─funcharts::AMFCC_PhaseI(...) at test_AMFCC.R:38:1 2. └─funcharts:::get_CL(p_value_com_cont_rr[[rr]], 1/alpha_diagn) 3. ├─spatstat.univar::quantile.density(...) 4. │ └─base::stopifnot(inherits(x, "density")) 5. ├─stats::density(p_values_combined[[ww]], bw = "SJ") 6. └─stats::density.default(p_values_combined[[ww]], bw = "SJ") 7. └─stats::bw.SJ(x, method = "ste") [ FAIL 1 | WARN 0 | SKIP 3 | PASS 113 ] Error: ! Test failures. Execution halted Flavor: r-oldrel-windows-x86_64

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.