Skip to content

migrate from remotes to pak #92

migrate from remotes to pak

migrate from remotes to pak #92

Triggered via pull request May 30, 2026 10:24
@e-kotove-kotov
synchronize #29
remotes-to-pak
Status Failure
Total duration 9m 45s
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 (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
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
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 (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/
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.33 MB
sha256:4d0b2c91d66a1b8d5dcf357352297e94bdd4dce99a911aad8ec50137bc589568
Linux-X64-roldrel-1-4-results
809 KB
sha256:5595cce53140d6233a784eee3c1b3cb8630345c1dd930864c1b1e8015d520f7e
Linux-X64-rrelease-3-results
811 KB
sha256:f864367f7906b6feddb40b3eaa96ded47f3bc4b6ed7387dd8f884a82590a1a5b
Windows-X64-rrelease-1-results
773 KB
sha256:1a0b8f65b4de9fed4d146a66e5727c92f43bad2d079d285d1b15b073bcb4595b
macOS-ARM64-rrelease-0-results
769 KB
sha256:6cab710adbe9c30e313e1356a5a46448ccfc58930a46efbce8272cb7faac2868