You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@arrow.apache.org by GitBox <gi...@apache.org> on 2022/09/22 16:49:57 UTC
[GitHub] [arrow] jonkeane commented on a diff in pull request #14209: ARROW-17818: [R] Skip duckdb test that is failing until the issue is resolved
jonkeane commented on code in PR #14209:
URL: https://github.com/apache/arrow/pull/14209#discussion_r977884685
##########
r/tests/testthat/test-duckdb.R:
##########
@@ -202,9 +202,9 @@ dbExecute(con, "PRAGMA threads=2")
on.exit(dbDisconnect(con, shutdown = TRUE), add = TRUE)
test_that("Joining, auto-cleanup enabled", {
- # ARROW-17643: A change in duckdb 0.5.0 caused this test to fail but will
- # be fixed in the next release.
- skip_if_not(packageVersion("duckdb") > "0.5.0")
+ # ARROW-17643, ARROW-17818: A change in duckdb 0.5.0 caused this test to fail
+ # TODO: ARROW-17809 Follow up with the latest duckdb release to solve the issue
+ skip("ARROW-17818: Latest DuckDB causes this test to fail")
Review Comment:
I haven't been following this particular bug too closely so don't know this off the top of my head: is this the only test block that fails? And if so: does it fail during cleanup or during the query?
This is a pretty low-risk test to generically skip if this is the only test that is an issue since we have basically the same query without autocleanup below.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org