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
update R CMD workflow to apply patches in .github/patches/duckdb-r #9412
Conversation
.github/workflows/R_CMD_CHECK.yml
Outdated
- name: Apply duckdb-r patches | ||
shell: bash | ||
run: | | ||
for filename in $GITHUB_WORKSPACE/$DUCKDB_SRC/.github/patches/duckdb-r/*.patch; do |
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.
for filename in $GITHUB_WORKSPACE/$DUCKDB_SRC/.github/patches/duckdb-r/*.patch; do | |
for filename in ${{ env.DUCKDB_SRC }}/.github/patches/duckdb-r/*.patch; do |
(not that I am completely sure, but this seems to make more sense)
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.
$GITHUB_WORKSPACE
is just the absolute path. we also use $GITHUB_WORKSPACE/$DUCKDB_SRC/
here
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.
nvm, also realized that this was executing in the wrong directory
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.
I got a bit lost with the directories, unsure.
Actually one thing you need to add, to handle the case of no files being there, is:
shopt -s nullglob
See for example this part of the Nightly workflow: https://github.com/duckdb/duckdb/blob/main/.github/workflows/NightlyTests.yml#L630
Thanks! LGTM |
If the duckdb repo ever creates breaking changes to the duckdb-r repo that need patches, we can prevent CI from yelling at us if we include the patches. These patches then need to be applied to duckdb-r at some later date.
Most likely the duckdb-r CI will yell when the sources are updated. One idea might be to apply the patches from within the vendor script.
Needed because #9406 will break the duckdb-r client