Speed up Ubuntu CI with binary arrow/duckdb via r2u - #84
Closed
diraol wants to merge 2 commits into
Closed
Conversation
arrow and duckdb have no CRAN binary for every matrix cell, so pak (via r-lib/actions/setup-r-dependencies) falls back to compiling libarrow's C++ core and duckdb's bundled amalgamation from source on every cold cache -- the largest CI time sink. Pre-installing both as apt binaries via r2u before setup-r-dependencies runs lets pak see them already satisfied and skip the source build entirely. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XgLB4bj3a47WZziQUU9BiE
Mirrors the CI speedup: point users at pre-compiled arrow/duckdb binaries via r2u before installing censobr, so they don't have to compile either package from source on Ubuntu/Debian. Added identically to README.md and vignettes/censobr.Rmd to keep the two install sections from drifting apart. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XgLB4bj3a47WZziQUU9BiE
Contributor
Author
|
Achei que funcionaria, não funcionou.... rs |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
arrowandduckdbhave no CRAN binary for every CI matrix cell, sopak(viar-lib/actions/setup-r-dependencies) falls back to compiling libarrow's C++ core and duckdb's bundled amalgamation from source on cold cache — the largest CI time sink.ubuntu-24.04matrix cells inR-CMD-check.yaml,R-CMD-check-CRAN.yaml, andtest-coverage.yaml, then pre-installsr-cran-arrow/r-cran-duckdbas apt binaries beforesetup-r-dependenciesruns.pakchecks already-installed package versions againstDESCRIPTIONconstraints and skips a package that's already satisfied, so no bspm/pak interception is required — this sidesteps a known pak/bspm incompatibility.if: runner.os == 'Linux'); no changes toR/,DESCRIPTION, or the data-release pin.Test plan
ubuntu-24.04cells in the Actions run for this PRsetup-r-dependenciesstep log reportsarrow/duckdbas already satisfied (not compiled)R-CMD-check --as-cranstill passes 0 errors / 0 warningsmainas a sanity check on the speedup