Skip to content

[Tests] Update gdtools to 0.5.2 in renv.lock - #15124

Merged
cderv merged 1 commit into
mainfrom
fix/renv-update-gdtools
Oct 20, 2026
Merged

cderv merged 1 commit into
mainfrom
fix/renv-update-gdtools

Conversation

@cderv

@cderv cderv commented Oct 20, 2026

Copy link
Copy Markdown
Member

The macOS jobs of the nightly built-version smoke run have failed in "Restore R packages" since 2026-10-17 (example run), so no macOS test has run since then.

Root cause

tests/renv.lock pins gdtools 0.5.1 from the moving P3M cran/latest URL. gdtools 0.5.2 reached CRAN on 2026-10-15, and P3M stopped serving the 0.5.1 macOS binary afterwards (for macOS arm64 on R 4.6, gdtools_0.5.1.tgz is a 404 and gdtools_0.5.2.tgz is served). The 2026-10-16 nightly installed a 2.0 MB binary; the 2026-10-20 nightly downloaded the 81 kB source tarball instead.

The source build fails on the runner with ld: library 'intl' not found, and flextable fails with it as a dependent. renv::restore() then stops before any test runs. This is a different failure from the cold-cache cluster in #14711, where renv reports no underlying install error.

Fix

Update gdtools to 0.5.2 with a targeted renv::update(). No other package changes.

The macOS legs run only in the nightly, against the create-release commit, so this PR's CI does not exercise them. The first nightly after merge will.

Checklist

I have (if applicable):

  • referenced the GitHub issue this PR closes
  • updated the appropriate changelog in the PR
  • ensured the present test suite passes
  • added new tests
  • created a separate documentation PR in Quarto's website repo and linked it to this PR
AI-assisted PR
  • AI tool used: Claude Code
  • Codebase grounding: local clone, CI job logs, P3M and CRAN package indexes
  • Human review: I have reviewed, tested, and verified the AI-generated content before submitting.

Note: autonomous AI agents submitting PRs without human oversight are not permitted — see the Code of Conduct.

gdtools 0.5.2 reached CRAN on 2026-10-15. `tests/renv.lock` pins 0.5.1 from the moving P3M `cran/latest` URL, so P3M no longer serves a macOS arm64 binary for 0.5.1 (`gdtools_0.5.1.tgz` is a 404, `gdtools_0.5.2.tgz` is served).

renv then falls back to the source tarball, and compiling it on the macOS runners fails with `ld: library 'intl' not found`. `flextable` fails with it as a dependent, which stops `renv::restore()` and makes the macOS jobs of the built-version nightly fail before running any test.

A targeted update to 0.5.2 gets the binary back. No other package changes.
@posit-snyk-bot

posit-snyk-bot commented Oct 20, 2026 •

Copy link
Copy Markdown
Collaborator

✅ Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
✅ Open Source Security 0 0 0 0 0 issues
✅ Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@mcanouil

Copy link
Copy Markdown
Collaborator

FYI, the gdtools update was motivated by performance issues regarding font caching.

@cderv
cderv merged commit 83f015f into main Oct 20, 2026
51 checks passed
@cderv
cderv deleted the fix/renv-update-gdtools branch October 20, 2026 12:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants