• using R Under development (unstable) (2026-07-24 r90297)
• using platform: x86_64-pc-linux-gnu
• R was compiled by     clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)     flang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
• running under: Fedora Linux 42 (Workstation Edition)
• using session charset: UTF-8 * current time: 2026-07-25 07:06:05 UTC
• using option ‘--no-stop-on-test-error’
• checking for file ‘dbi.table/DESCRIPTION’ ... OK
• checking extension type ... Package
• this is package ‘dbi.table’ version ‘1.0.7’
• package encoding: UTF-8
• checking package namespace information ... OK
• checking package dependencies ... OK
• checking if this is a source package ... OK
• checking if there is a namespace ... OK
• checking for executable files ... OK
• checking for hidden files and directories ... OK
• checking for portable file names ... OK
• checking for sufficient/correct file permissions ... OK
• checking whether package ‘dbi.table’ can be installed ... [9s/11s] OK See the install log for details.
• checking installed package size ... OK
• checking package directory ... OK
• checking ‘build’ directory ... OK
• checking DESCRIPTION meta-information ... OK
• checking top-level files ... OK
• checking for left-over files ... OK
• checking index information ... OK
• checking package subdirectories ... OK
• checking code files for non-ASCII characters ... OK
• checking R files for syntax errors ... OK
• checking whether the package can be loaded ... OK
• checking whether the package can be loaded with stated dependencies ... OK
• checking whether the package can be unloaded cleanly ... OK
• checking whether the namespace can be loaded with stated dependencies ... OK
• checking whether the namespace can be unloaded cleanly ... OK
• checking loading without being on the library search path ... OK
• checking use of S3 registration ... OK
• checking dependencies in R code ... OK
• checking S3 generic/method consistency ... OK
• checking replacement functions ... OK
• checking foreign function calls ... OK
• checking R code for possible problems ... [19s/28s] OK
• checking Rd files ... OK
• checking Rd metadata ... OK
• checking Rd line widths ... OK
• checking Rd cross-references ... OK
• checking for missing documentation entries ... OK
• checking for code/documentation mismatches ... OK
• checking Rd \usage sections ... OK
• checking Rd contents ... OK
• checking for unstated dependencies in examples ... OK
• checking installed files from ‘inst/doc’ ... OK
• checking files in ‘vignettes’ ... OK
• checking examples ... [18s/39s] OK
• checking for unstated dependencies in ‘tests’ ... OK
• checking tests ... [146s/224s] 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
• checking for unstated dependencies in vignettes ... OK
• checking package vignettes ... OK
• checking re-building of vignette outputs ... [14s/17s] OK
• checking PDF version of manual ... OK
• checking HTML version of manual ... OK
• checking for non-standard things in the check directory ... OK
• checking for detritus in the temp directory ... OK
• DONE

Status: 1 ERROR