CRAN Package Check Results for Package BayesChange

Last updated on 2025-04-26 20:50:29 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 2.0.0 41.68 76.53 118.21 ERROR
r-devel-linux-x86_64-debian-gcc 2.0.0 32.54 63.93 96.47 OK
r-devel-linux-x86_64-fedora-clang 2.0.0 204.80 OK
r-devel-linux-x86_64-fedora-gcc 2.0.0 235.23 OK
r-devel-windows-x86_64 2.0.0 50.00 116.00 166.00 OK
r-patched-linux-x86_64 2.0.0 47.33 72.59 119.92 OK
r-release-linux-x86_64 2.0.0 44.10 71.65 115.75 OK
r-release-macos-arm64 2.0.0 74.00 OK
r-release-macos-x86_64 2.0.0 97.00 OK
r-release-windows-x86_64 2.0.0 47.00 120.00 167.00 OK
r-oldrel-macos-arm64 2.0.0 74.00 NOTE
r-oldrel-macos-x86_64 2.0.0 96.00 NOTE
r-oldrel-windows-x86_64 2.0.0 60.00 143.00 203.00 OK

Check Details

Version: 2.0.0
Check: tests
Result: ERROR Running ‘testthat.R’ [3s/4s] Running the tests in ‘tests/testthat.R’ failed. Complete output: > # This file is part of the standard setup for testthat. > # It is recommended that you do not modify it. > # > # Where should you do additional test configuration? > # Learn more about the roles of various files in: > # * https://r-pkgs.org/testing-design.html#sec-tests-files-overview > # * https://testthat.r-lib.org/articles/special-files.html > > library(testthat) > library(BayesChange) > > test_check("BayesChange") [ FAIL 1 | WARN 0 | SKIP 0 | PASS 2 ] ══ Failed tests ════════════════════════════════════════════════════════════════ ── Error ('test-test-clust_cp.R:11:3'): clust_cp works ───────────────────────── <std::logic_error/C++Error/error/condition> Error: max(): object has no elements Backtrace: ▆ 1. └─BayesChange::clust_cp(...) at test-test-clust_cp.R:11:3 2. └─BayesChange::clust_cp_uni(...) [ FAIL 1 | WARN 0 | SKIP 0 | PASS 2 ] Error: Test failures Execution halted Flavor: r-devel-linux-x86_64-debian-clang

Version: 2.0.0
Check: installed package size
Result: NOTE installed size is 6.7Mb sub-directories of 1Mb or more: libs 6.4Mb Flavors: r-oldrel-macos-arm64, r-oldrel-macos-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.
Health stats visible at Monitor.