Optimize wgrad CUTLASS grouped gemm (#4891) #18814
facebook-github-botfbgemm_ci.yml
on: push
Matrix: build-bazel
Matrix: build-linux
Matrix: build-macos
Matrix: build-windows
Annotations
9 errors
|
build-linux (arm, linux.arm64.m7g.4xlarge, shared, clang, 16.0.6)
The self-hosted runner 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-linux (arm, linux.arm64.m7g.4xlarge, shared, gcc, 14.1.0)
The self-hosted runner 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-linux (arm, linux.arm64.m7g.4xlarge, static, clang, 16.0.6)
The self-hosted runner 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-linux (x86, linux.12xlarge, static, gcc, 9.5.0)
The operation was canceled.
|
|
build-linux (x86, linux.12xlarge, shared, gcc, 14.1.0)
The operation was canceled.
|
|
build-linux (arm, linux.arm64.m7g.4xlarge, static, gcc, 14.1.0)
The operation was canceled.
|
|
build-linux (x86, linux.12xlarge, static, clang, 16.0.6)
The self-hosted runner 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-macos (macos-13, static)
The operation was canceled.
|
|
build-linux (x86, linux.12xlarge, static, gcc, 14.1.0)
The self-hosted runner 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.
|