Skip to content

Refactoring

Refactoring #26

Triggered via pull request April 14, 2026 17:03
Status Failure
Total duration 30m 43s
Artifacts 4

r.yml

on: pull_request
Matrix: R-CMD-check
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 13 warnings
ubuntu-latest (oldrel)
Process completed with exit code 1.
ubuntu-latest (oldrel)
R CMD check found WARNINGs
macOS-latest (release)
Process completed with exit code 1.
macOS-latest (release)
R CMD check found WARNINGs
ubuntu-latest (devel)
Process completed with exit code 1.
ubuntu-latest (devel)
R CMD check found WARNINGs
ubuntu-latest (release)
Process completed with exit code 1.
ubuntu-latest (release)
R CMD check found WARNINGs
ubuntu-latest (oldrel)
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. Node.js 20 will be removed from the runner on September 16th, 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-latest (oldrel)
Found the following significant 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, 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. Node.js 20 will be removed from the runner on September 16th, 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-latest (release)
Found the following significant warnings:
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, r-lib/actions/setup-r@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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)
Found the following significant warnings:
windows-latest (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, r-lib/actions/setup-r@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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 (devel)
Found the following significant warnings:
windows-latest (devel)
unable to access index for repository https://r-lib.github.io/p/pak/stable/win.binary/mingw32/x86_64/bin/windows/contrib/4.7:
ubuntu-latest (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. Node.js 20 will be removed from the runner on September 16th, 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-latest (devel)
Found the following significant warnings:
ubuntu-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-r@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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-latest (release)
Found the following significant warnings:

Artifacts

Produced during runtime
Name Size Digest
Linux-X64-rdevel-3-results
332 KB
sha256:4bc72a09c2cdf6ae41e87d9cf6367959f67614747ad8bdc621c855381c14e69e
Linux-X64-roldrel-5-results
331 KB
sha256:aec5c9f233cec62623517dade0837da9f6c62f0552f1a38b063f9c800f49cc8a
Linux-X64-rrelease-4-results
331 KB
sha256:9ac88f0456b850d29b07704911f25abd9b71201a732fb82a866c23c26d2ab477
macOS-ARM64-rrelease-0-results
329 KB
sha256:9eb9d51fb9052af39e621cfa780ec1d40f1554267f135a19a6a747c4fc50a5c2