Skip to content

Update imgui

Update imgui #4294

Triggered via push August 10, 2025 04:53
Status Failure
Total duration 1h 23m 36s
Artifacts

build-cmake.yml

on: push
Matrix: build-linux
Matrix: build-macos
Matrix: build-windows
Fit to window
Zoom out
Zoom in

Annotations

2 errors, 27 warnings, and 10 notices
Release / ubuntu-24.04-arm / aarch64 / clang
Process completed with exit code 4.
Debug / ubuntu-24.04-arm / aarch64 / gcc
The hosted runner lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
macOS / Debug / system-clang
ninja 1.13.1 is already installed and up-to-date. To reinstall 1.13.1, run: brew reinstall ninja
macOS / Release / homebrew-clang
ninja 1.13.1 is already installed and up-to-date. To reinstall 1.13.1, run: brew reinstall ninja
macOS / Release / system-clang
ninja 1.13.1 is already installed and up-to-date. To reinstall 1.13.1, run: brew reinstall ninja
macOS / Debug / homebrew-clang
ninja 1.13.1 is already installed and up-to-date. To reinstall 1.13.1, run: brew reinstall ninja
Windows / Debug / cl
Cache not found for keys: v0-rust-build-windows-Windows_NT-x64-78cd9f1d-da39a3ee, v0-rust-build-windows-Windows_NT-x64-78cd9f1d
Windows / Debug / cl
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0+imYaAAAAABAD1yT1/O5QIMMw7UczvBrQ0hJMzBFREdFMDQyMgBFZGdl
Windows / Debug / cl
Failed to restore: Cache service responded with 400
Windows / Release / clang
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Windows / Release / clang
Cache not found for keys: v0-rust-build-windows-Windows_NT-x64-78cd9f1d-da39a3ee, v0-rust-build-windows-Windows_NT-x64-78cd9f1d
Windows / Release / clang
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0CyqYaAAAAAAGYTik2lPETY6Z4G6E1UQ8QkwyQUEyMDMwMTEwMDUzAEVkZ2U=
Windows / Release / clang
Failed to restore: Cache service responded with 400
Windows / Release / cl
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Windows / Release / cl
Cache not found for keys: v0-rust-build-windows-Windows_NT-x64-78cd9f1d-da39a3ee, v0-rust-build-windows-Windows_NT-x64-78cd9f1d
Windows / Release / cl
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0DSmYaAAAAAD6lN1e22CAT6HW0ILqXFz+QkwyQUEyMDMwMTA2MDAzAEVkZ2U=
Windows / Release / cl
Failed to restore: Cache service responded with 400
Windows / Release / clang-cl
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Windows / Release / clang-cl
Cache not found for keys: v0-rust-build-windows-Windows_NT-x64-78cd9f1d-da39a3ee, v0-rust-build-windows-Windows_NT-x64-78cd9f1d
Windows / Release / clang-cl
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0oyqYaAAAAADt/IQcgElaR4ekpk4wsMfAUEhYMzFFREdFMDIxMQBFZGdl
Windows / Release / clang-cl
Failed to restore: Cache service responded with 400
Windows / Debug / clang-cl
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Windows / Debug / clang-cl
Cache not found for keys: v0-rust-build-windows-Windows_NT-x64-78cd9f1d-da39a3ee, v0-rust-build-windows-Windows_NT-x64-78cd9f1d
Windows / Debug / clang-cl
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0DiyYaAAAAACR5quIeAcOQocqDbqb/nyxUEhYMzFFREdFMDYyMQBFZGdl
Windows / Debug / clang-cl
Failed to restore: Cache service responded with 400
Windows / Debug / clang
Failed to save: Failed to CreateCacheEntry: Received non-retryable error: Failed request: (409) Conflict: cache entry with the same key, version, and scope already exists
Windows / Debug / clang
Cache not found for keys: v0-rust-build-windows-Windows_NT-x64-78cd9f1d-da39a3ee, v0-rust-build-windows-Windows_NT-x64-78cd9f1d
Windows / Debug / clang
Failed to save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0YCyYaAAAAACXjfja79ezSbk4TAAckMTYUEFPRURHRTA1MTAARWRnZQ==
Windows / Debug / clang
Failed to restore: Cache service responded with 400
macOS / Debug / system-clang
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
macOS / Release / homebrew-clang
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
macOS / Release / system-clang
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
macOS / Debug / homebrew-clang
The macos-latest label will migrate to macOS 15 beginning August 4, 2025. For more information see https://github.com/actions/runner-images/issues/12520
Windows / Debug / cl
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Windows / Release / clang
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Windows / Release / cl
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Windows / Release / clang-cl
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Windows / Debug / clang-cl
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
Windows / Debug / clang
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677