CRAN Package Check Results for Package dbi.table

Last updated on 2026-07-26 05:50:17 CEST.

Flavor	Version	Tinstall	Tcheck	Ttotal	Status	Flags
r-devel-linux-x86_64-debian-clang	1.0.7	5.64	151.39	157.03	OK
r-devel-linux-x86_64-debian-gcc	1.0.7	4.42	106.50	110.92	OK
r-devel-linux-x86_64-fedora-clang	1.0.7	9.00	242.47	251.47	ERROR
r-devel-linux-x86_64-fedora-gcc	1.0.7			107.23	OK
r-devel-windows-x86_64	1.0.7	8.00	140.00	148.00	OK
r-patched-linux-x86_64	1.0.7	5.68	145.16	150.84	OK
r-release-linux-x86_64	1.0.7	5.00	145.42	150.42	OK
r-release-macos-arm64	1.0.7	1.00	33.00	34.00	OK
r-release-macos-x86_64	1.0.7	4.00	156.00	160.00	OK
r-release-windows-x86_64	1.0.7	8.00	140.00	148.00	OK
r-oldrel-macos-arm64	1.0.7	1.00	33.00	34.00	OK
r-oldrel-macos-x86_64	1.0.7	4.00	230.00	234.00	OK
r-oldrel-windows-x86_64	1.0.7	10.00	210.00	220.00	OK

Check Details

Version: 1.0.7
Check: tests
Result: ERROR Running ‘testthat.R’ [145s/224s] 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(dbi.table) > > test_check("dbi.table") Attaching package: 'data.table' The following object is masked from 'package:base': %notin% duckdb keeps downloaded extensions and secrets in a temporary directory: ℹ /tmp/Rtmpvr4Uce/working_dir/RtmpPoRAkp/duckdb This is removed when the R session ends. • Extensions are re-downloaded each session. • Secrets are lost. ℹ Run duckdb(shared_home = TRUE) (or create ~/.duckdb) to keep them (suitable for most users). ℹ Run duckdb(shared_home = FALSE) to accept the temporary directory (and silence this message). ℹ See ?duckdb_storage for details and alternatives. duckdb was built with libc++ (not libstdc++) on Linux, so DuckDB extensions are disabled: • Loading a prebuilt (libstdc++) extension could crash R (https://github.com/duckdb/duckdb-r/issues/1107). • INSTALL/LOAD of an extension will error, and automatic extension loading is off. ℹ Pass duckdb(allow_extensions = FALSE) to accept this and silence this message. ℹ Pass duckdb(allow_extensions = TRUE) to attempt loading anyway (may crash R). ℹ See ?duckdb for details. duckdb was built with libc++ (not libstdc++) on Linux, so DuckDB extensions are disabled: • Loading a prebuilt (libstdc++) extension could crash R (https://github.com/duckdb/duckdb-r/issues/1107). • INSTALL/LOAD of an extension will error, and automatic extension loading is off. ℹ Pass duckdb(allow_extensions = FALSE) to accept this and silence this message. ℹ Pass duckdb(allow_extensions = TRUE) to attempt loading anyway (may crash R). ℹ See ?duckdb for details. duckdb keeps downloaded extensions and secrets in a temporary directory: ℹ /tmp/Rtmpvr4Uce/working_dir/RtmpPoRAkp/duckdb This is removed when the R session ends. • Extensions are re-downloaded each session. • Secrets are lost. ℹ Run duckdb(shared_home = TRUE) (or create ~/.duckdb) to keep them (suitable for most users). ℹ Run duckdb(shared_home = FALSE) to accept the temporary directory (and silence this message). ℹ See ?duckdb_storage for details and alternatives. duckdb was built with libc++ (not libstdc++) on Linux, so DuckDB extensions are disabled: • Loading a prebuilt (libstdc++) extension could crash R (https://github.com/duckdb/duckdb-r/issues/1107). • INSTALL/LOAD of an extension will error, and automatic extension loading is off. ℹ Pass duckdb(allow_extensions = FALSE) to accept this and silence this message. ℹ Pass duckdb(allow_extensions = TRUE) to attempt loading anyway (may crash R). ℹ See ?duckdb for details. duckdb keeps downloaded extensions and secrets in a temporary directory: i /tmp/Rtmpvr4Uce/working_dir/RtmpPoRAkp/duckdb This is removed when the R session ends. * Extensions are re-downloaded each session. * Secrets are lost. i Run duckdb(shared_home = TRUE) (or create ~/.duckdb) to keep them (suitable for most users). i Run duckdb(shared_home = FALSE) to accept the temporary directory (and silence this message). i See ?duckdb_storage for details and alternatives. duckdb was built with libc++ (not libstdc++) on Linux, so DuckDB extensions are disabled: * Loading a prebuilt (libstdc++) extension could crash R (https://github.com/duckdb/duckdb-r/issues/1107). * INSTALL/LOAD of an extension will error, and automatic extension loading is off. i Pass duckdb(allow_extensions = FALSE) to accept this and silence this message. i Pass duckdb(allow_extensions = TRUE) to attempt loading anyway (may crash R). i See ?duckdb for details. duckdb was built with libc++ (not libstdc++) on Linux, so DuckDB extensions are disabled: * Loading a prebuilt (libstdc++) extension could crash R (https://github.com/duckdb/duckdb-r/issues/1107). * INSTALL/LOAD of an extension will error, and automatic extension loading is off. i Pass duckdb(allow_extensions = FALSE) to accept this and silence this message. i Pass duckdb(allow_extensions = TRUE) to attempt loading anyway (may crash R). i See ?duckdb for details. Saving _problems/test-DBI-methods-80.R Saving _problems/test-DBI-methods-84.R Saving _problems/test-DBI-methods-88.R duckdb keeps downloaded extensions and secrets in a temporary directory: i /tmp/Rtmpvr4Uce/working_dir/RtmpPoRAkp/duckdb This is removed when the R session ends. * Extensions are re-downloaded each session. * Secrets are lost. i Run duckdb(shared_home = TRUE) (or create ~/.duckdb) to keep them (suitable for most users). i Run duckdb(shared_home = FALSE) to accept the temporary directory (and silence this message). i See ?duckdb_storage for details and alternatives. duckdb was built with libc++ (not libstdc++) on Linux, so DuckDB extensions are disabled: * Loading a prebuilt (libstdc++) extension could crash R (https://github.com/duckdb/duckdb-r/issues/1107). * INSTALL/LOAD of an extension will error, and automatic extension loading is off. i Pass duckdb(allow_extensions = FALSE) to accept this and silence this message. i Pass duckdb(allow_extensions = TRUE) to attempt loading anyway (may crash R). i See ?duckdb for details. duckdb was built with libc++ (not libstdc++) on Linux, so DuckDB extensions are disabled: * Loading a prebuilt (libstdc++) extension could crash R (https://github.com/duckdb/duckdb-r/issues/1107). * INSTALL/LOAD of an extension will error, and automatic extension loading is off. i Pass duckdb(allow_extensions = FALSE) to accept this and silence this message. i Pass duckdb(allow_extensions = TRUE) to attempt loading anyway (may crash R). i See ?duckdb for details. duckdb keeps downloaded extensions and secrets in a temporary directory: i /tmp/Rtmpvr4Uce/working_dir/RtmpPoRAkp/duckdb This is removed when the R session ends. * Extensions are re-downloaded each session. * Secrets are lost. i Run duckdb(shared_home = TRUE) (or create ~/.duckdb) to keep them (suitable for most users). i Run duckdb(shared_home = FALSE) to accept the temporary directory (and silence this message). i See ?duckdb_storage for details and alternatives. duckdb was built with libc++ (not libstdc++) on Linux, so DuckDB extensions are disabled: * Loading a prebuilt (libstdc++) extension could crash R (https://github.com/duckdb/duckdb-r/issues/1107). * INSTALL/LOAD of an extension will error, and automatic extension loading is off. i Pass duckdb(allow_extensions = FALSE) to accept this and silence this message. i Pass duckdb(allow_extensions = TRUE) to attempt loading anyway (may crash R). i See ?duckdb for details. duckdb was built with libc++ (not libstdc++) on Linux, so DuckDB extensions are disabled: * Loading a prebuilt (libstdc++) extension could crash R (https://github.com/duckdb/duckdb-r/issues/1107). * INSTALL/LOAD of an extension will error, and automatic extension loading is off. i Pass duckdb(allow_extensions = FALSE) to accept this and silence this message. i Pass duckdb(allow_extensions = TRUE) to attempt loading anyway (may crash R). i See ?duckdb for details. [ FAIL 3 | WARN 0 | SKIP 2 | PASS 421 ] ══ Skipped tests (2) ═══════════════════════════════════════════════════════════ • On CRAN (2): 'test-mariadb.R:10:3', 'test-postgres.R:11:3' ══ Failed tests ════════════════════════════════════════════════════════════════ ── Failure ('test-DBI-methods.R:78:3'): DBI::dbExecute works ─────────────────── Expected `{ ... }` not to throw any errors. Actually got a <rlang_error> with message: DuckDB extension loading (INSTALL / LOAD) is disabled for this driver. i Recreate the driver with duckdb(allow_extensions = TRUE) to enable it (this may crash R on a Linux build not compiled with libstdc++; see https://github.com/duckdb/duckdb-r/issues/1107). i See ?duckdb for details. i Context: load_extension ── Failure ('test-DBI-methods.R:82:3'): DBI::dbExecute works ─────────────────── Expected `{ ... }` not to throw any errors. Actually got a <rlang_error> with message: DuckDB extension loading (INSTALL / LOAD) is disabled for this driver. i Recreate the driver with duckdb(allow_extensions = TRUE) to enable it (this may crash R on a Linux build not compiled with libstdc++; see https://github.com/duckdb/duckdb-r/issues/1107). i See ?duckdb for details. i Context: load_extension ── Failure ('test-DBI-methods.R:86:3'): DBI::dbExecute works ─────────────────── Expected `{ ... }` not to throw any errors. Actually got a <rlang_error> with message: DuckDB extension loading (INSTALL / LOAD) is disabled for this driver. i Recreate the driver with duckdb(allow_extensions = TRUE) to enable it (this may crash R on a Linux build not compiled with libstdc++; see https://github.com/duckdb/duckdb-r/issues/1107). i See ?duckdb for details. i Context: load_extension [ FAIL 3 | WARN 0 | SKIP 2 | PASS 421 ] Error: ! Test failures. Execution halted Flavor: r-devel-linux-x86_64-fedora-clang