CRAN Package Check Results for Package snvecR

Last updated on 2025-02-16 08:51:01 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 3.9.4 3.21 167.69 170.90 OK
r-devel-linux-x86_64-debian-gcc 3.9.4 2.42 117.09 119.51 OK
r-devel-linux-x86_64-fedora-clang 3.9.4 274.82 NOTE
r-devel-linux-x86_64-fedora-gcc 3.9.4 273.32 NOTE
r-devel-macos-arm64 3.9.4 370.00 OK
r-devel-macos-x86_64 3.9.4 1271.00 ERROR
r-devel-windows-x86_64 3.9.4 6.00 0.00 6.00 FAIL
r-patched-linux-x86_64 3.9.4 3.29 157.77 161.06 OK
r-release-linux-x86_64 3.9.4 3.36 161.08 164.44 OK
r-release-macos-arm64 3.9.4 163.00 OK
r-release-macos-x86_64 3.9.4 264.00 OK
r-release-windows-x86_64 3.9.4 5.00 421.00 426.00 OK
r-oldrel-macos-arm64 3.9.4 216.00 OK
r-oldrel-macos-x86_64 3.9.4 333.00 OK
r-oldrel-windows-x86_64 3.9.4 6.00 0.00 6.00 FAIL

Check Details

Version: 3.9.4
Check: dependencies in R code
Result: NOTE Namespace in Imports field not imported from: ‘backports’ All declared Imports should be used. Flavors: r-devel-linux-x86_64-fedora-clang, r-devel-linux-x86_64-fedora-gcc

Version: 3.9.4
Check: tests
Result: ERROR Running ‘testthat.R’ [0m/14m] 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/tests.html > # * https://testthat.r-lib.org/reference/test_package.html#special-files > > library(testthat) > library(snvecR) > > test_check("snvecR") [ FAIL 1 | WARN 0 | SKIP 2 | PASS 38 ] ══ Skipped tests (2) ═══════════════════════════════════════════════════════════ • On CRAN (2): 'test-get_solution.R:22:3', 'test-snvec.R:34:3' ══ Failed tests ════════════════════════════════════════════════════════════════ ── Error ('test-get_solution.R:13:3'): get_solution() can load eccentricity solutions ── Error in `open.connection(con, "rb")`: cannot open the connection Backtrace: ▆ 1. └─testthat::expect_snapshot(...) at test-get_solution.R:13:3 2. └─rlang::cnd_signal(state$error) [ FAIL 1 | WARN 0 | SKIP 2 | PASS 38 ] Error: Test failures Execution halted Flavor: r-devel-macos-x86_64

Version: 3.9.4
Check: tests
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: > cleanEx() > nameEx("snvec") > ### * snvec > > flush(stderr()); flush(stdout()) > > ### Name: snvec > ### Title: Calculate Earth’s Obliquity and Precession in the Past > ### Aliases: snvec > > ### ** Examples > > > > > ### * <FOOTER> > ### > cleanEx() > options(digits = 7L) > base::cat("Time elapsed: ", proc.time() - base::get("ptime", pos = 'CheckExEnv'),"\n") Time elapsed: 0.44 0.01 0.46 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-devel-windows-x86_64

Version: 3.9.4
Check: tests
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: > cleanEx() > nameEx("snvec") > ### * snvec > > flush(stderr()); flush(stdout()) > > ### Name: snvec > ### Title: Calculate Earth’s Obliquity and Precession in the Past > ### Aliases: snvec > > ### ** Examples > > > > > ### * <FOOTER> > ### > cleanEx() > options(digits = 7L) > base::cat("Time elapsed: ", proc.time() - base::get("ptime", pos = 'CheckExEnv'),"\n") Time elapsed: 0.47 0.05 0.52 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-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.