CRAN Package Check Results for Package parabar

Last updated on 2025-12-23 11:52:47 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 1.4.2 15.13 104.59 119.72 OK
r-devel-linux-x86_64-debian-gcc 1.4.2 9.79 76.78 86.57 ERROR
r-devel-linux-x86_64-fedora-clang 1.4.2 26.00 161.15 187.15 OK
r-devel-linux-x86_64-fedora-gcc 1.4.2 25.00 186.24 211.24 OK
r-devel-windows-x86_64 1.4.2 16.00 223.00 239.00 OK
r-patched-linux-x86_64 1.4.2 17.84 94.93 112.77 OK
r-release-linux-x86_64 1.4.2 14.38 94.72 109.10 OK
r-release-macos-arm64 1.4.2 OK
r-release-macos-x86_64 1.4.2 9.00 162.00 171.00 OK
r-release-windows-x86_64 1.4.2 16.00 230.00 246.00 OK
r-oldrel-macos-arm64 1.4.2 OK
r-oldrel-macos-x86_64 1.4.2 10.00 156.00 166.00 OK
r-oldrel-windows-x86_64 1.4.2 23.00 260.00 283.00 OK

Check Details

Version: 1.4.2
Check: tests
Result: ERROR Running ‘testthat.R’ [25s/45s] 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 365 ] ══ 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 ════════════════════════════════════════════════════════════════ ── Error ('test-context.R:74:5'): 'Context' performs operations on the cluster correctly ── Error: A task is completed with unread results. 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:458:5 3. ├─testthat::expect_error(eval(operation), as_text(Exception$async_task_running())) at ./helpers.R:358:5 4. │ └─testthat:::expect_condition_matching_(...) 5. │ └─testthat:::quasi_capture(...) 6. │ ├─testthat (local) .capture(...) 7. │ │ └─base::withCallingHandlers(...) 8. │ └─rlang::eval_bare(quo_get_expr(.quo), quo_get_env(.quo)) 9. ├─base::eval(operation) 10. │ └─base::eval(operation) 11. └─service$apply(`<dbl>`, 1, `<fn>`, y = 4L, z = 78L, sleep = 0) 12. └─private$.backend$apply(x = x, margin = margin, fun = fun, ...) 13. └─private$.throw_if_backend_is_busy() 14. └─Exception$async_task_completed() ── Error ('test-context.R:74:5'): 'Context' performs operations on the cluster correctly ── Error: Cannot stop a busy backend when option `stop_forceful = FALSE`. Backtrace: ▆ 1. └─parabar:::tests_set_for_asynchronous_backend_operations(...) at test-context.R:74:5 2. └─service$stop() at ./helpers.R:388:9 3. └─private$.backend$stop() 4. └─private$.stop() 5. └─Exception$stop_busy_backend_not_allowed() [ FAIL 2 | WARN 0 | SKIP 3 | PASS 365 ] Error: ! Test failures. Execution halted Flavor: r-devel-linux-x86_64-debian-gcc