Skip to content

ARROW-17818: [R] Skip duckdb test that is failing until the issue is resolved - #14209

Merged
paleolimbot merged 2 commits into
apache:masterfrom
paleolimbot:r-duckdb-skipit
Sep 23, 2022
Merged

paleolimbot merged 2 commits into
apache:masterfrom
paleolimbot:r-duckdb-skipit

Conversation

@paleolimbot

Copy link
Copy Markdown
Member

This just skips the test to stop it from obscuring other failures until we diagnose it properly (ARROW-17818).

@paleolimbot paleolimbot changed the title ARROW-17809: [R] DuckDB test is failing (again) with new duckdb release ARROW-17818: [R] Skip duckdb test that is failing until the issue is resolved Sep 22, 2022
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")

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it's just this one. A user may run into this if they try a dplyr left_join() of their own, but it's not a crash or a corruption of data, just a mysterious error.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, given that none of us can replicate it on normal computers, it's unlikely to surface in real life (still good to solve, just improbable).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That sounds a bit dismissive. Just because this particular test doesn't replicate it doesn't mean it may not occur more frequently with another sequence of operations.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, sorry, it's definitely a problem, and may well be a problem with Arrow/R or Arrow/C++ that the change in DuckDB surfaced. There's an open PR + an open JIRA to make sure this doesn't get forgotten about.

@github-actions

Copy link
Copy Markdown

@github-actions

Copy link
Copy Markdown

⚠️ Ticket has not been started in JIRA, please click 'Start Progress'.

@github-actions

Copy link
Copy Markdown

@github-actions

Copy link
Copy Markdown

⚠️ Ticket has no components in JIRA, make sure you assign one.

@paleolimbot
paleolimbot merged commit 53b19a9 into apache:master Sep 23, 2022
@paleolimbot
paleolimbot deleted the r-duckdb-skipit branch September 23, 2022 12:04
@ursabot

ursabot commented Sep 23, 2022

Copy link
Copy Markdown

Benchmark runs are scheduled for baseline = 36928ec and contender = 53b19a9. 53b19a9 is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Finished ⬇️0.0% ⬆️0.0%] ec2-t3-xlarge-us-east-2
[Failed ⬇️0.31% ⬆️0.07%] test-mac-arm
[Failed ⬇️0.27% ⬆️0.0%] ursa-i9-9960x
[Finished ⬇️0.21% ⬆️0.0%] ursa-thinkcentre-m75q
Buildkite builds:
[Finished] 53b19a9e ec2-t3-xlarge-us-east-2
[Failed] 53b19a9e test-mac-arm
[Failed] 53b19a9e ursa-i9-9960x
[Finished] 53b19a9e ursa-thinkcentre-m75q
[Finished] 36928ec3 ec2-t3-xlarge-us-east-2
[Failed] 36928ec3 test-mac-arm
[Failed] 36928ec3 ursa-i9-9960x
[Finished] 36928ec3 ursa-thinkcentre-m75q
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java

zagto pushed a commit to zagto/arrow that referenced this pull request Oct 7, 2022
…resolved (apache#14209)

This just skips the test to stop it from obscuring other failures until we diagnose it properly (ARROW-17818).

Authored-by: Dewey Dunnington <[email protected]>
Signed-off-by: Dewey Dunnington <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants