Skip to content

Merge pull request #2314 from lukaszstolarczuk/bump-umf-on-v0.10.x #10544

Merge pull request #2314 from lukaszstolarczuk/bump-umf-on-v0.10.x

Merge pull request #2314 from lukaszstolarczuk/bump-umf-on-v0.10.x #10544

Triggered via push November 12, 2024 13:39
Status Success
Total duration 2h 8m 55s
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: Build - MacOS
Matrix: Native CPU / Build & Test HW
Matrix: Build - Windows
E2E CUDA  /  ...  /  Check for changed files
8s
E2E CUDA / Start e2e job / Check for changed files
E2E L0  /  ...  /  Check for changed files
8s
E2E L0 / Start e2e job / Check for changed files
E2E OpenCL  /  ...  /  Check for changed files
9s
E2E OpenCL / Start e2e job / Check for changed files
Matrix: E2E CUDA / Start e2e job / Build SYCL, UR, run E2E
Matrix: E2E L0 / Start e2e job / Build SYCL, UR, run E2E
Matrix: E2E OpenCL / Start e2e job / Build SYCL, UR, run E2E
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
Build - MacOS (macos-12)
A brownout will take place on November 11, 14:00 UTC - November 12, 00:00 UTC to raise awareness of the upcoming macOS-12 environment removal. For more details, see https://github.com/actions/runner-images/issues/10721
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.