You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Neal Richardson / @nealrichardson:
But it's expensive to always clean first. Why isn't "run make clean when building docs" an instruction for users for if/when they run into issues?
Jonathan Keane / @jonkeane:
We could add it to instructions, for the specifics of the docs build, that is quite a bit of waiting time since that build can take a while to complete or error out.
Jonathan Keane / @jonkeane:
Also, I can't think of an example where I would want built files from one docker image to be used by another (or from my local host used by docker). Is there a time where that's helpful?
Jonathan Keane / @jonkeane:
Alternatively, we could do something in the docker builds that builds in a fresh(er) location that ignores the extras that are in the host system's arrow/R directory (R CMD BUILD . followed by R CMD INSTALL . might do that)
Jonathan Keane / @jonkeane:
Or by using R CMD INSTALL --preclean in arrow/ci/scripts/r_build.sh. And unless I'm mistaken, it looks like that shell script is only being used by the docs build?
If someone already has some built files in arrow/r, the re-install sometimes does not pick this up and will lead to segfaults or other odities
Reporter: Jonathan Keane / @jonkeane
Assignee: Jonathan Keane / @jonkeane
PRs and other links:
Note: This issue was originally created as ARROW-14510. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: