CRAN Package Check Results for Package syrup

Last updated on 2025-02-23 15:49:59 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.1.1 3.47 42.76 46.23 OK
r-devel-linux-x86_64-debian-gcc 0.1.1 2.58 33.76 36.34 OK
r-devel-linux-x86_64-fedora-clang 0.1.1 72.16 ERROR
r-devel-linux-x86_64-fedora-gcc 0.1.1 72.55 ERROR
r-devel-macos-arm64 0.1.1 35.00 OK
r-devel-macos-x86_64 0.1.1 54.00 OK
r-devel-windows-x86_64 0.1.1 4.00 49.00 53.00 OK
r-patched-linux-x86_64 0.1.1 3.26 40.07 43.33 OK
r-release-linux-x86_64 0.1.1 3.00 40.32 43.32 OK
r-release-macos-arm64 0.1.1 37.00 OK
r-release-macos-x86_64 0.1.1 66.00 OK
r-release-windows-x86_64 0.1.1 5.00 49.00 54.00 OK
r-oldrel-macos-arm64 0.1.1 40.00 OK
r-oldrel-macos-x86_64 0.1.1 63.00 OK
r-oldrel-windows-x86_64 0.1.1 6.00 55.00 61.00 OK

Check Details

Version: 0.1.1
Check: examples
Result: ERROR Running examples in ‘syrup-Ex.R’ failed The error most likely occurred in: > ### Name: syrup > ### Title: Memory and CPU Usage Information for Parallel R Code > ### Aliases: syrup > > ### ** Examples > > ## Don't show: > if (ps::ps_os_type()[["POSIX"]]) (if (getRversion() >= "3.4") withAutoprint else force)({ # examplesIf + ## End(Don't show) + # pass any expression to syrup. first, sequentially: + res_syrup <- syrup({res_output <- Sys.sleep(1)}) + + res_syrup + + # to snapshot memory and CPU information more (or less) often, set `interval` + syrup(Sys.sleep(1), interval = .01) + + # use `peak = TRUE` to return only the snapshot with + # the highest memory usage (as `sum(rss)`) + syrup(Sys.sleep(1), interval = .01, peak = TRUE) + + # results from syrup are more---or maybe only---useful when + # computations are evaluated in parallel. see package README + # for an example. + ## Don't show: + }) # examplesIf > res_syrup <- syrup({ + res_output <- Sys.sleep(1) + }) Error in `syrup()`: ! Unable to retrieve resource usage results from the temporary session. ℹ This is an internal error that was detected in the syrup package. Please report it at <https://github.com/simonpcouch/syrup/issues> with a reprex (<https://tidyverse.org/help/>) and the full backtrace. Backtrace: ▆ 1. ├─(if (getRversion() >= "3.4") withAutoprint else force)(...) 2. │ └─base::source(...) 3. │ ├─base::withVisible(eval(ei, envir)) 4. │ └─base::eval(ei, envir) 5. │ └─base::eval(ei, envir) 6. └─syrup::syrup(...) 7. └─syrup:::retrieve_results(sesh) 8. └─rlang::abort(...) Execution halted Flavor: r-devel-linux-x86_64-fedora-clang

Version: 0.1.1
Check: tests
Result: ERROR Running ‘testthat.R’ [11s/39s] 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/testing-design.html#sec-tests-files-overview > # * https://testthat.r-lib.org/articles/special-files.html > > library(testthat) > library(syrup) Loading required package: bench > > test_check("syrup") [ FAIL 7 | WARN 0 | SKIP 2 | PASS 1 ] ══ Skipped tests (2) ═══════════════════════════════════════════════════════════ • On CRAN (2): 'test-syrup.R:70:3', 'test-syrup.R:76:3' ══ Failed tests ════════════════════════════════════════════════════════════════ ── Failure ('test-syrup.R:5:3'): syrup works ─────────────────────────────────── Expected `res <- syrup(res_with_syrup <- Sys.sleep(1))` to run without any errors. i Actually got a <rlang_error> with text: Unable to retrieve resource usage results from the temporary session. i This is an internal error that was detected in the syrup package. Please report it at <https://github.com/simonpcouch/syrup/issues> with a reprex (<https://tidyverse.org/help/>) and the full backtrace. ── Error ('test-syrup.R:16:3'): syrup works ──────────────────────────────────── Error in `eval(code, test_env)`: object 'res' not found Backtrace: ▆ 1. └─testthat::expect_s3_class(res, "tbl_df") at test-syrup.R:16:3 2. └─testthat::quasi_label(enquo(object), arg = "object") 3. └─rlang::eval_bare(expr, quo_get_env(quo)) ── Failure ('test-syrup.R:30:3'): syrup(peak = TRUE) works ───────────────────── Expected `res <- syrup(Sys.sleep(1), peak = TRUE)` to run without any errors. i Actually got a <rlang_error> with text: Unable to retrieve resource usage results from the temporary session. i This is an internal error that was detected in the syrup package. Please report it at <https://github.com/simonpcouch/syrup/issues> with a reprex (<https://tidyverse.org/help/>) and the full backtrace. ── Error ('test-syrup.R:37:3'): syrup(peak = TRUE) works ─────────────────────── Error in `eval(code, test_env)`: object 'res' not found Backtrace: ▆ 1. └─testthat::expect_s3_class(res, "tbl_df") at test-syrup.R:37:3 2. └─testthat::quasi_label(enquo(object), arg = "object") 3. └─rlang::eval_bare(expr, quo_get_env(quo)) ── Failure ('test-syrup.R:45:3'): syrup(interval) works ──────────────────────── Expected `res_01 <- syrup(Sys.sleep(1), interval = 0.01)` to run without any errors. i Actually got a <rlang_error> with text: Unable to retrieve resource usage results from the temporary session. i This is an internal error that was detected in the syrup package. Please report it at <https://github.com/simonpcouch/syrup/issues> with a reprex (<https://tidyverse.org/help/>) and the full backtrace. ── Failure ('test-syrup.R:52:3'): syrup(interval) works ──────────────────────── Expected `res_1 <- syrup(Sys.sleep(1), interval = 0.1)` to run without any errors. i Actually got a <rlang_error> with text: Unable to retrieve resource usage results from the temporary session. i This is an internal error that was detected in the syrup package. Please report it at <https://github.com/simonpcouch/syrup/issues> with a reprex (<https://tidyverse.org/help/>) and the full backtrace. ── Error ('test-syrup.R:59:3'): syrup(interval) works ────────────────────────── Error in `eval(code, test_env)`: object 'res_01' not found Backtrace: ▆ 1. └─testthat::expect_s3_class(res_01, "tbl_df") at test-syrup.R:59:3 2. └─testthat::quasi_label(enquo(object), arg = "object") 3. └─rlang::eval_bare(expr, quo_get_env(quo)) [ FAIL 7 | WARN 0 | SKIP 2 | PASS 1 ] Error: Test failures Execution halted Flavor: r-devel-linux-x86_64-fedora-clang

Version: 0.1.1
Check: tests
Result: ERROR Running ‘testthat.R’ [13s/20s] 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/testing-design.html#sec-tests-files-overview > # * https://testthat.r-lib.org/articles/special-files.html > > library(testthat) > library(syrup) Loading required package: bench > > test_check("syrup") [ FAIL 2 | WARN 2 | SKIP 2 | PASS 16 ] ══ Skipped tests (2) ═══════════════════════════════════════════════════════════ • On CRAN (2): 'test-syrup.R:70:3', 'test-syrup.R:76:3' ══ Failed tests ════════════════════════════════════════════════════════════════ ── Failure ('test-syrup.R:45:3'): syrup(interval) works ──────────────────────── Expected `res_01 <- syrup(Sys.sleep(1), interval = 0.01)` to run without any errors. i Actually got a <rlang_error> with text: Unable to retrieve resource usage results from the temporary session. i This is an internal error that was detected in the syrup package. Please report it at <https://github.com/simonpcouch/syrup/issues> with a reprex (<https://tidyverse.org/help/>) and the full backtrace. ── Error ('test-syrup.R:59:3'): syrup(interval) works ────────────────────────── Error in `eval(code, test_env)`: object 'res_01' not found Backtrace: ▆ 1. └─testthat::expect_s3_class(res_01, "tbl_df") at test-syrup.R:59:3 2. └─testthat::quasi_label(enquo(object), arg = "object") 3. └─rlang::eval_bare(expr, quo_get_env(quo)) [ FAIL 2 | WARN 2 | SKIP 2 | PASS 16 ] Error: Test failures Execution halted Flavor: r-devel-linux-x86_64-fedora-gcc

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.
Health stats visible at Monitor.