Skip to content

std.Build: allow packages to expose arbitrary LazyPaths by name #16620

std.Build: allow packages to expose arbitrary LazyPaths by name

std.Build: allow packages to expose arbitrary LazyPaths by name #16620

Triggered via pull request September 11, 2024 08:16
Status Failure
Total duration 3h 34m 48s
Artifacts

ci.yaml

on: pull_request
x86_64-linux-debug
3h 9m
x86_64-linux-debug
x86_64-linux-release
2h 18m
x86_64-linux-release
aarch64-linux-debug
3h 34m
aarch64-linux-debug
aarch64-linux-release
2h 32m
aarch64-linux-release
x86_64-macos-release
1h 14m
x86_64-macos-release
aarch64-macos-debug
44m 36s
aarch64-macos-debug
aarch64-macos-release
42m 58s
aarch64-macos-release
x86_64-windows-debug
55m 24s
x86_64-windows-debug
x86_64-windows-release
46m 14s
x86_64-windows-release
aarch64-windows
1h 0m
aarch64-windows
Fit to window
Zoom out
Zoom in

Annotations

4 errors
x86_64-windows-debug
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
x86_64-windows-debug
The self-hosted runner: George 3 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
x86_64-windows-release
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
x86_64-windows-release
The self-hosted runner: George 8 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.