CRAN Package Check Results for Package parabar

Last updated on 2026-08-16 17:50:39 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 1.4.2 15.62 106.83 122.45 OK
r-devel-linux-x86_64-debian-gcc 1.4.2 9.62 81.01 90.63 OK
r-devel-linux-x86_64-fedora-clang 1.4.2 10.00 72.28 82.28 OK
r-devel-linux-x86_64-fedora-gcc 1.4.2 10.00 77.36 87.36 OK
r-devel-windows-x86_64 1.4.2 18.00 227.00 245.00 OK
r-patched-linux-x86_64 1.4.2 17.92 104.21 122.13 OK
r-release-linux-x86_64 1.4.2 12.88 102.25 115.13 OK
r-release-macos-arm64 1.4.2 3.00 79.00 82.00 OK
r-release-macos-x86_64 1.4.2 10.00 171.00 181.00 OK
r-release-windows-x86_64 1.4.2 15.00 0.00 15.00 ERROR
r-oldrel-macos-arm64 1.4.2 OK
r-oldrel-macos-x86_64 1.4.2 9.00 162.00 171.00 OK
r-oldrel-windows-x86_64 1.4.2 21.00 283.00 304.00 OK

Check Details

Version: 1.4.2
Check: tests
Result: ERROR Running 'testthat.R' [186s] 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 > > # Set environmental variable to prevent hang on quitting the `R` session. > # Error message: > # - `Error while shutting down parallel: unable to terminate some child processes` > # See: > # - https://github.com/r-lib/processx/issues/310 > # - https://github.com/r-lib/processx/issues/240 > # - https://github.com/r-lib/callr/issues/158 > Sys.setenv(PROCESSX_NOTIFY_OLD_SIGCHLD = "true") > > library(testthat) > library(parabar) > > test_check("parabar") stdout:] stderr:] Saving _problems/test-backend-finalizer-37.R [ FAIL 1 | WARN 0 | SKIP 3 | PASS 391 ] ══ Skipped tests (3) ═══════════════════════════════════════════════════════════ • On Windows (2): 'test-specification.R:90:5', 'test-user-api.R:145:5' • Test only runs in interactive contexts. (1): 'test-user-api.R:384:9' ══ Failed tests ════════════════════════════════════════════════════════════════ ── Error ('test-backend-finalizer.R:37:5'): 'AsyncBackend' finalizer executes without throwing ── <rlib_error_3_0/rlib_error/error/condition> Error in `"rs_init(self, private, super, options, wait, wait_timeout)"`: ! Could not start R session, timed out Backtrace: ▆ 1. └─parabar::start_backend(cores = 2, backend_type = "async") at test-backend-finalizer.R:37:5 2. └─backend$start(specification) 3. └─private$.start(specification) 4. └─callr::r_session$new() 5. └─callr (local) initialize(...) 6. └─callr:::rs_init(self, private, super, options, wait, wait_timeout) 7. └─throw(new_error("Could not start R session, timed out")) [ FAIL 1 | WARN 0 | SKIP 3 | PASS 391 ] Error: ! Test failures. Execution halted Flavor: r-release-windows-x86_64