Merge pull request #2099 from RossBrunton/ross/matchdet #9259
RossBruntoncmake.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
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
Annotations
7 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-0c00c4c0a9a81fa18 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 self-hosted runner: ephemeral-action-runner-ubuntu-2204-i-0af2ca60a0d984f2f 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++, -DUR_ENABLE_LATENCY_HISTOGRAM=ON)
The self-hosted runner: ephemeral-action-runner-ubuntu-2204-i-02c790eac14942e34 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=ON)
The self-hosted runner: ephemeral-action-runner-ubuntu-2204-i-0f6662cda23f34137 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-060817b371867c679 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=OFF, -DUMF_ENAB...
The self-hosted runner: ephemeral-action-runner-ubuntu-2204-i-04a52a73a845d4c3d 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=OFF, -DUMF_ENAB...
GitHub Actions has encountered an internal error when running your job.
|
|
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.
|