Run: https://github.com/astral-sh/uv-dev/actions/runs/30968289367
Job: https://github.com/astral-sh/uv-dev/actions/runs/30968289367/job/92187523875
The CI workflow failed on attempt 1 in test-integration / windows nanoserver on windows-latest, before the NanoServer container started:
failed to connect to the docker API at npipe:////./pipe/docker_engine; check if the path is correct and if the daemon is running: open //./pipe/docker_engine: The system cannot find the file specified.
The workflow invokes docker run directly without checking that the service and named pipe are ready. The logs establish that the pipe was unavailable, but not why the runner's Docker service was unavailable. The triggering main-branch commit only updates generated Python release metadata, so this is unrelated to that source change and appears to be a CI infrastructure flake. Consider a bounded Docker readiness/recovery step before running the container.
The run also independently timed out in test / cargo test on linux while apt slowly downloaded gnome-keyring packages; #542 tracks that Ubuntu-mirror setup flake. The all required jobs passed failure was only a rollup. astral-sh#18663 tracks the distinct application-level NanoServer error this job normally exercises; this occurrence failed before reaching it.
Run: https://github.com/astral-sh/uv-dev/actions/runs/30968289367
Job: https://github.com/astral-sh/uv-dev/actions/runs/30968289367/job/92187523875
The CI workflow failed on attempt 1 in test-integration / windows nanoserver on windows-latest, before the NanoServer container started:
The workflow invokes docker run directly without checking that the service and named pipe are ready. The logs establish that the pipe was unavailable, but not why the runner's Docker service was unavailable. The triggering main-branch commit only updates generated Python release metadata, so this is unrelated to that source change and appears to be a CI infrastructure flake. Consider a bounded Docker readiness/recovery step before running the container.
The run also independently timed out in test / cargo test on linux while apt slowly downloaded gnome-keyring packages; #542 tracks that Ubuntu-mirror setup flake. The all required jobs passed failure was only a rollup. astral-sh#18663 tracks the distinct application-level NanoServer error this job normally exercises; this occurrence failed before reaching it.