Check we can load duckdb extensions in a separate process #94
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DuckDB extensions are shared libraries downloaded when
running
INSTAll <name>
. They are pre-built by the DuckDBteam https://github.com/duckdb/extension-ci-tools
They are built for the major platforms using the standard
compilers.
One of the CRAN test server is a Linux machine with R compiled
with clang instead of GCC. Since the compilers have different
ABIs, a crash happens when trying to execute extensions that are
pre-built on GCC.
To avoid the crash on CRAN machines, we check if the extensions can
be loaded in a separate process and proceed if that's possible. This follows the same pattern that's used by duckplyr in tidyverse/duckplyr#620
For reference this is how the crash looks on CRAN machines: