- using R Under development (unstable) (2025-11-15 r89024)
- using platform: x86_64-pc-linux-gnu
- R was compiled by
gcc-15 (Debian 15.2.0-7) 15.2.0
GNU Fortran (Debian 15.2.0-7) 15.2.0
- running under: Debian GNU/Linux forky/sid
- using session charset: UTF-8
- checking for file ‘parabar/DESCRIPTION’ ... OK
- this is package ‘parabar’ version ‘1.4.2’
- package encoding: UTF-8
- checking CRAN incoming feasibility ... [2s/2s] OK
- checking package namespace information ... OK
- checking package dependencies ... OK
- checking if this is a source package ... OK
- checking if there is a namespace ... OK
- checking for executable files ... OK
- checking for hidden files and directories ... OK
- checking for portable file names ... OK
- checking for sufficient/correct file permissions ... OK
- checking serialization versions ... OK
- checking whether package ‘parabar’ can be installed ... OK
See the install log for details.
- checking package directory ... OK
- checking for future file timestamps ... OK
- checking ‘build’ directory ... OK
- checking DESCRIPTION meta-information ... OK
- checking top-level files ... OK
- checking for left-over files ... OK
- checking index information ... OK
- checking package subdirectories ... OK
- checking code files for non-ASCII characters ... OK
- checking R files for syntax errors ... OK
- checking whether the package can be loaded ... [1s/1s] OK
- checking whether the package can be loaded with stated dependencies ... [0s/1s] OK
- checking whether the package can be unloaded cleanly ... [0s/1s] OK
- checking whether the namespace can be loaded with stated dependencies ... [0s/1s] OK
- checking whether the namespace can be unloaded cleanly ... [0s/1s] OK
- checking loading without being on the library search path ... [0s/1s] OK
- checking whether startup messages can be suppressed ... [1s/1s] OK
- checking use of S3 registration ... OK
- checking dependencies in R code ... OK
- checking S3 generic/method consistency ... OK
- checking replacement functions ... OK
- checking foreign function calls ... OK
- checking R code for possible problems ... [4s/6s] OK
- checking Rd files ... [1s/1s] OK
- checking Rd metadata ... OK
- checking Rd line widths ... OK
- checking Rd cross-references ... OK
- checking for missing documentation entries ... OK
- checking for code/documentation mismatches ... OK
- checking Rd \usage sections ... OK
- checking Rd contents ... OK
- checking for unstated dependencies in examples ... OK
- checking installed files from ‘inst/doc’ ... OK
- checking files in ‘vignettes’ ... OK
- checking examples ... [10s/40s] OK
- checking for unstated dependencies in ‘tests’ ... OK
- checking tests ... [28s/43s] 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
- checking for unstated dependencies in vignettes ... OK
- checking package vignettes ... OK
- checking re-building of vignette outputs ... [3s/5s] OK
- checking PDF version of manual ... [9s/12s] OK
- checking HTML version of manual ... [5s/7s] OK
- checking for non-standard things in the check directory ... OK
- DONE
Status: 1 ERROR