Skip to content
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

[R] [CI] A crossbow job that tests against DuckDB's dev branch #30944

Closed
asfimport opened this issue Jan 26, 2022 · 1 comment
Closed

[R] [CI] A crossbow job that tests against DuckDB's dev branch #30944

asfimport opened this issue Jan 26, 2022 · 1 comment

Comments

@asfimport
Copy link

It would be good to test against DuckDB's dev branch to warn us if there are impending changes that break something.

While we're doing this, we should clean up some of the Currently some of our jobs do already

# (Temporarily) install DuckDB from source to avoid their Unity builds
# (though only if we haven't filtered it out of the deps above,
# and if we can't get a binary from RSPM)
# Remove when there is a DuckDB release > 0.3.1-1
if [ ${R_PRUNE_DEPS} != "true" ]; then
${R_BIN} -e "if (all(!grepl('packagemanager.rstudio', options('repos')))) { remotes::install_github('duckdb/duckdb', subdir = '/tools/rpkg', build = FALSE) }"
fi

We should clean this up so that generally builds use the released DuckDB, but we can toggle dev DuckDB (and run a separate build that uses the dev DuckDB optionally)

Reporter: Jonathan Keane / @jonkeane
Assignee: Jonathan Keane / @jonkeane

PRs and other links:

Note: This issue was originally created as ARROW-15468. Please see the migration documentation for further details.

@asfimport
Copy link
Author

Jonathan Keane / @jonkeane:
Issue resolved by pull request 12366
#12366

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants