Skip to content

use -I to upgrade pip in ubuntu:noble+ #2204

use -I to upgrade pip in ubuntu:noble+

use -I to upgrade pip in ubuntu:noble+ #2204

Triggered via push August 9, 2024 17:42
Status Failure
Total duration 1h 52m 23s
Artifacts

test.yml

on: push
Check PR Event
0s
Check PR Event
Build  /  Check GH Event
0s
Build / Check GH Event
Validate Features
13s
Validate Features
Matrix: Build / RAPIDS / build
Determine features matrix
6s
Determine features matrix
Determine image matrix
5s
Determine image matrix
Matrix: Feature integration / test
Matrix: run-feature-scenario-tests
Matrix: run-generated-feature-tests
Matrix: build-and-test-linux-images
Matrix: build-and-test-windows-images
Fit to window
Zoom out
Zoom in

Annotations

13 errors
gcc7-cuda11.1-ubuntu:18.04 / amd64
Process completed with exit code 1.
llvm9-cuda11.1-ubuntu:18.04 / amd64
Process completed with exit code 1.
gcc6-cuda11.1-ubuntu:18.04 / amd64
Process completed with exit code 1.
gcc8-cuda11.1-ubuntu:18.04 / amd64
Process completed with exit code 1.
gcc9-cuda11.1-ubuntu:18.04 / amd64
Process completed with exit code 1.
oneapi2023.2.0-cuda11.1-ubuntu:18.04 / amd64
Process completed with exit code 1.
oneapi2023.2.0-cuda11.1-ubuntu:18.04 / arm64
Process completed with exit code 1.
gcc7-cuda11.1-ubuntu:18.04 / arm64
Process completed with exit code 1.
gcc6-cuda11.1-ubuntu:18.04 / arm64
Process completed with exit code 1.
gcc9-cuda11.1-ubuntu:18.04 / arm64
Process completed with exit code 1.
gcc8-cuda11.1-ubuntu:18.04 / arm64
Process completed with exit code 1.
cuda12.6-cl14.16-windows / 2022
The self-hosted runner: windows-amd64-cpu4-x5wm8-runner-zghms 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.
llvm9-cuda11.1-ubuntu:18.04 / arm64
Process completed with exit code 1.