Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
The latest duckdb release was just put on CRAN (0.5.0), and when it's installed we get a test failure:
── Error (test-duckdb.R:212:3): Joining, auto-cleanup enabled ──────────────────
Error: rapi_execute: Failed to run query
Error: Invalid Error: std::exception
Backtrace:
▆
1. ├─DBI::dbGetQuery(...) at test-duckdb.R:212:2
2. └─DBI::dbGetQuery(...)
3. └─DBI (local) .local(conn, statement, ...)
4. ├─DBI::dbSendQuery(conn, statement, ...)
5. └─duckdb::dbSendQuery(conn, statement, ...)
6. └─duckdb (local) .local(conn, statement, ...)
7. └─duckdb:::duckdb_result(...)
8. └─duckdb:::duckdb_execute(res)
9. └─duckdb:::rapi_execute(...)
[ FAIL 1 | WARN 1 | SKIP 28 | PASS 8460 ]
Error: Test failures
Execution halted
Warning messages:
1: Connection is garbage-collected, use dbDisconnect() to avoid this.
2: Database is garbage-collected, use dbDisconnect(con, shutdown=TRUE) or duckdb::duckdb_shutdown(drv) to avoid this.
1 error ✖ | 0 warnings ✔ | 2 notes ✖
Unfortunately I can't reproduce this on either MacOS nor Ubuntu (20.04).
