You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@arrow.apache.org by "Dewey Dunnington (Jira)" <ji...@apache.org> on 2022/09/23 00:44:00 UTC

[jira] [Assigned] (ARROW-17809) [R] DuckDB test is failing (again) with new duckdb release

     [ https://issues.apache.org/jira/browse/ARROW-17809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dewey Dunnington reassigned ARROW-17809:
----------------------------------------

    Assignee: Dewey Dunnington

> [R] DuckDB test is failing (again) with new duckdb release
> ----------------------------------------------------------
>
>                 Key: ARROW-17809
>                 URL: https://issues.apache.org/jira/browse/ARROW-17809
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: R
>            Reporter: Dewey Dunnington
>            Assignee: Dewey Dunnington
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> It looks like the fix that I thought would work in DuckDB did not, in fact fix the error! The previous ticket, ARROW-17643, just skipped the test until the new release of duckdb (which just happened).



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