Skip to content

move to v0.2.6 (#280) #222

move to v0.2.6 (#280)

move to v0.2.6 (#280) #222

Triggered via push April 28, 2026 21:22
Status Failure
Total duration 32m 53s
Artifacts

check.yml

on: push
Matrix: check
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 40 warnings
check (macos-latest, release)
package or namespace load failed for ‘VoltRon’ in .requirePackage(package):
check (windows-latest, devel, 45)
Process completed with exit code 1.
check (windows-latest, devel, 45)
subscript out of bounds
check (ubuntu-latest, devel)
Process completed with exit code 1.
check (ubuntu-latest, devel)
Failed to install 'VoltRon' from local:
check (ubuntu-24.04, devel)
Process completed with exit code 1.
check (ubuntu-24.04, devel)
Failed to install 'VoltRon' from local:
check (macos-latest, devel)
package or namespace load failed for ‘VoltRon’ in .requirePackage(package):
check (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@v3, 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. 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/
check (macos-latest, release)
Loading required namespace: BPCells
check (macos-latest, release)
Found the following significant warnings:
check (macos-latest, release)
file 'VoltRon/cleanup' did not have execute permissions: corrected
check (macos-latest, release)
file 'VoltRon/cleanup' did not have execute permissions: corrected
check (macos-latest, release)
SystemRequirements: invalid C++ specification ‘C++ 17’
check (macos-latest, release)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
check (macos-latest, release)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
check (macos-latest, release)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
check (macos-latest, release)
fribidi 1.0.16 is already installed and up-to-date. To reinstall 1.0.16, run: brew reinstall fribidi
check (macos-latest, release)
harfbuzz 14.2.0 is already installed and up-to-date. To reinstall 14.2.0, run: brew reinstall harfbuzz
check (macos-latest, release)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
check (macos-latest, release)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
check (windows-latest, devel, 45)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, 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. 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/
check (windows-latest, devel, 45)
file 'VoltRon/configure' did not have execute permissions: corrected
check (windows-latest, devel, 45)
file 'VoltRon/cleanup' did not have execute permissions: corrected
check (windows-latest, devel, 45)
file 'BPCells/configure' did not have execute permissions: corrected
check (windows-latest, devel, 45)
file 'BPCells/cleanup' did not have execute permissions: corrected
check (windows-latest, devel, 45)
SystemRequirements: invalid C++ specification 'C++ 17'
check (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@v3, 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. 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/
check (ubuntu-latest, devel)
SystemRequirements: invalid C++ specification ‘C++ 17’
check (ubuntu-latest, devel)
os-prober will not be executed to detect other bootable partitions.
check (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/checkout@v3, 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. 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/
check (ubuntu-24.04, devel)
SystemRequirements: invalid C++ specification ‘C++ 17’
check (ubuntu-24.04, devel)
os-prober will not be executed to detect other bootable partitions.
check (ubuntu-24.04, devel)
The unit file, source configuration file or drop-ins of ua-timer.timer changed on disk. Run 'systemctl daemon-reload' to reload units.
check (ubuntu-24.04, devel)
The unit file, source configuration file or drop-ins of ubuntu-advantage.service changed on disk. Run 'systemctl daemon-reload' to reload units.
check (macos-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@v3, 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. 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/
check (macos-latest, devel)
Loading required namespace: BPCells
check (macos-latest, devel)
Found the following significant warnings:
check (macos-latest, devel)
file 'VoltRon/cleanup' did not have execute permissions: corrected
check (macos-latest, devel)
file 'VoltRon/cleanup' did not have execute permissions: corrected
check (macos-latest, devel)
SystemRequirements: invalid C++ specification ‘C++ 17’
check (macos-latest, devel)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
check (macos-latest, devel)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
check (macos-latest, devel)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
check (macos-latest, devel)
fribidi 1.0.16 is already installed and up-to-date. To reinstall 1.0.16, run: brew reinstall fribidi
check (macos-latest, devel)
harfbuzz 14.2.0 is already installed and up-to-date. To reinstall 14.2.0, run: brew reinstall harfbuzz
check (macos-latest, devel)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!
check (macos-latest, devel)
`$HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` is set: not checking for outdated dependents or dependents with broken linkage!