CRAN Package Check Results for Package fiery

Last updated on 2025-11-11 00:50:05 CET.

Flavor Version Tinstall Tcheck Ttotal Status Flags
r-devel-linux-x86_64-debian-clang 1.3.0 10.64 79.57 90.21 OK
r-devel-linux-x86_64-debian-gcc 1.3.0 7.13 59.70 66.83 OK
r-devel-linux-x86_64-fedora-clang 1.4.0 43.00 94.52 137.52 ERROR
r-devel-linux-x86_64-fedora-gcc 1.4.0 22.00 120.17 142.17 OK
r-devel-windows-x86_64 1.3.0 14.00 105.00 119.00 ERROR
r-patched-linux-x86_64 1.3.0 11.10 75.63 86.73 OK
r-release-linux-x86_64 1.3.0 9.98 75.75 85.73 OK
r-release-macos-arm64 1.4.0 4.00 56.00 60.00 OK
r-release-macos-x86_64 1.4.0 23.00 127.00 150.00 OK
r-release-windows-x86_64 1.3.0 11.00 104.00 115.00 OK
r-oldrel-macos-arm64 1.4.0 5.00 67.00 72.00 OK
r-oldrel-macos-x86_64 1.4.0 11.00 122.00 133.00 OK
r-oldrel-windows-x86_64 1.3.0 16.00 123.00 139.00 OK

Check Details

Version: 1.4.0
Check: tests
Result: ERROR Running ‘testthat.R’ [44s/126s] 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 > > library(testthat) > library(fiery) > > test_check("fiery") [ FAIL 1 | WARN 0 | SKIP 29 | PASS 111 ] ══ Skipped tests (29) ══════════════════════════════════════════════════════════ • On CRAN (29): 'test-Fire.R:25:3', 'test-Fire.R:36:3', 'test-Fire.R:73:5', 'test-Fire.R:84:3', 'test-Fire.R:103:3', 'test-Fire.R:149:3', 'test-Fire.R:161:3', 'test-Fire.R:364:3', 'test-Fire.R:396:3', 'test-Fire.R:501:3', 'test-Fire.R:525:3', 'test-Fire.R:541:3', 'test-Fire.R:566:3', 'test-Fire.R:611:3', 'test-Fire.R:644:3', 'test-Fire.R:665:3', 'test-Fire.R:679:3', 'test-Fire.R:689:3', 'test-Fire.R:728:3', 'test-Fire.R:754:3', 'test-Fire.R:777:3', 'test-HandlerStack.R:60:3', 'test-PromiseStack.R:18:3', 'test-PromiseStack.R:64:3', 'test-fake_request.R:52:3', 'test-fake_request.R:74:3', 'test-loggers.R:4:3', 'test-loggers.R:55:3', 'test-loggers.R:73:3' ══ Failed tests ════════════════════════════════════════════════════════════════ ── Error ('test-loggers.R:14:3'): console logger works ───────────────────────── Error in `stdout()`: invalid connection Backtrace: ▆ 1. └─testthat::expect_snapshot(rs(logger("error", "error test"))) at test-loggers.R:14:3 2. └─rlang::cnd_signal(state$error) [ FAIL 1 | WARN 0 | SKIP 29 | PASS 111 ] Error: Test failures Execution halted Flavor: r-devel-linux-x86_64-fedora-clang

Version: 1.3.0
Check: tests
Result: ERROR Running 'testthat.R' [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/tests.html > # * https://testthat.r-lib.org/reference/test_package.html#special-files > > library(testthat) > library(fiery) > > test_check("fiery") [ FAIL 1 | WARN 0 | SKIP 29 | PASS 111 ] ══ Skipped tests (29) ══════════════════════════════════════════════════════════ • On CRAN (28): 'test-Fire.R:25:5', 'test-Fire.R:56:9', 'test-Fire.R:67:5', 'test-Fire.R:86:5', 'test-Fire.R:126:5', 'test-Fire.R:133:5', 'test-Fire.R:310:5', 'test-Fire.R:339:5', 'test-Fire.R:427:5', 'test-Fire.R:451:5', 'test-Fire.R:465:5', 'test-Fire.R:482:5', 'test-Fire.R:512:5', 'test-Fire.R:549:5', 'test-Fire.R:565:5', 'test-Fire.R:579:5', 'test-Fire.R:589:5', 'test-Fire.R:628:5', 'test-Fire.R:654:5', 'test-Fire.R:677:5', 'test-HandlerStack.R:60:5', 'test-PromiseStack.R:13:5', 'test-PromiseStack.R:53:5', 'test-fake_request.R:49:5', 'test-fake_request.R:62:5', 'test-loggers.R:4:5', 'test-loggers.R:46:5', 'test-loggers.R:64:5' • On Windows (1): 'test-Fire.R:30:5' ══ Failed tests ════════════════════════════════════════════════════════════════ ── Error ('test-loggers.R:14:5'): console logger works ───────────────────────── Error in `stdout()`: invalid connection Backtrace: ▆ 1. └─testthat::expect_snapshot(rs(logger("error", "error test"))) at test-loggers.R:14:5 2. └─rlang::cnd_signal(state$error) [ FAIL 1 | WARN 0 | SKIP 29 | PASS 111 ] Error: Test failures Execution halted Flavor: r-devel-windows-x86_64