Skip to content

fix cmakelist.txt

fix cmakelist.txt #17

Triggered via push April 1, 2026 11:11
Status Failure
Total duration 1d 0h 0m 1s
Artifacts

config.yml

on: push
Matrix: cmake-on-linux
Matrix: vcpkg-on-linux
Matrix: vcpkg-on-windows
Fit to window
Zoom out
Zoom in

Annotations

13 errors and 6 warnings
vcpkg-on-linux (ubuntu-22.04, 11)
Process completed with exit code 2.
vcpkg-on-linux (ubuntu-22.04, 11): src/fmi4cpp/fmi2/fmu.cpp#L44
‘tmpPath’ was not declared in this scope; did you mean ‘fmuPath’?
vcpkg-on-linux (ubuntu-22.04, 11): src/fmi4cpp/fmi2/fmu.cpp#L38
‘tmpPath’ was not declared in this scope; did you mean ‘fmuPath’?
vcpkg-on-linux (ubuntu-22.04, 11): src/fmi4cpp/fmi2/fmu.cpp#L36
‘tmpPath’ was not declared in this scope; did you mean ‘fmuPath’?
vcpkg-on-linux (ubuntu-22.04, 11): src/fmi4cpp/fmi2/fmu.cpp#L36
‘tmpPath’ was not declared in this scope; did you mean ‘fmuPath’?
vcpkg-on-linux (ubuntu-22.04, 11): src/fmi4cpp/fmi2/fmu.cpp#L30
‘create_directories’ was not declared in this scope; did you mean ‘std::filesystem::create_directories’?
vcpkg-on-linux (ubuntu-22.04, 11): src/fmi4cpp/fmi2/fmu.cpp#L30
‘tmpPath’ was not declared in this scope; did you mean ‘fmuPath’?
vcpkg-on-linux (ubuntu-22.04, 11): src/fmi4cpp/fmi2/fmu.cpp#L28
‘fs’ has not been declared
vcpkg-on-linux (ubuntu-22.04, 11): src/fmi4cpp/fmi2/fmu.cpp#L16
‘fs’ has not been declared
vcpkg-on-windows (windows-2022)
Process completed with exit code 1.
vcpkg-on-windows (windows-2022)
vcpkg install failed. See logs for more information:
vcpkg-on-windows (windows-2019)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
cmake-on-linux (ubuntu-20.04)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
vcpkg-on-linux (ubuntu-22.04, 11)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, lukka/run-vcpkg@v10. 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/
vcpkg-on-linux (ubuntu-22.04, 11)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Dv7MaQAAAAARyNCLJ9HRS7GQsjsenC+iRE0yRURHRTA3MDkARWRnZQ==
vcpkg-on-linux (ubuntu-22.04, 11)
Failed to restore: Cache service responded with 400
vcpkg-on-windows (windows-2022)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, lukka/run-vcpkg@v10. 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/
vcpkg-on-windows (windows-2022)
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0O/7MaQAAAAAQdRQr20B1RK/ce+HXJfZWUEhMMzBFREdFMDIwNgBFZGdl
vcpkg-on-windows (windows-2022)
Failed to restore: Cache service responded with 400