The process '/usr/bin/git' failed with exit code 128

Fetched in submodule path 'vendor/llama.cpp', but it did not contain 8e34af8cc4fbc6351914e653b3ca9cf564922d5e. Direct fetching of that commit failed.

remote error: upload-pack: not our ref 8e34af8cc4fbc6351914e653b3ca9cf564922d5e

The process '/usr/bin/git' failed with exit code 128

Fetched in submodule path 'vendor/llama.cpp', but it did not contain 8e34af8cc4fbc6351914e653b3ca9cf564922d5e. Direct fetching of that commit failed.

remote error: upload-pack: not our ref 8e34af8cc4fbc6351914e653b3ca9cf564922d5e

The process '/usr/bin/git' failed with exit code 128

Fetched in submodule path 'vendor/llama.cpp', but it did not contain 8e34af8cc4fbc6351914e653b3ca9cf564922d5e. Direct fetching of that commit failed.

remote error: upload-pack: not our ref 8e34af8cc4fbc6351914e653b3ca9cf564922d5e

The process '/opt/homebrew/bin/git' failed with exit code 128

Fetched in submodule path 'vendor/llama.cpp', but it did not contain 8e34af8cc4fbc6351914e653b3ca9cf564922d5e. Direct fetching of that commit failed.

remote error: upload-pack: not our ref 8e34af8cc4fbc6351914e653b3ca9cf564922d5e

The strategy configuration was canceled because "build-macos._3_12" failed

The strategy configuration was canceled because "build-macos._3_12" failed

The process '/opt/homebrew/bin/git' failed with exit code 128

Fetched in submodule path 'vendor/llama.cpp', but it did not contain 8e34af8cc4fbc6351914e653b3ca9cf564922d5e. Direct fetching of that commit failed.

remote error: upload-pack: not our ref 8e34af8cc4fbc6351914e653b3ca9cf564922d5e

The strategy configuration was canceled because "build-macos._3_12" failed

The process '/opt/homebrew/bin/git' failed with exit code 128

Fetched in submodule path 'vendor/llama.cpp', but it did not contain 8e34af8cc4fbc6351914e653b3ca9cf564922d5e. Direct fetching of that commit failed.

remote error: upload-pack: not our ref 8e34af8cc4fbc6351914e653b3ca9cf564922d5e

The process '/usr/bin/git' failed with exit code 128

Fetched in submodule path 'vendor/llama.cpp', but it did not contain 8e34af8cc4fbc6351914e653b3ca9cf564922d5e. Direct fetching of that commit failed.

remote error: upload-pack: not our ref 8e34af8cc4fbc6351914e653b3ca9cf564922d5e

The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128

Fetched in submodule path 'vendor/llama.cpp', but it did not contain 8e34af8cc4fbc6351914e653b3ca9cf564922d5e. Direct fetching of that commit failed.

remote error: upload-pack: not our ref 8e34af8cc4fbc6351914e653b3ca9cf564922d5e

The strategy configuration was canceled because "build-windows._3_11" failed

The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128

Fetched in submodule path 'vendor/llama.cpp', but it did not contain 8e34af8cc4fbc6351914e653b3ca9cf564922d5e. Direct fetching of that commit failed.

remote error: upload-pack: not our ref 8e34af8cc4fbc6351914e653b3ca9cf564922d5e

The strategy configuration was canceled because "build-windows._3_11" failed

The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128

Fetched in submodule path 'vendor/llama.cpp', but it did not contain 8e34af8cc4fbc6351914e653b3ca9cf564922d5e. Direct fetching of that commit failed.

remote error: upload-pack: not our ref 8e34af8cc4fbc6351914e653b3ca9cf564922d5e

The strategy configuration was canceled because "build-windows._3_11" failed

The operation was canceled.

The process '/usr/local/bin/git' failed with exit code 128

Fetched in submodule path 'vendor/llama.cpp', but it did not contain 8e34af8cc4fbc6351914e653b3ca9cf564922d5e. Direct fetching of that commit failed.

remote error: upload-pack: not our ref 8e34af8cc4fbc6351914e653b3ca9cf564922d5e

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/setup-python@v5. 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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

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/

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026