Skip to content

Raise MSVC warning level from /W3 to /W4 #9342

Raise MSVC warning level from /W3 to /W4

Raise MSVC warning level from /W3 to /W4 #9342

Triggered via pull request September 24, 2024 13:24
Status Failure
Total duration 1h 13m 21s
Artifacts

cmake.yml

on: pull_request
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

38 errors and 1 warning
OpenCL / Build & Test HW (OPENCL, Intel(R) OpenCL, OFF, OFF, Release, gcc, g++)
Process completed with exit code 1.
OpenCL / Build & Test HW (OPENCL, Intel(R) OpenCL, OFF, OFF, Debug, clang, clang++)
The job was canceled because "OPENCL_Intel_R__OpenCL__3" failed.
OpenCL / Build & Test HW (OPENCL, Intel(R) OpenCL, OFF, OFF, Debug, gcc, g++)
The job was canceled because "OPENCL_Intel_R__OpenCL__3" failed.
OpenCL / Build & Test HW (OPENCL, Intel(R) OpenCL, OFF, OFF, Release, clang, clang++)
The job was canceled because "OPENCL_Intel_R__OpenCL__3" failed.
Build - Ubuntu (ubuntu-22.04, Release, clang, clang++, -DVAL_USE_LIBBACKTRACE_BACKTRACE=ON)
The self-hosted runner: ephemeral-action-runner-ubuntu-2204-i-060722b3bd34fe44e 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-0fb4f79644c1b7912 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-056e22e0fd619e23f 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 job was canceled because "ubuntu-22_04_Release_cl_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_Release_cl_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_Release_cl_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_Release_cl_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_Release_cl_2" failed.
Build - Windows (windows-2022, L0_V2, -DUR_BUILD_ADAPTER_L0_V2=ON, Debug, cl, cl)
Process completed with exit code 1.
Build - Windows (windows-2022, None, Debug, cl, cl)
The job was canceled because "windows-2022_L0_V2_-DUR_B" failed.
Build - Windows (windows-2022, None, Debug, cl, cl)
The operation was canceled.
Build - Windows (windows-2022, None, Release, cl, cl)
The job was canceled because "windows-2022_L0_V2_-DUR_B" failed.
Build - Windows (windows-2022, None, Release, cl, cl)
The operation was canceled.
Build - Windows (windows-2022, None, Release, clang-cl, clang-cl)
The job was canceled because "windows-2022_L0_V2_-DUR_B" failed.
Build - Windows (windows-2022, None, Release, clang-cl, clang-cl)
The operation was canceled.
Build - Windows (windows-2022, None, Release, cl, cl)
The job was canceled because "windows-2022_L0_V2_-DUR_B" failed.
Build - Windows (windows-2022, None, Release, cl, cl)
The operation was canceled.
Build - Windows (windows-2022, None, Debug, clang-cl, clang-cl)
The job was canceled because "windows-2022_L0_V2_-DUR_B" failed.
Build - Windows (windows-2022, None, Debug, clang-cl, clang-cl)
The operation was canceled.
Build - Windows (windows-2022, None, Release, clang-cl, clang-cl)
The job was canceled because "windows-2022_L0_V2_-DUR_B" failed.
Build - Windows (windows-2022, None, Release, clang-cl, clang-cl)
The operation was canceled.
Build - Windows (windows-2022, None, Debug, cl, cl)
The job was canceled because "windows-2022_L0_V2_-DUR_B" failed.
Build - Windows (windows-2022, None, Debug, cl, cl)
The operation was canceled.
Build - Windows (windows-2022, None, Debug, clang-cl, clang-cl)
The job was canceled because "windows-2022_L0_V2_-DUR_B" failed.
Build - Windows (windows-2022, None, Debug, clang-cl, clang-cl)
The operation was canceled.
Level Zero V2 / Build & Test HW (L0_V2, OFF, OFF, Release, gcc, g++)
Process completed with exit code 8.
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.