CRAN Package Check Results for Package subprocess

Last updated on 2019-09-15 15:47:36 CEST.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.8.3 6.52 27.14 33.66 OK
r-devel-linux-x86_64-debian-gcc 0.8.3 5.01 22.24 27.25 WARN
r-devel-linux-x86_64-fedora-clang 0.8.3 45.49 OK
r-devel-linux-x86_64-fedora-gcc 0.8.3 43.15 WARN
r-devel-windows-ix86+x86_64 0.8.3 42.00 68.00 110.00 ERROR
r-patched-linux-x86_64 0.8.3 5.04 27.20 32.24 WARN
r-patched-solaris-x86 0.8.3 62.30 ERROR
r-release-linux-x86_64 0.8.3 5.33 27.46 32.79 WARN
r-release-windows-ix86+x86_64 0.8.3 28.00 0.00 28.00 OK
r-release-osx-x86_64 0.8.3 OK
r-oldrel-windows-ix86+x86_64 0.8.3 45.00 66.00 111.00 OK
r-oldrel-osx-x86_64 0.8.3 OK

Check Details

Version: 0.8.3
Check: whether package can be installed
Result: WARN
    Found the following significant warnings:
     rapi.cc:191:12: warning: catching polymorphic type ‘struct subprocess::subprocess_exception’ by value [-Wcatch-value=]
Flavors: r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-gcc, r-patched-linux-x86_64, r-release-linux-x86_64

Version: 0.8.3
Check: running tests for arch ‘i386’
Result: ERROR
     Running 'testthat.R' [9s]
    Running the tests in 'tests/testthat.R' failed.
    Complete output:
     > library(testthat)
     > library(subprocess)
     >
     > # See for more details:
     > # https://github.com/hadley/testthat/issues/144
     > # https://github.com/hadley/testthat/issues/86
     > # https://github.com/luckyrandom/cmaker/commit/b85813ac2b7aef69932eca8fbb4fa0ec225e0af0
     > #
     > # When R CMD check runs tests, it sets R_TESTS. When the tests
     > # themeselves run R CMD xxxx, as is the case with the tests in
     > # devtools, having R_TESTS set causes errors because it confuses
     > # the R subprocesses. Unsetting it here avoids those problems.
     > #
     > # We need this because we spawn child R processes and they get very
     > # confused if this variable (R_TESTS) is present in their environment.
     > Sys.setenv("R_TESTS" = "")
     >
     > test_check("subprocess")
     Keine Instanzen verf<c2><81>gbar.
     -- 1. Failure: child process is terminated in Windows (@test-termination.R#33)
     `child_id` has length 0, not length 1.
    
     -- 2. Error: child process is terminated in Windows (@test-termination.R#34) --
     `pid` must be a single integer value
     1: expect_true(process_exists(child_id)) at testthat/test-termination.R:34
     2: quasi_label(enquo(object), label, arg = "object")
     3: eval_bare(get_expr(quo), get_env(quo))
     4: process_exists(child_id)
     5: isTRUE(.Call("C_process_exists", as.integer(x)))
    
     == testthat results ===========================================================
     [ OK: 58 | SKIPPED: 3 | WARNINGS: 0 | FAILED: 2 ]
     1. Failure: child process is terminated in Windows (@test-termination.R#33)
     2. Error: child process is terminated in Windows (@test-termination.R#34)
    
     Error: testthat unit tests failed
     Execution halted
Flavor: r-devel-windows-ix86+x86_64

Version: 0.8.3
Check: running tests for arch ‘x64’
Result: ERROR
     Running 'testthat.R' [9s]
    Running the tests in 'tests/testthat.R' failed.
    Complete output:
     > library(testthat)
     > library(subprocess)
     >
     > # See for more details:
     > # https://github.com/hadley/testthat/issues/144
     > # https://github.com/hadley/testthat/issues/86
     > # https://github.com/luckyrandom/cmaker/commit/b85813ac2b7aef69932eca8fbb4fa0ec225e0af0
     > #
     > # When R CMD check runs tests, it sets R_TESTS. When the tests
     > # themeselves run R CMD xxxx, as is the case with the tests in
     > # devtools, having R_TESTS set causes errors because it confuses
     > # the R subprocesses. Unsetting it here avoids those problems.
     > #
     > # We need this because we spawn child R processes and they get very
     > # confused if this variable (R_TESTS) is present in their environment.
     > Sys.setenv("R_TESTS" = "")
     >
     > test_check("subprocess")
     Keine Instanzen verf<c2><81>gbar.
     -- 1. Failure: child process is terminated in Windows (@test-termination.R#33)
     `child_id` has length 0, not length 1.
    
     -- 2. Error: child process is terminated in Windows (@test-termination.R#34) --
     `pid` must be a single integer value
     1: expect_true(process_exists(child_id)) at testthat/test-termination.R:34
     2: quasi_label(enquo(object), label, arg = "object")
     3: eval_bare(get_expr(quo), get_env(quo))
     4: process_exists(child_id)
     5: isTRUE(.Call("C_process_exists", as.integer(x)))
    
     == testthat results ===========================================================
     [ OK: 58 | SKIPPED: 3 | WARNINGS: 0 | FAILED: 2 ]
     1. Failure: child process is terminated in Windows (@test-termination.R#33)
     2. Error: child process is terminated in Windows (@test-termination.R#34)
    
     Error: testthat unit tests failed
     Execution halted
Flavor: r-devel-windows-ix86+x86_64

Version: 0.8.3
Check: tests
Result: ERROR
     Running ‘testthat.R’ [0m/160m]
    Running the tests in ‘tests/testthat.R’ failed.
    Complete output:
     > library(testthat)
     > library(subprocess)
     >
     > # See for more details:
     > # https://github.com/hadley/testthat/issues/144
     > # https://github.com/hadley/testthat/issues/86
     > # https://github.com/luckyrandom/cmaker/commit/b85813ac2b7aef69932eca8fbb4fa0ec225e0af0
     > #
     > # When R CMD check runs tests, it sets R_TESTS. When the tests
     > # themeselves run R CMD xxxx, as is the case with the tests in
     > # devtools, having R_TESTS set causes errors because it confuses
     > # the R subprocesses. Unsetting it here avoids those problems.
     > #
     > # We need this because we spawn child R processes and they get very
     > # confused if this variable (R_TESTS) is present in their environment.
     > Sys.setenv("R_TESTS" = "")
     >
     > test_check("subprocess")
     ── 1. Failure: sending signal in Linux/MacOS/Solaris (@test-signals.R#29) ─────
     `output` not equal to names(signals)[[i]].
     Lengths differ: 2 is not 1
     SIGTSTP
    
     ── 2. Failure: C tests pass (@test-utf8.R#4) ──────────────────────────────────
     C_tests_utf8() not equal to "All C tests passed!".
     1/1 mismatches
     x[1]: "1 error(s) encountered in C tests, see warnings() for details"
     y[1]: "All C tests passed!"
    
     ── 3. Error: multi-byte can come in parts (@test-utf8.R#23) ───────────────────
     malformed multibyte string: I/O error
     1: expect_equal(process_read(handle1, timeout = TIMEOUT_INFINITE)$stdout, "\xf0\U00010350") at testthat/test-utf8.R:23
     2: quasi_label(enquo(object), label, arg = "object")
     3: eval_bare(get_expr(quo), get_env(quo))
     4: process_read(handle1, timeout = TIMEOUT_INFINITE)
    
     ══ testthat results ═══════════════════════════════════════════════════════════
     [ OK: 75 | SKIPPED: 2 | WARNINGS: 3 | FAILED: 3 ]
     1. Failure: sending signal in Linux/MacOS/Solaris (@test-signals.R#29)
     2. Failure: C tests pass (@test-utf8.R#4)
     3. Error: multi-byte can come in parts (@test-utf8.R#23)
    
     Error: testthat unit tests failed
     Execution halted
Flavor: r-patched-solaris-x86