Skip to content

replace hardcoded hack with getHackPath() #6294

replace hardcoded hack with getHackPath()

replace hardcoded hack with getHackPath() #6294

Triggered via push March 17, 2026 03:11
Status Success
Total duration 6m 6s
Artifacts 8

build.yml

on: push
Matrix: test / build-linux
test  /  ...  /  Build win64
4m 41s
test / Windows MSVC / Build win64
test  /  ...  /  Test (ubuntu, gcc-11, default plugins, default config)
58s
test / Run Linux test suite / Test (ubuntu, gcc-11, default plugins, default config)
test  /  ...  /  Test (ubuntu, gcc-12, all plugins, default config)
52s
test / Run Linux test suite (gcc-12, all plugins) / Test (ubuntu, gcc-12, all plugins, default config)
test  /  ...  /  Test (windows, msvc, default plugins, default config)
1m 3s
test / Run Windows test suite / Test (windows, msvc, default plugins, default config)
test  /  ...  /  Test (windows, msvc, default plugins, empty config)
1m 19s
test / Run Windows test suite (empty config) / Test (windows, msvc, default plugins, empty config)
Fit to window
Zoom out
Zoom in

Annotations

9 warnings
lint / lint
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 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/
docs / Build linux64
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/upload-artifact@v4. 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/
test / Linux gcc-11 / Build linux64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/checkout@v4, actions/upload-artifact@v4. 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/
test / Linux gcc-12 / Build linux64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/checkout@v4, actions/upload-artifact@v4. 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/
test / Run Linux test suite (gcc-12, all plugins) / Test (ubuntu, gcc-12, all plugins, default config)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4, nick-fields/retry@v3. 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/
test / Run Linux test suite / Test (ubuntu, gcc-11, default plugins, default config)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4, nick-fields/retry@v3. 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/
test / Windows MSVC / Build win64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/checkout@v4, actions/upload-artifact@v4, ilammy/msvc-dev-cmd@v1. 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/
test / Run Windows test suite / Test (windows, msvc, default plugins, default config)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4, nick-fields/retry@v3. 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/
test / Run Windows test suite (empty config) / Test (windows, msvc, default plugins, empty config)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/checkout@v4, actions/download-artifact@v4, actions/upload-artifact@v4, nick-fields/retry@v3. 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/

Artifacts

Produced during runtime
Name Size Digest
docs
2.36 MB
sha256:7e8e4e9ea2fb3543b114a6181e29c6c6ade5f13bd4f80c950ec0afe745eb54ff
test-gcc-11
11.2 MB
sha256:53a89ce1febd7e0dd792e85ca466b3b5ffc0a2ef8698517057e5551827a52939
test-gcc-12
21.1 MB
sha256:21a02c69463ee53ce562a88a2fd5ae4cf5d6819388df3803ac6a58cf0528230b
test-msvc
7.99 MB
sha256:496e6cbc36ade2f206650c80fe4c07f7ff578cef901678d37f238297e245201a
test-output-gcc-11-default_plugins-default_config
45.9 KB
sha256:1ef229cae639ec1d79036518f1766a0d125df4c865e7655104f46e0a07327042
test-output-gcc-12-all_plugins-default_config
46.5 KB
sha256:7839eed889e18b168e5e75dcaa196899da466a9df377aa7beed49c095cfa584a
test-output-msvc-default_plugins-default_config
46.2 KB
sha256:2218c59e243d45102e796a53a503eb7c4a0d3da8c859018edab485c99af0e841
test-output-msvc-default_plugins-empty_config
45.8 KB
sha256:45eb6da60090ba608d297c1991e5789276104208751775d3ef35981cf5a69ca6