Skip to content

CI: Update server build configuration to use C2x standard for i686 ta… #124

CI: Update server build configuration to use C2x standard for i686 ta…

CI: Update server build configuration to use C2x standard for i686 ta… #124

Triggered via push April 20, 2026 16:07
Status Failure
Total duration 11m 0s
Artifacts

server-build.yml

on: push
Matrix: server-release
Release Dev
0s
Release Dev
Fit to window
Zoom out
Zoom in

Annotations

24 errors and 9 warnings
Build - linux_armv5te_musl
Process completed with exit code 101.
Build - linux_x86_64_musl
The strategy configuration was canceled because "server-release.linux_armv5te_musl_armv5t" failed
Build - linux_arm_musleabi
The strategy configuration was canceled because "server-release.linux_armv5te_musl_armv5t" failed
Build - linux_i686_musl
The strategy configuration was canceled because "server-release.linux_armv5te_musl_armv5t" failed
Build - linux_aarch64_gnu
The strategy configuration was canceled because "server-release.linux_armv5te_musl_armv5t" failed
Build - linux_x86_64_gnu
The strategy configuration was canceled because "server-release.linux_armv5te_musl_armv5t" failed
Build - linux_armv5te_gnu
The strategy configuration was canceled because "server-release.linux_armv5te_musl_armv5t" failed
Build - linux_armv7_musleabihf
The strategy configuration was canceled because "server-release.linux_armv5te_musl_armv5t" failed
Build - linux_arm_gnueabi
The strategy configuration was canceled because "server-release.linux_armv5te_musl_armv5t" failed
Build - linux_arm_gnueabi
The operation was canceled.
Build - linux_arm_musleabihf
The strategy configuration was canceled because "server-release.linux_armv5te_musl_armv5t" failed
Build - linux_arm_musleabihf
The operation was canceled.
Build - linux_arm_gnueabihf
The strategy configuration was canceled because "server-release.linux_armv5te_musl_armv5t" failed
Build - linux_arm_gnueabihf
The operation was canceled.
Build - linux_armv7_gnueabi
The strategy configuration was canceled because "server-release.linux_armv5te_musl_armv5t" failed
Build - linux_armv7_gnueabi
The operation was canceled.
Build - linux_armv7_gnueabihf
The strategy configuration was canceled because "server-release.linux_armv5te_musl_armv5t" failed
Build - linux_armv7_gnueabihf
The operation was canceled.
Build - linux_i686_gnu
The strategy configuration was canceled because "server-release.linux_armv5te_musl_armv5t" failed
Build - linux_i686_gnu
The operation was canceled.
Build - linux_aarch64_musl
The strategy configuration was canceled because "server-release.linux_armv5te_musl_armv5t" failed
Build - linux_aarch64_musl
The operation was canceled.
Build - linux_armv7_musleabi
The strategy configuration was canceled because "server-release.linux_armv5te_musl_armv5t" failed
Build - linux_armv7_musleabi
The operation was canceled.
Build - linux_armv5te_musl
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. 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 - linux_arm_gnueabi
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. 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 - linux_arm_musleabihf
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. 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 - linux_arm_gnueabihf
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. 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 - linux_armv7_gnueabi
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. 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 - linux_armv7_gnueabihf
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. 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 - linux_i686_gnu
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. 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 - linux_aarch64_musl
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. 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 - linux_armv7_musleabi
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. 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/