CRAN Package Check Results for Package bsts

Last updated on 2026-07-29 03:58:37 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.9.11 125.65 102.24 227.89 OK
r-devel-linux-x86_64-debian-gcc 0.9.11 87.98 74.73 162.71 NOTE
r-devel-linux-x86_64-fedora-clang 0.9.11 164.00 171.44 335.44 OK
r-devel-linux-x86_64-fedora-gcc 0.9.11 94.00 68.35 162.35 OK
r-devel-windows-x86_64 0.9.11 154.00 199.00 353.00 OK
r-patched-linux-x86_64 0.9.11 125.32 101.28 226.60 OK
r-release-linux-x86_64 0.9.11 122.55 99.75 222.30 OK
r-release-macos-arm64 0.9.11 27.00 10.00 37.00 OK
r-release-macos-x86_64 0.9.11 64.00 179.00 243.00 OK
r-release-windows-x86_64 0.9.11 156.00 211.00 367.00 OK
r-oldrel-macos-arm64 0.9.11 OK
r-oldrel-macos-x86_64 0.9.11 61.00 149.00 210.00 OK
r-oldrel-windows-x86_64 0.9.11 147.00 282.00 429.00 OK

Additional issues

rchk

Check Details

Version: 0.9.11
Check: compiled code
Result: NOTE File ‘/home/hornik/tmp/R.check/r-devel-gcc/Work/build/Packages/bsts/libs/bsts.so’: Found ‘_ZSt4cerr’, possibly from ‘std::cerr’ (C++) Found ‘_ZSt4cout’, possibly from ‘std::cout’ (C++) Found ‘srand’, possibly from ‘srand’ (C) Compiled code should not call entry points which might terminate R nor write to stdout/stderr instead of to the console, nor use Fortran I/O nor system RNGs nor [v]sprintf. The detected symbols are linked into the code but might come from libraries and not actually be called. See ‘Writing portable packages’ in the ‘Writing R Extensions’ manual. Flavor: r-devel-linux-x86_64-debian-gcc