AArch64 Capstone Update / SME2 support #147
FinnWilkinsonMAIN.yml
on: pull_request
Matrix: Debug - build and test / Build_and_Run
Matrix: Debug - build and test / Build_and_Run
Matrix: Release - build, test and benchmarks / Build_and_Run
Matrix: Release - build, test and benchmarks / Build_and_Run
Annotations
44 errors and 8 warnings
|
Debug - build and test / redhat/ubi8:latest, gcc-7
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Debug - build and test / redhat/ubi8:latest, gcc-7
The hosted runner: GitHub Actions 15 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
Debug - build and test / rockylinux:8, gcc-7
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Debug - build and test / rockylinux:8, gcc-7
The hosted runner: GitHub Actions 6 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
Debug - build and test / rockylinux:8, gcc-8
The hosted runner: GitHub Actions 2 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
Debug - build and test / debian:10, gcc-7
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Debug - build and test / debian:10, gcc-7
Process completed with exit code 137.
|
|
Debug - build and test / debian:11, gcc-8
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Debug - build and test / debian:11, gcc-8
The hosted runner: GitHub Actions 5 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
Debug - build and test / ubuntu:20.04, gcc-8
The hosted runner encountered an error while running your job. (Error Type: Disconnect).
|
|
Debug - build and test / redhat/ubi8:latest, gcc-8
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Debug - build and test / redhat/ubi8:latest, gcc-8
Process completed with exit code 137.
|
|
Debug - build and test / rockylinux:8, gcc-9
The hosted runner encountered an error while running your job. (Error Type: Disconnect).
|
|
Debug - build and test / ubuntu:20.04, gcc-9
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Debug - build and test / ubuntu:20.04, gcc-9
Process completed with exit code 137.
|
|
Debug - build and test / redhat/ubi9:latest, gcc-9
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Debug - build and test / redhat/ubi9:latest, gcc-9
Process completed with exit code 137.
|
|
Debug - build and test / ubuntu:20.04, gcc-10
The hosted runner encountered an error while running your job. (Error Type: Disconnect).
|
|
Debug - build and test / rockylinux:8, gcc-10
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Debug - build and test / debian:11, gcc-10
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Debug - build and test / debian:11, gcc-10
The hosted runner: GitHub Actions 8 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
Debug - build and test / debian:11, gcc-9
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Debug - build and test / debian:11, gcc-9
The hosted runner: GitHub Actions 9 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
Debug - build and test / redhat/ubi9:latest, gcc-10
The hosted runner: GitHub Actions 17 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
Release - build, test and benchmarks / rockylinux:8, gcc-7
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Release - build, test and benchmarks / rockylinux:8, gcc-7
Process completed with exit code 137.
|
|
Release - build, test and benchmarks / redhat/ubi8:latest, gcc-7
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Release - build, test and benchmarks / redhat/ubi8:latest, gcc-7
The hosted runner: GitHub Actions 3 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
Release - build, test and benchmarks / debian:10, gcc-7
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Release - build, test and benchmarks / ubuntu:20.04, gcc-8
The hosted runner encountered an error while running your job. (Error Type: Disconnect).
|
|
Release - build, test and benchmarks / debian:11, gcc-8
Process completed with exit code 100.
|
|
Release - build, test and benchmarks / debian:11, gcc-8
Process completed with exit code 127.
|
|
Release - build, test and benchmarks / debian:11, gcc-8
Process completed with exit code 127.
|
|
Release - build, test and benchmarks / rockylinux:8, gcc-9
The hosted runner encountered an error while running your job. (Error Type: Disconnect).
|
|
Release - build, test and benchmarks / ubuntu:20.04, gcc-9
The hosted runner encountered an error while running your job. (Error Type: Disconnect).
|
|
Release - build, test and benchmarks / redhat/ubi9:latest, gcc-9
The hosted runner: GitHub Actions 12 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
Release - build, test and benchmarks / debian:11, gcc-9
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Release - build, test and benchmarks / debian:11, gcc-9
Process completed with exit code 137.
|
|
Release - build, test and benchmarks / redhat/ubi9:latest, gcc-10
The hosted runner: GitHub Actions 1 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
Release - build, test and benchmarks / rockylinux:8, gcc-10
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Release - build, test and benchmarks / rockylinux:8, gcc-10
Process completed with exit code 137.
|
|
Release - build, test and benchmarks / debian:11, gcc-10
The hosted runner: GitHub Actions 14 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
Debug - build and test / ubuntu:18.04, gcc-7
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
Debug - build and test / ubuntu:18.04, gcc-7
The hosted runner encountered an error while running your job. (Error Type: Disconnect).
|
|
Debug - build and test / rockylinux:8, gcc-10
Received request to deprovision: The request was cancelled by the remote provider.
|
|
Release - build, test and benchmarks / rockylinux:8, gcc-7
Cache save failed.
|
|
Release - build, test and benchmarks / ubuntu:18.04, gcc-7
Received request to deprovision: The request was cancelled by the remote provider.
|
|
Release - build, test and benchmarks / debian:10, gcc-7
Received request to deprovision: The request was cancelled by the remote provider.
|
|
Release - build, test and benchmarks / rockylinux:8, gcc-8
Cache save failed.
|
|
Release - build, test and benchmarks / redhat/ubi8:latest, gcc-8
Cache save failed.
|
|
Release - build, test and benchmarks / debian:11, gcc-9
Cache save failed.
|
|
Release - build, test and benchmarks / ubuntu:20.04, gcc-10
Received request to deprovision: The request was cancelled by the remote provider.
|