CRAN Package Check Results for Package parabar

Last updated on 2025-11-17 01:49:51 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 1.4.2 15.41 101.34 116.75 OK
r-devel-linux-x86_64-debian-gcc 1.4.2 10.98 81.17 92.15 ERROR
r-devel-linux-x86_64-fedora-clang 1.4.2 31.00 144.54 175.54 OK
r-devel-linux-x86_64-fedora-gcc 1.4.2 29.00 166.10 195.10 OK
r-devel-windows-x86_64 1.4.2 19.00 213.00 232.00 OK
r-patched-linux-x86_64 1.4.2 16.42 95.89 112.31 OK
r-release-linux-x86_64 1.4.2 13.49 97.57 111.06 OK
r-release-macos-arm64 1.4.2 7.00 116.00 123.00 OK
r-release-macos-x86_64 1.4.2 14.00 157.00 171.00 OK
r-release-windows-x86_64 1.4.2 15.00 231.00 246.00 OK
r-oldrel-macos-arm64 1.4.2 7.00 100.00 107.00 OK
r-oldrel-macos-x86_64 1.4.2 14.00 152.00 166.00 OK
r-oldrel-windows-x86_64 1.4.2 22.00 242.00 264.00 OK

Check Details

Version: 1.4.2
Check: tests
Result: ERROR Running ‘testthat.R’ [28s/42s] 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") Saving _problems/test-context-74.R Saving _problems/test-context-74.R [ FAIL 2 | WARN 0 | SKIP 3 | PASS 387 ] ══ Skipped tests (3) ═══════════════════════════════════════════════════════════ • On Linux (2): 'test-specification.R:123:5', 'test-user-api.R:169:5' • Test only runs in interactive contexts. (1): 'test-user-api.R:384:9' ══ Failed tests ════════════════════════════════════════════════════════════════ ── Failure ('test-context.R:74:5'): 'Context' performs operations on the cluster correctly ── Expected `service$get_output()` to throw a error. Backtrace: ▆ 1. └─parabar:::tests_set_for_asynchronous_backend_operations(...) at test-context.R:74:5 2. └─parabar:::tests_set_for_asynchronous_backend_task_execution(...) at ./helpers.R:437:5 3. └─testthat::expect_error(service$get_output(), as_text(Exception$async_task_running())) at ./helpers.R:367:5 ── Failure ('test-context.R:74:5'): 'Context' performs operations on the cluster correctly ── Expected `eval(operation)` to throw a error. Backtrace: ▆ 1. └─parabar:::tests_set_for_asynchronous_backend_operations(...) at test-context.R:74:5 2. └─parabar:::tests_set_for_asynchronous_backend_task_execution(...) at ./helpers.R:437:5 3. └─testthat::expect_error(eval(operation), as_text(Exception$async_task_completed())) at ./helpers.R:373:5 [ FAIL 2 | WARN 0 | SKIP 3 | PASS 387 ] Error: ! Test failures. Execution halted Flavor: r-devel-linux-x86_64-debian-gcc