Skip to content

migrate from remotes to pak #91

migrate from remotes to pak

migrate from remotes to pak #91

Triggered via pull request May 30, 2026 10:18
Status Failure
Total duration 7m 42s
Artifacts 5

R-CMD-check.yaml

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

Annotations

15 errors, 5 warnings, and 1 notice
macos-latest (release)
Process completed with exit code 1.
macos-latest (release)
R CMD check found ERRORs
macos-latest (release)
Running examples in ‘rdocdump-Ex.R’ failed
ubuntu-latest (oldrel-1)
Process completed with exit code 1.
ubuntu-latest (oldrel-1)
R CMD check found ERRORs
ubuntu-latest (oldrel-1)
Running examples in ‘rdocdump-Ex.R’ failed
ubuntu-latest (release)
Process completed with exit code 1.
ubuntu-latest (release)
R CMD check found ERRORs
ubuntu-latest (release)
Running examples in ‘rdocdump-Ex.R’ failed
windows-latest (release)
Process completed with exit code 1.
windows-latest (release)
R CMD check found ERRORs
windows-latest (release)
Running examples in 'rdocdump-Ex.R' failed
ubuntu-latest (devel)
Process completed with exit code 1.
ubuntu-latest (devel)
R CMD check found ERRORs
ubuntu-latest (devel)
Running examples in ‘rdocdump-Ex.R’ failed
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/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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-1)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

Artifacts

Produced during runtime
Name Size Digest
Linux-X64-rdevel-2-results
1.35 MB
sha256:276a1da8e9e5b3a7fc2bd1b1013a363dcb81797352fb209542ede9ebb95a779c
Linux-X64-roldrel-1-4-results
866 KB
sha256:fa0fae071674206df00ca314eb8ba61130a30ac13b3c887dcf02bd278db8fa3e
Linux-X64-rrelease-3-results
868 KB
sha256:e2d31e509679cbb8c683d6aef02528a192b33d680b3950e827a433a0064082e8
Windows-X64-rrelease-1-results
867 KB
sha256:43c2befb2a2bc458a61fabfc7c602da4d0558b0bbcad8f83353cd72ebba53ad4
macOS-ARM64-rrelease-0-results
863 KB
sha256:95d50051a1327cc0f901ebc4e96cbc808152282c406db5f4f3863a4b9b370493