Skip to content

Fix to check if events should be recorded in tracing #743

Fix to check if events should be recorded in tracing

Fix to check if events should be recorded in tracing #743

Re-run triggered March 1, 2025 21:40
Status Failure
Total duration 4m 46s
Artifacts 1

llama-cpp-rs-check.yml

on: pull_request
Run Tests on LLama Cpp Rs
4m 35s
Run Tests on LLama Cpp Rs
Check that it builds on mac
1m 15s
Check that it builds on mac
Check that it builds on windows
4m 31s
Check that it builds on windows
Matrix: Check that it builds on various targets
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 3 warnings
Check that it builds on various targets (linux/amd64)
buildx failed with: ERROR: failed to solve: process "/bin/sh -c cargo build --bin simple --features cuda" did not complete successfully: exit code: 101
Check that it builds on various targets (linux/arm64)
The job was canceled because "linux_amd64" failed.
Check that it builds on various targets (linux/arm64)
The operation was canceled.
Check that it builds on windows
Process completed with exit code 1.
Check that it builds on various targets (linux/amd64)
Cache not found for keys: docker.io--tonistiigi--binfmt-latest-linux-x64
Check that it builds on various targets (linux/arm64)
Cache not found for keys: docker.io--tonistiigi--binfmt-latest-linux-x64
Check that it builds on various targets (linux/arm64)
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

Artifacts

Produced during runtime
Name Size
utilityai~llama-cpp-rs~M6BHOH.dockerbuild
50.8 KB