[
https://issues.apache.org/jira/browse/ARROW-14735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445247#comment-17445247
]
Jonathan Keane commented on ARROW-14735:
----------------------------------------
Yeah, we can disable those if we want, the solution to the flakiness is
actually in DuckDB, which they have already solved and we are waiting for a
release before we can merge https://github.com/apache/arrow/pull/11482 which
should be much more reliable.
They have a pre-release just out today, so their full release should happen
soon.
> [R] duckdb integration tests seem flaky
> ---------------------------------------
>
> Key: ARROW-14735
> URL: https://issues.apache.org/jira/browse/ARROW-14735
> Project: Apache Arrow
> Issue Type: Bug
> Components: Continuous Integration, R
> Reporter: Antoine Pitrou
> Priority: Major
>
> I have seen this failure at least twice on CI:
> {code}
> ══ Failed tests
> ════════════════════════════════════════════════════════════════
> ── Failure (test-duckdb.R:145:3): Joining, auto-cleanup enabled
> ────────────────
> all(c(table_one_name, table_two_name) %in% DBI::dbListTables(con)) is not TRUE
> `actual`: FALSE
> `expected`: TRUE
> ── Failure (test-duckdb.R:158:3): Joining, auto-cleanup disabled
> ───────────────
> table_three_name %in% DBI::dbListTables(con) is not TRUE
> `actual`: FALSE
> `expected`: TRUE
> ── Failure (test-duckdb.R:162:3): Joining, auto-cleanup disabled
> ───────────────
> table_three_name %in% DBI::dbListTables(con) is not TRUE
> `actual`: FALSE
> `expected`: TRUE
> {code}
> example:
> https://github.com/apache/arrow/runs/4235794453?check_suite_focus=true#step:8:20637
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
