Skip to content

add Common.GetCurrLibPath and Common.GetCurrExePath method #206

add Common.GetCurrLibPath and Common.GetCurrExePath method

add Common.GetCurrLibPath and Common.GetCurrExePath method #206

Triggered via push March 24, 2026 10:45
Status Failure
Total duration 43s
Artifacts

linux.yml

on: push
Matrix: Ubuntu-latest
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 4 warnings
GCC-C++17-Debug
Process completed with exit code 1.
GCC-C++17-Release
The strategy configuration was canceled because "Ubuntu-latest.Debug_17" failed
GCC-C++17-Release
The operation was canceled.
GCC-C++20-Release
The strategy configuration was canceled because "Ubuntu-latest.Debug_17" failed
GCC-C++20-Release
The operation was canceled.
GCC-C++20-Debug
The strategy configuration was canceled because "Ubuntu-latest.Debug_17" failed
GCC-C++20-Debug
The operation was canceled.
GCC-C++17-Debug
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, ashutoshvarma/setup-ninja@master. 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/
GCC-C++17-Release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, ashutoshvarma/setup-ninja@master. 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/
GCC-C++20-Release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, ashutoshvarma/setup-ninja@master. 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/
GCC-C++20-Debug
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, ashutoshvarma/setup-ninja@master. 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/