CRAN Package Check Results for Package subprocess

Last updated on 2020-01-20 02:47:41 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 0.8.3 7.27 29.70 36.97 WARN
r-devel-linux-x86_64-debian-gcc 0.8.3 4.73 23.97 28.70 WARN
r-devel-linux-x86_64-fedora-clang 0.8.3 49.78 WARN
r-devel-linux-x86_64-fedora-gcc 0.8.3 45.50 WARN
r-devel-windows-ix86+x86_64 0.8.3 43.00 0.00 43.00 FAIL
r-devel-windows-ix86+x86_64-gcc8 0.8.3 34.00 344.00 378.00 ERROR
r-patched-linux-x86_64 0.8.3 5.22 27.37 32.59 WARN
r-patched-solaris-x86 0.8.3 68.30 ERROR
r-release-linux-x86_64 0.8.3 5.44 27.08 32.52 WARN
r-release-windows-ix86+x86_64 0.8.3 49.00 75.00 124.00 ERROR
r-release-osx-x86_64 0.8.3 OK
r-oldrel-windows-ix86+x86_64 0.8.3 28.00 66.00 94.00 ERROR
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:
     sub-linux.cc:362:28: warning: designated initializers are a C99 feature [-Wc99-extensions]
     sub-linux.cc:362:42: warning: designated initializers are a C99 feature [-Wc99-extensions]
Flavors: r-devel-linux-x86_64-debian-clang, r-devel-linux-x86_64-fedora-clang

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=]
     sub-linux.cc:362:28: warning: C++ designated initializers only available with ‘-std=c++2a’ or ‘-std=gnu++2a’ [-Wpedantic]
     sub-linux.cc:362:42: warning: C++ designated initializers only available with ‘-std=c++2a’ or ‘-std=gnu++2a’ [-Wpedantic]
Flavors: r-devel-linux-x86_64-debian-gcc, r-devel-linux-x86_64-fedora-gcc

Version: 0.8.3
Check: running tests for arch ‘i386’
Result: ERROR
     Running 'testthat.R' [18s]
    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
     Backtrace:
     1. testthat::expect_true(process_exists(child_id))
     4. subprocess::process_exists(child_id)
     5. base::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: FAIL
    Check process probably crashed or hung up for 20 minutes ... killed
    Most likely this happened in the example checks (?),
    if not, ignore the following last lines of example output:
    
    ======== End of example output (where/before crash/hang up occured ?) ========
Flavor: r-devel-windows-ix86+x86_64

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-windows-ix86+x86_64-gcc8, 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' [135s]
    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
     Backtrace:
     1. testthat::expect_true(process_exists(child_id))
     4. subprocess::process_exists(child_id)
     5. base::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-gcc8

Version: 0.8.3
Check: running tests for arch ‘x64’
Result: ERROR
     Running 'testthat.R' [135s]
    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
     Backtrace:
     1. testthat::expect_true(process_exists(child_id))
     4. subprocess::process_exists(child_id)
     5. base::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-gcc8

Version: 0.8.3
Check: tests
Result: ERROR
     Running ‘testthat.R’ [16s/20s]
    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. Error: child process is terminated in Linux/MacOS/SunOS (@test-termination
     `pid` must be a single integer value
     Backtrace:
     1. testthat::expect_true(wait_until_appears(child_id))
     4. subprocess:::wait_until_appears(child_id)
     5. subprocess::process_exists(handle) /home/ripley/R/packages/tests32/subprocess.Rcheck/tests/helper-processes.R:44:2
     6. base::isTRUE(.Call("C_process_exists", as.integer(x)))
    
     ── 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
     Backtrace:
     1. testthat::expect_equal(...)
     4. subprocess::process_read(handle1, timeout = TIMEOUT_INFINITE)
    
     ══ testthat results ═══════════════════════════════════════════════════════════
     [ OK: 70 | SKIPPED: 2 | WARNINGS: 4 | FAILED: 3 ]
     1. Error: child process is terminated in Linux/MacOS/SunOS (@test-termination.R#85)
     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

Version: 0.8.3
Check: running tests for arch ‘i386’
Result: ERROR
     Running 'testthat.R' [11s]
    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
     Backtrace:
     1. testthat::expect_true(process_exists(child_id))
     4. subprocess::process_exists(child_id)
     5. base::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-release-windows-ix86+x86_64

Version: 0.8.3
Check: running tests for arch ‘x64’
Result: ERROR
     Running 'testthat.R' [11s]
    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
     Backtrace:
     1. testthat::expect_true(process_exists(child_id))
     4. subprocess::process_exists(child_id)
     5. base::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-release-windows-ix86+x86_64

Version: 0.8.3
Check: running tests for arch ‘i386’
Result: ERROR
     Running 'testthat.R' [10s]
    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
     Backtrace:
     1. testthat::expect_true(process_exists(child_id))
     4. subprocess::process_exists(child_id)
     5. base::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-oldrel-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
     Backtrace:
     1. testthat::expect_true(process_exists(child_id))
     4. subprocess::process_exists(child_id)
     5. base::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-oldrel-windows-ix86+x86_64