-
Notifications
You must be signed in to change notification settings - Fork 4k
ARROW-16374: [R] [C++] skip another snappy test during sanitizer runs #13014
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@github-actions crossbow submit test-fedora-r-clang-sanitizer |
| }) | ||
|
|
||
| test_that("read_parquet() and write_parquet() accept connection objects", { | ||
| skip_if_not_available("snappy") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The other way to do this would be to specify no compression in write_parquet(). That plus a comment explaining why is probably clearer since skip_if_not_available("snappy") isn't actually what's happening (snappy is available in the build but the function still skips on linux devel to avoid sanitizers)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I've been thinking about how may of these we need + it would be great if we actually tested this with our default and then fell back on sanitizers only. Either compression should be totally fine, but it would be nice to have coverage on both. But we should do that generally. I'll make a Jira for that + we can do that outside of the release pressure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
|
|
Revision: 1e86276 Submitted crossbow builds: ursacomputing/crossbow @ actions-1978
|
|
Benchmark runs are scheduled for baseline = b048937 and contender = f03f090. f03f090 is a master commit associated with this PR. Results will be available as each benchmark for each run completes. |
Another example of google/snappy#148