unit-tests #1212
unittests.yml
on: schedule
unit-tests
/
scheduled-run-check
2s
Matrix: unit-tests / unit-tests
Annotations
8 errors and 4 warnings
|
unit-tests / ubuntu-latest (R release - latest packages)
Process completed with exit code 1.
|
|
unit-tests / ubuntu-latest (R release - latest packages)
non-character argument
|
|
unit-tests / ubuntu-latest (R release - lockfile packages)
Process completed with exit code 1.
|
|
unit-tests / ubuntu-latest (R release - lockfile packages)
non-character argument
|
|
unit-tests / macos-latest (R release - lockfile packages)
Process completed with exit code 1.
|
|
unit-tests / macos-latest (R release - lockfile packages)
non-character argument
|
|
unit-tests / windows-latest (R release - lockfile packages)
Process completed with exit code 1.
|
|
unit-tests / windows-latest (R release - lockfile packages)
non-character argument
|
|
unit-tests / ubuntu-latest (R release - latest packages)
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. 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/
|
|
unit-tests / ubuntu-latest (R release - lockfile packages)
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. 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/
|
|
unit-tests / macos-latest (R release - lockfile packages)
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. 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/
|
|
unit-tests / windows-latest (R release - lockfile packages)
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. 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/
|