You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Dewey Dunnington (Jira)" <ji...@apache.org> on 2022/09/07 13:36:00 UTC

[jira] [Created] (ARROW-17643) [R] Latest duckdb release is causing test failure

Dewey Dunnington created ARROW-17643:
----------------------------------------

             Summary: [R] Latest duckdb release is causing test failure
                 Key: ARROW-17643
                 URL: https://issues.apache.org/jira/browse/ARROW-17643
             Project: Apache Arrow
          Issue Type: Bug
          Components: R
            Reporter: Dewey Dunnington


The latest duckdb release was just put on CRAN (0.5.0), and when it's installed we get a test failure:

{noformat}
── 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 ✖
{noformat}

Unfortunately I can't reproduce this on either MacOS nor Ubuntu (20.04).





--
This message was sent by Atlassian Jira
(v8.20.10#820010)