Skip to content

fix cmake.yaml: vcpkg install #16

fix cmake.yaml: vcpkg install

fix cmake.yaml: vcpkg install #16

Triggered via push June 13, 2026 15:14
Status Failure
Total duration 1d 0h 0m 2s
Artifacts

cmake.yaml

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

Annotations

12 errors and 16 warnings
build (windows-2022, x64, Debug)
Process completed with exit code 1.
build (windows-2022, x64, Debug)
Could NOT find Dia (missing: Dia_INCLUDE_DIR Dia_LIBRARY)
build (windows-2022, x64, Release)
Process completed with exit code 1.
build (windows-2022, x64, Release)
Could NOT find Dia (missing: Dia_INCLUDE_DIR Dia_LIBRARY)
build (windows-2022, Win32, Debug)
Process completed with exit code 1.
build (windows-2022, Win32, Debug)
Could NOT find Dia (missing: Dia_INCLUDE_DIR Dia_LIBRARY)
build (windows-2022, Win32, Release)
Process completed with exit code 1.
build (windows-2022, Win32, Release)
Could NOT find Dia (missing: Dia_INCLUDE_DIR Dia_LIBRARY)
build (windows-2019, x64, Release)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
build (windows-2019, Win32, Debug)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
build (windows-2019, Win32, Release)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
build (windows-2019, x64, Debug)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
build (windows-2022, x64, Debug)
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/
build (windows-2022, x64, Debug)
boost-system's buildsystem uses very long paths and may fail on your
build (windows-2022, x64, Debug)
Unexpected input(s) 'vcpkgArguments', 'vcpkgTriplet', valid inputs are ['vcpkgDirectory', 'runVcpkgInstall', 'vcpkgGitCommitId', 'vcpkgGitURL', 'doNotUpdateVcpkg', 'doNotCache', 'vcpkgJsonGlob', 'vcpkgJsonIgnores', 'vcpkgConfigurationJsonGlob', 'binaryCachePath', 'runVcpkgFormatString', 'useShell', 'logCollectionRegExps']
build (windows-2022, x64, 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/
build (windows-2022, x64, Release)
boost-system's buildsystem uses very long paths and may fail on your
build (windows-2022, x64, Release)
Unexpected input(s) 'vcpkgArguments', 'vcpkgTriplet', valid inputs are ['vcpkgDirectory', 'runVcpkgInstall', 'vcpkgGitCommitId', 'vcpkgGitURL', 'doNotUpdateVcpkg', 'doNotCache', 'vcpkgJsonGlob', 'vcpkgJsonIgnores', 'vcpkgConfigurationJsonGlob', 'binaryCachePath', 'runVcpkgFormatString', 'useShell', 'logCollectionRegExps']
build (windows-2022, Win32, Debug)
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/
build (windows-2022, Win32, Debug)
boost-system's buildsystem uses very long paths and may fail on your
build (windows-2022, Win32, Debug)
Unexpected input(s) 'vcpkgArguments', 'vcpkgTriplet', valid inputs are ['vcpkgDirectory', 'runVcpkgInstall', 'vcpkgGitCommitId', 'vcpkgGitURL', 'doNotUpdateVcpkg', 'doNotCache', 'vcpkgJsonGlob', 'vcpkgJsonIgnores', 'vcpkgConfigurationJsonGlob', 'binaryCachePath', 'runVcpkgFormatString', 'useShell', 'logCollectionRegExps']
build (windows-2022, Win32, 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/
build (windows-2022, Win32, Release)
boost-system's buildsystem uses very long paths and may fail on your
build (windows-2022, Win32, Release)
Unexpected input(s) 'vcpkgArguments', 'vcpkgTriplet', valid inputs are ['vcpkgDirectory', 'runVcpkgInstall', 'vcpkgGitCommitId', 'vcpkgGitURL', 'doNotUpdateVcpkg', 'doNotCache', 'vcpkgJsonGlob', 'vcpkgJsonIgnores', 'vcpkgConfigurationJsonGlob', 'binaryCachePath', 'runVcpkgFormatString', 'useShell', 'logCollectionRegExps']