Skip to content
CMake

Update to JUCE 8.0.13 #8095

Sign in to view logs

Update to JUCE 8.0.13

Update to JUCE 8.0.13 #8095

Triggered via push June 11, 2026 15:13
@timothyschoentimothyschoen
pushed bc5b775
develop
Status Failure
Total duration 10m 4s
Artifacts –

cmake.yml

on: push
Matrix: linux-arm-build
Matrix: linux-x64-build
macos-universal-build
2m 12s
macos-universal-build
macos-legacy-build
9m 47s
macos-legacy-build
windows-64-build
1m 27s
windows-64-build
windows-32-build
1m 30s
windows-32-build
push-nightlies
9s
push-nightlies
package-all-artifacts
0s
package-all-artifacts
Fit to window
Zoom out
Zoom in

Annotations

32 errors and 10 warnings
windows-64-build
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
windows-64-build
Fetched in submodule path 'Libraries/JUCE', but it did not contain 3faada4defb90a62b08134febb22b744f84f9428. Direct fetching of that commit failed.
windows-64-build
remote error: upload-pack: not our ref 3faada4defb90a62b08134febb22b744f84f9428
windows-32-build
The process 'C:\Program Files\Git\bin\git.exe' failed with exit code 128
windows-32-build
Fetched in submodule path 'Libraries/JUCE', but it did not contain 3faada4defb90a62b08134febb22b744f84f9428. Direct fetching of that commit failed.
windows-32-build
remote error: upload-pack: not our ref 3faada4defb90a62b08134febb22b744f84f9428
Arch-x64
The process '/usr/sbin/git' failed with exit code 128
Arch-x64
Fetched in submodule path 'Libraries/JUCE', but it did not contain 3faada4defb90a62b08134febb22b744f84f9428. Direct fetching of that commit failed.
Arch-x64
remote error: upload-pack: not our ref 3faada4defb90a62b08134febb22b744f84f9428
Debian-x64
The process '/usr/bin/git' failed with exit code 128
Debian-x64
Fetched in submodule path 'Libraries/JUCE', but it did not contain 3faada4defb90a62b08134febb22b744f84f9428. Direct fetching of that commit failed.
Debian-x64
remote error: upload-pack: not our ref 3faada4defb90a62b08134febb22b744f84f9428
Fedora-43-x64
The process '/usr/sbin/git' failed with exit code 128
Fedora-43-x64
Fetched in submodule path 'Libraries/JUCE', but it did not contain 3faada4defb90a62b08134febb22b744f84f9428. Direct fetching of that commit failed.
Fedora-43-x64
remote error: upload-pack: not our ref 3faada4defb90a62b08134febb22b744f84f9428
Fedora-44-aarch64
The process '/usr/sbin/git' failed with exit code 128
Fedora-44-aarch64
Fetched in submodule path 'Libraries/JUCE', but it did not contain 3faada4defb90a62b08134febb22b744f84f9428. Direct fetching of that commit failed.
Fedora-44-aarch64
remote error: upload-pack: not our ref 3faada4defb90a62b08134febb22b744f84f9428
macos-universal-build
The process '/opt/homebrew/bin/git' failed with exit code 128
macos-universal-build
Fetched in submodule path 'Libraries/JUCE', but it did not contain 3faada4defb90a62b08134febb22b744f84f9428. Direct fetching of that commit failed.
macos-universal-build
remote error: upload-pack: not our ref 3faada4defb90a62b08134febb22b744f84f9428
Fedora-43-aarch64
Process completed with exit code 1.
OpenSUSE-Tumbleweed-aarch64
Process completed with exit code 1.
OpenSUSE-Tumbleweed-x64
Process completed with exit code 4.
Ubuntu-26.04-x64
Process completed with exit code 1.
Ubuntu-26.04-aarch64
Process completed with exit code 1.
Arch-aarch64
Process completed with exit code 1.
Ubuntu-24.04-x64
Process completed with exit code 1.
Ubuntu-24.04-aarch64
Process completed with exit code 1.
Debian-aarch64
Process completed with exit code 1.
Fedora-44-x64
Process completed with exit code 1.
macos-legacy-build
Process completed with exit code 1.
Fedora-43-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hendrikmuhs/ccache-action@v1.2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
OpenSUSE-Tumbleweed-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hendrikmuhs/ccache-action@v1.2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Ubuntu-26.04-x64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hendrikmuhs/ccache-action@v1.2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Ubuntu-26.04-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hendrikmuhs/ccache-action@v1.2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Arch-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hendrikmuhs/ccache-action@v1.2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Ubuntu-24.04-x64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hendrikmuhs/ccache-action@v1.2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Ubuntu-24.04-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hendrikmuhs/ccache-action@v1.2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Debian-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hendrikmuhs/ccache-action@v1.2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Fedora-44-x64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hendrikmuhs/ccache-action@v1.2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
macos-legacy-build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: hendrikmuhs/ccache-action@v1.2. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/