Skip to content

Add R-level validation for functions that lost Rcpp::stop() guards #1296

Add R-level validation for functions that lost Rcpp::stop() guards

Add R-level validation for functions that lost Rcpp::stop() guards #1296

Triggered via push March 22, 2026 13:04
Status Failure
Total duration 10m 54s
Artifacts 5

R-CMD-check.yml

on: push
ubuntu-24.04 (release)
8m 10s
ubuntu-24.04 (release)
Matrix: check-all
revdepcheck
0s
revdepcheck
benchmark
0s
benchmark
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 8 warnings
ubuntu-22.04 (4.1)
Process completed with exit code 1.
ubuntu-22.04 (4.1)
R CMD check found WARNINGs
ubuntu-24.04 (release)
Process completed with exit code 1.
ubuntu-24.04 (release)
R CMD check found WARNINGs
ubuntu-24.04-arm (release)
Process completed with exit code 1.
ubuntu-24.04-arm (release)
R CMD check found WARNINGs
windows-latest (release)
Process completed with exit code 1.
windows-latest (release)
R CMD check found WARNINGs
ubuntu-24.04 (devel)
Process completed with exit code 1.
ubuntu-24.04 (devel)
R CMD check found WARNINGs
macOS-latest (release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, r-lib/actions/setup-pandoc@v2, r-lib/actions/setup-r@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ubuntu-22.04 (4.1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, r-lib/actions/setup-r@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ubuntu-22.04 (4.1)
Found the following significant warnings:
ubuntu-24.04 (release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, r-lib/actions/setup-r@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ubuntu-24.04-arm (release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, r-lib/actions/setup-r@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
windows-latest (release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, r-lib/actions/setup-pandoc@v2, r-lib/actions/setup-r@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
macos-15-intel (release)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, r-lib/actions/setup-pandoc@v2, r-lib/actions/setup-r@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
ubuntu-24.04 (devel)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/upload-artifact@v4, r-lib/actions/setup-r@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
Linux-ARM64-rrelease-4-results
25.2 MB
sha256:a219de1f6ffa049604a0fc467352a48a7f1ac4737e541fc13035852260d6e027
Linux-X64-r-0-results
25.6 MB
sha256:8e93bb1439a68a5b6c3eca5d84b4f48220fece01cee15a6ed3bdcfd281b64ebe
Linux-X64-r4.1-3-results
24.5 MB
sha256:42fe3b328754a97117c176e364c1da403d91e4b480c8d81151e43fd530988473
Linux-X64-rdevel-5-results
25.6 MB
sha256:97dddc5115c33befc23704e9127ae7a16e7aca481557335aaa879675e3b82a77
Windows-X64-rrelease-0-results
9.74 MB
sha256:c8587ba1b34b634c6c4c07871d11e4975e85c8b8c2c368b79feba26d6f811207