Last updated on 2026-07-26 11:50:01 CEST.
| Flavor | Version | Tinstall | Tcheck | Ttotal | Status | Flags |
|---|---|---|---|---|---|---|
| r-devel-linux-x86_64-debian-clang | 0.2.1 | 3.53 | 56.91 | 60.44 | OK | |
| r-devel-linux-x86_64-debian-gcc | 0.2.1 | 2.29 | 42.19 | 44.48 | OK | |
| r-devel-linux-x86_64-fedora-clang | 0.2.1 | 85.72 | ERROR | |||
| r-devel-linux-x86_64-fedora-gcc | 0.2.1 | 37.30 | OK | |||
| r-devel-windows-x86_64 | 0.2.1 | 5.00 | 80.00 | 85.00 | OK | |
| r-patched-linux-x86_64 | 0.2.1 | 4.40 | 51.51 | 55.91 | OK | |
| r-release-linux-x86_64 | 0.2.1 | 3.53 | 51.56 | 55.09 | OK | |
| r-release-macos-arm64 | 0.2.1 | 1.00 | 26.00 | 27.00 | OK | |
| r-release-macos-x86_64 | 0.2.1 | 3.00 | 96.00 | 99.00 | OK | |
| r-release-windows-x86_64 | 0.2.1 | 6.00 | 87.00 | 93.00 | OK | |
| r-oldrel-macos-arm64 | 0.2.1 | 1.00 | 21.00 | 22.00 | OK | |
| r-oldrel-macos-x86_64 | 0.2.1 | 3.00 | 97.00 | 100.00 | OK | |
| r-oldrel-windows-x86_64 | 0.2.1 | 8.00 | 99.00 | 107.00 | OK |
Version: 0.2.1
Check: tests
Result: ERROR
Running ‘testthat.R’ [25s/35s]
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(motherduck)
> library(DBI)
> library(openxlsx)
>
> test_check("motherduck")
duckdb keeps downloaded extensions and secrets in a temporary directory:
i /tmp/RtmpEniUfn/working_dir/RtmpuzOsbq/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.
-- Status: ---------------------------------------------------------------------
-- Connection Status Report: --
! You are not connected to MotherDuck
-- User Report: --
* User Name: "duckdb"
* Role: "duckdb"
-- Catalog Report: --
* Current Database: "memory"
* Current Schema: "main"
* # Total Catalogs you have access to: 3
* # Total Tables you have access to: 0
* # Total Shares you have access to: 0
* # Tables in this catalog you have access to: 0
* # Tables in this catalog & schema you have access to: 0
-- Action Report: --
v Inserted into existing database "memory"
v Created new schema "test_schema"
> Current role: `duckdb`
-- Status: ---------------------------------------------------------------------
-- User Report: --
* User Name: "duckdb"
* Role: "duckdb"
-- Catalog Report: --
* Current Database: "memory"
* Current Schema: "test_schema"
* # Total Catalogs you have access to: 3
* # Total Tables you have access to: 0
* # Total Shares you have access to: 0
* # Tables in this catalog you have access to: 0
* # Tables in this catalog & schema you have access to: 0
> Current role: `duckdb`
duckdb keeps downloaded extensions and secrets in a temporary directory:
i /tmp/RtmpEniUfn/working_dir/RtmpuzOsbq/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 keeps downloaded extensions and secrets in a temporary directory:
i /tmp/RtmpEniUfn/working_dir/RtmpuzOsbq/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 keeps downloaded extensions and secrets in a temporary directory:
i /tmp/RtmpEniUfn/working_dir/RtmpuzOsbq/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.
> Current role: `duckdb`
duckdb keeps downloaded extensions and secrets in a temporary directory:
i /tmp/RtmpEniUfn/working_dir/RtmpuzOsbq/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.
> Current role: `duckdb`
duckdb keeps downloaded extensions and secrets in a temporary directory:
i /tmp/RtmpEniUfn/working_dir/RtmpuzOsbq/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.
-- Status: ---------------------------------------------------------------------
-- Connection Status Report: --
! You are not connected to MotherDuck
-- User Report: --
* User Name: "duckdb"
* Role: "duckdb"
-- Catalog Report: --
* Current Database: "memory"
* Current Schema: "main"
* # Total Catalogs you have access to: 3
* # Total Tables you have access to: 1
* # Total Shares you have access to: 0
* # Tables in this catalog you have access to: 1
* # Tables in this catalog & schema you have access to: 1
-- Action Report: --
v Inserted into existing database "memory"
v Using existing schema "main"
duckdb keeps downloaded extensions and secrets in a temporary directory:
i /tmp/RtmpEniUfn/working_dir/RtmpuzOsbq/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.
-- Status: ---------------------------------------------------------------------
-- Connection Status Report: --
! You are not connected to MotherDuck
-- User Report: --
* User Name: "duckdb"
* Role: "duckdb"
-- Catalog Report: --
* Current Database: "memory"
* Current Schema: "main"
* # Total Catalogs you have access to: 3
* # Total Tables you have access to: 1
* # Total Shares you have access to: 0
* # Tables in this catalog you have access to: 1
* # Tables in this catalog & schema you have access to: 1
-- Action Report: --
v Inserted into existing database "memory"
v Using existing schema "main"
duckdb keeps downloaded extensions and secrets in a temporary directory:
i /tmp/RtmpEniUfn/working_dir/RtmpuzOsbq/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.
-- Status: ---------------------------------------------------------------------
-- Connection Status Report: --
! You are not connected to MotherDuck
-- User Report: --
* User Name: "duckdb"
* Role: "duckdb"
-- Catalog Report: --
* Current Database: "memory"
* Current Schema: "main"
* # Total Catalogs you have access to: 3
* # Total Tables you have access to: 1
* # Total Shares you have access to: 0
* # Tables in this catalog you have access to: 1
* # Tables in this catalog & schema you have access to: 1
-- Action Report: --
v Inserted into existing database "memory"
v Using existing schema "main"
duckdb keeps downloaded extensions and secrets in a temporary directory:
i /tmp/RtmpEniUfn/working_dir/RtmpuzOsbq/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.
-- Status: ---------------------------------------------------------------------
-- Connection Status Report: --
! You are not connected to MotherDuck
-- User Report: --
* User Name: "duckdb"
* Role: "duckdb"
-- Catalog Report: --
* Current Database: "memory"
* Current Schema: "main"
* # Total Catalogs you have access to: 3
* # Total Tables you have access to: 3
* # Total Shares you have access to: 0
* # Tables in this catalog you have access to: 3
* # Tables in this catalog & schema you have access to: 3
-- Action Report: --
v Inserted into existing database "memory"
v Using existing schema "main"
-- Status: ---------------------------------------------------------------------
-- Connection Status Report: --
! You are not connected to MotherDuck
-- User Report: --
* User Name: "duckdb"
* Role: "duckdb"
-- Catalog Report: --
* Current Database: "memory"
* Current Schema: "main"
* # Total Catalogs you have access to: 3
* # Total Tables you have access to: 3
* # Total Shares you have access to: 0
* # Tables in this catalog you have access to: 3
* # Tables in this catalog & schema you have access to: 3
-- Action Report: --
v Inserted into existing database "memory"
v Using existing schema "main"
duckdb keeps downloaded extensions and secrets in a temporary directory:
i /tmp/RtmpEniUfn/working_dir/RtmpuzOsbq/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 keeps downloaded extensions and secrets in a temporary directory:
i /tmp/RtmpEniUfn/working_dir/RtmpuzOsbq/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.
Note: method with signature 'DBIConnection#Id' chosen for function 'dbExistsTable',
target signature 'duckdb_connection#Id'.
"duckdb_connection#ANY" would also be valid
-- Status: ---------------------------------------------------------------------
-- Connection Status Report: --
! You are not connected to MotherDuck
-- User Report: --
* User Name: "duckdb"
* Role: "duckdb"
-- Catalog Report: --
* Current Database: "memory"
* Current Schema: "main"
* # Total Catalogs you have access to: 3
* # Total Tables you have access to: 0
* # Total Shares you have access to: 0
* # Tables in this catalog you have access to: 0
* # Tables in this catalog & schema you have access to: 0
-- Action Report:
* Deleted "delete_table" from "[database_name]" in "main"
duckdb keeps downloaded extensions and secrets in a temporary directory:
i /tmp/RtmpEniUfn/working_dir/RtmpuzOsbq/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 keeps downloaded extensions and secrets in a temporary directory:
i /tmp/RtmpEniUfn/working_dir/RtmpuzOsbq/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 keeps downloaded extensions and secrets in a temporary directory:
i /tmp/RtmpEniUfn/working_dir/RtmpuzOsbq/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.
-- Status: ---------------------------------------------------------------------
-- Connection Status Report: --
! You are not connected to MotherDuck
-- User Report: --
* User Name: "duckdb"
* Role: "duckdb"
-- Catalog Report: --
* Current Database: "memory"
* Current Schema: "main"
* # Total Catalogs you have access to: 3
* # Total Tables you have access to: 0
* # Total Shares you have access to: 0
* # Tables in this catalog you have access to: 0
* # Tables in this catalog & schema you have access to: 0
-- Action Report: --
v Inserted into existing database "memory"
v Created new schema "test_schema"
-- Status: ---------------------------------------------------------------------
-- Connection Status Report: --
! You are not connected to MotherDuck
-- User Report: --
* User Name: "duckdb"
* Role: "duckdb"
-- Catalog Report: --
* Current Database: "memory"
* Current Schema: "main"
* # Total Catalogs you have access to: 3
* # Total Tables you have access to: 1
* # Total Shares you have access to: 0
* # Tables in this catalog you have access to: 1
* # Tables in this catalog & schema you have access to: 0
-- Action Report: --
* Deleted "test_schema" schema and 1 tables
-- Status: ---------------------------------------------------------------------
-- Connection Status Report: --
! You are not connected to MotherDuck
-- User Report: --
* User Name: "duckdb"
* Role: "duckdb"
-- Catalog Report: --
* Current Database: "memory"
* Current Schema: "main"
* # Total Catalogs you have access to: 3
* # Total Tables you have access to: 0
* # Total Shares you have access to: 0
* # Tables in this catalog you have access to: 0
* # Tables in this catalog & schema you have access to: 0
-- Action Report: --
* Deleted "test_schema" schema and 1 tables
duckdb keeps downloaded extensions and secrets in a temporary directory:
i /tmp/RtmpEniUfn/working_dir/RtmpuzOsbq/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.
-- Action Report: --
v Inserted into existing database "memory"
v Using existing schema "main"
v Overwrite existing table "mtcars_csv"
duckdb keeps downloaded extensions and secrets in a temporary directory:
i /tmp/RtmpEniUfn/working_dir/RtmpuzOsbq/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.
Saving _problems/test-motherduck-405.R
[ FAIL 1 | WARN 0 | SKIP 1 | PASS 22 ]
══ Skipped tests (1) ═══════════════════════════════════════════════════════════
• empty test (1): 'test-motherduck.R:259:3'
══ Failed tests ════════════════════════════════════════════════════════════════
── Error ('test-motherduck.R:405:7'): read_excel / successfully reads a excel and copies table to database ──
<purrr_error_indexed/rlang_error/error/condition>
Error in `purrr::map(ext_lst$valid_ext, function(x) DBI::dbExecute(.con, glue::glue("INSTALL {x};")))`: i In index: 1.
Caused by error in `dbSendQuery()`:
! 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 1 | WARN 0 | SKIP 1 | PASS 22 ]
Error:
! Test failures.
Execution halted
Flavor: r-devel-linux-x86_64-fedora-clang