Skip to content

Merge pull request #1830 from JackAKirk/hip-set-device #9320

Merge pull request #1830 from JackAKirk/hip-set-device

Merge pull request #1830 from JackAKirk/hip-set-device #9320

Triggered via push September 23, 2024 15:27
Status Failure
Total duration 2h 22m 29s
Artifacts

cmake.yml

on: push
Matrix: Build - Ubuntu
Matrix: CUDA / Build & Test HW
Matrix: Level Zero / Build & Test HW
Matrix: OpenCL / Build & Test HW
Matrix: Fuzz tests short / Build and run fuzz tests on L0 HW
Matrix: HIP / Build & Test HW
Matrix: Level Zero static / Build & Test HW
Matrix: Level Zero V2 / Build & Test HW
Matrix: Build - MacOS
Matrix: Native CPU / Build & Test HW
Matrix: Build - Windows
E2E CUDA  /  ...  /  Check for changed files
E2E CUDA / Start e2e job / Check for changed files
E2E L0  /  ...  /  Check for changed files
E2E L0 / Start e2e job / Check for changed files
E2E OpenCL  /  ...  /  Check for changed files
E2E OpenCL / Start e2e job / Check for changed files
Matrix: E2E CUDA / Start e2e job / Build SYCL, UR, run E2E
Waiting for pending jobs
Matrix: E2E L0 / Start e2e job / Build SYCL, UR, run E2E
Waiting for pending jobs
Matrix: E2E OpenCL / Start e2e job / Build SYCL, UR, run E2E
Waiting for pending jobs
Fit to window
Zoom out
Zoom in

Annotations

24 errors and 1 warning
Build - Ubuntu (ubuntu-22.04, Debug, gcc, g++, -DVAL_USE_LIBBACKTRACE_BACKTRACE=OFF, -DUMF_ENABLE...
The self-hosted runner: ephemeral-action-runner-ubuntu-2204-i-0dadec11163373828 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.
Build - Ubuntu (ubuntu-22.04, Release, clang, clang++, -DVAL_USE_LIBBACKTRACE_BACKTRACE=OFF)
The self-hosted runner: ephemeral-action-runner-ubuntu-2204-i-0a2c5d9f95bc4ac9b 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.
Build - Ubuntu (ubuntu-22.04, Release, gcc, g++, -DVAL_USE_LIBBACKTRACE_BACKTRACE=ON)
The job was canceled because "ubuntu-22_04_Debug_gcc__2" failed.
Build - Ubuntu (ubuntu-20.04, Release, gcc, g++, -DVAL_USE_LIBBACKTRACE_BACKTRACE=OFF, -DUMF_ENAB...
The job was canceled because "ubuntu-22_04_Debug_gcc__2" failed.
Build - Ubuntu (ubuntu-20.04, Release, gcc-7, g++-7)
The job was canceled because "ubuntu-22_04_Debug_gcc__2" failed.
Build - Ubuntu (ubuntu-20.04, Release, gcc-7, g++-7)
The operation was canceled.
Build - Ubuntu (ubuntu-20.04, Release, gcc, g++, -DVAL_USE_LIBBACKTRACE_BACKTRACE=OFF, -DUMF_ENAB...
The job was canceled because "ubuntu-22_04_Debug_gcc__2" failed.
Build - Ubuntu (ubuntu-20.04, Debug, gcc, g++, -DVAL_USE_LIBBACKTRACE_BACKTRACE=OFF, -DUMF_ENABLE...
The job was canceled because "ubuntu-22_04_Debug_gcc__2" failed.
Build - Ubuntu (ubuntu-20.04, Debug, gcc, g++, -DVAL_USE_LIBBACKTRACE_BACKTRACE=OFF, -DUMF_ENABLE...
The job was canceled because "ubuntu-22_04_Debug_gcc__2" failed.
Build - Ubuntu (ubuntu-22.04, Release, gcc, g++, -DVAL_USE_LIBBACKTRACE_BACKTRACE=OFF, -DUMF_ENAB...
The job was canceled because "ubuntu-22_04_Debug_gcc__2" failed.
Build - Ubuntu (ubuntu-22.04, Release, clang, clang++, -DUR_ENABLE_LATENCY_HISTOGRAM=ON)
The job was canceled because "ubuntu-22_04_Debug_gcc__2" failed.
Build - Ubuntu (ubuntu-22.04, Release, gcc, g++, -DVAL_USE_LIBBACKTRACE_BACKTRACE=OFF, -DUMF_ENAB...
The job was canceled because "ubuntu-22_04_Debug_gcc__2" failed.
Build - Ubuntu (ubuntu-22.04, Debug, gcc, g++, -DVAL_USE_LIBBACKTRACE_BACKTRACE=OFF, -DUMF_ENABLE...
The job was canceled because "ubuntu-22_04_Debug_gcc__2" failed.
Build - Ubuntu (ubuntu-22.04, Release, clang, clang++, -DVAL_USE_LIBBACKTRACE_BACKTRACE=ON)
The job was canceled because "ubuntu-22_04_Debug_gcc__2" failed.
Build - MacOS (macos-12)
You are using macOS 12. We (and Apple) do not provide support for this old version. It is expected behaviour that some formulae will fail to build in this old version. It is expected behaviour that Homebrew will be buggy and slow. Do not create any issues about this on Homebrew's GitHub repositories. Do not create any issues even if you think this message is unrelated. Any opened issues will be immediately closed without response. Do not ask for help from Homebrew or its maintainers on social media. You may ask for help in Homebrew's discussions but are unlikely to receive a response. Try to figure out the problem yourself and submit a fix as a pull request. We will review it but may or may not accept it.