CRAN Package Check Results for Package parabar

Last updated on 2025-04-12 20:51:53 CEST.

Flavor	Version	Tinstall	Tcheck	Ttotal	Status	Flags
r-devel-linux-x86_64-debian-clang	1.4.2	15.16	98.79	113.95	OK
r-devel-linux-x86_64-debian-gcc	1.4.2	8.30	70.31	78.61	ERROR
r-devel-linux-x86_64-fedora-clang	1.4.2			179.46	OK
r-devel-linux-x86_64-fedora-gcc	1.4.2			195.05	OK
r-devel-macos-arm64	1.4.2			123.00	OK
r-devel-macos-x86_64	1.4.2			171.00	OK
r-devel-windows-x86_64	1.4.2	16.00	236.00	252.00	OK
r-patched-linux-x86_64	1.4.2	17.90	97.34	115.24	OK
r-release-linux-x86_64	1.4.2				OK
r-release-macos-arm64	1.4.2			107.00	OK
r-release-macos-x86_64	1.4.2			166.00	OK
r-release-windows-x86_64	1.4.2	19.00	237.00	256.00	OK
r-oldrel-macos-arm64	1.4.2				OK
r-oldrel-macos-x86_64	1.4.2			161.00	OK
r-oldrel-windows-x86_64	1.4.2	20.00	232.00	252.00	OK

Check Details

Version: 1.4.2
Check: tests
Result: ERROR Running ‘testthat.R’ [25s/38s] 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") [ 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-async-backend.R:133:5'): 'AsyncBackend' 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-async-backend.R:133:5 2. └─parabar:::tests_set_for_asynchronous_backend_task_execution(...) at tests/testthat/helpers.R:458:5 3. ├─testthat::expect_error(eval(operation), as_text(Exception$async_task_running())) at tests/testthat/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 = 11L, z = 16L, sleep = 0) 12. └─private$.throw_if_backend_is_busy() 13. └─Exception$async_task_completed() ── Error ('test-async-backend.R:133:5'): 'AsyncBackend' 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-async-backend.R:133:5 2. └─service$stop() at tests/testthat/helpers.R:388:9 3. └─private$.stop() 4. └─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