-
Notifications
You must be signed in to change notification settings - Fork 4k
ARROW-13538: [R] [CI] Don't test DuckDB in the minimal build #10861
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-r-minimal |
|
@github-actions crossbow submit test-r-minimal-build |
|
Revision: 2f9ee26e36ca438ce1bee3204e7f2c85c6804dac Submitted crossbow builds: ursacomputing/crossbow @ actions-706
|
|
@github-actions crossbow submit -g r |
|
Revision: 93ca61045bca627a90acf9e70d203128d9209f50 Submitted crossbow builds: ursacomputing/crossbow @ actions-710 |
nealrichardson
left a comment
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.
Can you rebase and resolve conflicts? I did a similar run_duckdb_examples on a branch I just merged in order to resolve some lint/broken rd messages, so we're conflicting.
Also, check the new regexp in ci/scripts/r_deps.sh: can you tweak that so that it still drops duckdb now that there's an explicit version listed?
e3a8a53 to
1097ab1
Compare
1097ab1 to
176f055
Compare
|
OK, thanks all done |
Also request the correct version of duckdb now that it's been released.