Skip to content
Build

[AArch64] NEON, SVE2 and SME2 instruction support with tests #202

Sign in to view logs

[AArch64] NEON, SVE2 and SME2 instruction support with tests

[AArch64] NEON, SVE2 and SME2 instruction support with tests #202

Triggered via pull request December 20, 2024 10:08
@FinnWilkinsonFinnWilkinson
synchronize #439
sme-loops-support
Status Failure
Total duration 2h 18m 47s
Artifacts –

MAIN.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
Fit to window
Zoom out
Zoom in

Annotations

96 errors and 8 warnings
Debug - build and test / ubuntu:20.04, gcc-8
Process completed with exit code 2.
Debug - build and test / ubuntu:20.04, gcc-8
Process completed with exit code 127.
Debug - build and test / ubuntu:20.04, gcc-8
Process completed with exit code 127.
Debug - build and test / ubuntu:20.04, gcc-10
Process completed with exit code 2.
Debug - build and test / ubuntu:20.04, gcc-10
Process completed with exit code 127.
Debug - build and test / ubuntu:20.04, gcc-10
Process completed with exit code 127.
Debug - build and test / ubuntu:20.04, gcc-7
Process completed with exit code 2.
Debug - build and test / ubuntu:20.04, gcc-7
Process completed with exit code 127.
Debug - build and test / ubuntu:20.04, gcc-7
Process completed with exit code 127.
Debug - build and test / rockylinux:8, gcc-9
Process completed with exit code 2.
Debug - build and test / rockylinux:8, gcc-9
Process completed with exit code 127.
Debug - build and test / rockylinux:8, gcc-9
Process completed with exit code 127.
Debug - build and test / ubuntu:20.04, gcc-9
Process completed with exit code 2.
Debug - build and test / ubuntu:20.04, gcc-9
Process completed with exit code 127.
Debug - build and test / ubuntu:20.04, gcc-9
Process completed with exit code 127.
Debug - build and test / rockylinux:8, gcc-10
Process completed with exit code 2.
Debug - build and test / rockylinux:8, gcc-10
Process completed with exit code 127.
Debug - build and test / rockylinux:8, gcc-10
Process completed with exit code 127.
Release - build, test and benchmarks / rockylinux:8, gcc-10
Process completed with exit code 2.
Release - build, test and benchmarks / rockylinux:8, gcc-10
Process completed with exit code 127.
Release - build, test and benchmarks / rockylinux:8, gcc-10
Process completed with exit code 127.
Release - build, test and benchmarks / ubuntu:20.04, gcc-10
Process completed with exit code 2.
Release - build, test and benchmarks / ubuntu:20.04, gcc-10
Process completed with exit code 127.
Release - build, test and benchmarks / ubuntu:20.04, gcc-10
Process completed with exit code 127.
Release - build, test and benchmarks / ubuntu:20.04, gcc-7
Process completed with exit code 2.
Release - build, test and benchmarks / ubuntu:20.04, gcc-7
Process completed with exit code 127.
Release - build, test and benchmarks / ubuntu:20.04, gcc-7
Process completed with exit code 127.
Release - build, test and benchmarks / ubuntu:20.04, gcc-8
Process completed with exit code 2.
Release - build, test and benchmarks / ubuntu:20.04, gcc-8
Process completed with exit code 127.
Release - build, test and benchmarks / ubuntu:20.04, gcc-8
Process completed with exit code 127.
Debug - build and test / debian:10, gcc-7
Process completed with exit code 2.
Debug - build and test / debian:10, gcc-7
Process completed with exit code 127.
Debug - build and test / debian:10, gcc-7
Process completed with exit code 127.
Debug - build and test / redhat/ubi8:latest, gcc-7
Process completed with exit code 2.
Debug - build and test / redhat/ubi8:latest, gcc-7
Process completed with exit code 127.
Debug - build and test / redhat/ubi8:latest, gcc-7
Process completed with exit code 127.
Debug - build and test / rockylinux:8, gcc-7
Process completed with exit code 2.
Debug - build and test / rockylinux:8, gcc-7
Process completed with exit code 127.
Debug - build and test / rockylinux:8, gcc-7
Process completed with exit code 127.
Release - build, test and benchmarks / debian:11, gcc-10
Process completed with exit code 2.
Release - build, test and benchmarks / debian:11, gcc-10
Process completed with exit code 127.
Release - build, test and benchmarks / debian:11, gcc-10
Process completed with exit code 127.
Release - build, test and benchmarks / redhat/ubi9:latest, gcc-10
Process completed with exit code 2.
Release - build, test and benchmarks / redhat/ubi9:latest, gcc-10
Process completed with exit code 127.
Release - build, test and benchmarks / redhat/ubi9:latest, gcc-10
Process completed with exit code 127.
Debug - build and test / debian:11, gcc-9
Process completed with exit code 2.
Debug - build and test / debian:11, gcc-9
Process completed with exit code 127.
Debug - build and test / debian:11, gcc-9
Process completed with exit code 127.
Debug - build and test / redhat/ubi9:latest, gcc-9
Process completed with exit code 2.
Debug - build and test / redhat/ubi9:latest, gcc-9
Process completed with exit code 127.
Debug - build and test / redhat/ubi9:latest, gcc-9
Process completed with exit code 127.
Release - build, test and benchmarks / debian:10, gcc-7
Process completed with exit code 2.
Release - build, test and benchmarks / debian:10, gcc-7
Process completed with exit code 127.
Release - build, test and benchmarks / debian:10, gcc-7
Process completed with exit code 127.
Debug - build and test / debian:11, gcc-10
Process completed with exit code 2.
Debug - build and test / debian:11, gcc-10
Process completed with exit code 127.
Debug - build and test / debian:11, gcc-10
Process completed with exit code 127.
Release - build, test and benchmarks / rockylinux:8, gcc-7
Process completed with exit code 2.
Release - build, test and benchmarks / rockylinux:8, gcc-7
Process completed with exit code 127.
Release - build, test and benchmarks / rockylinux:8, gcc-7
Process completed with exit code 127.
Debug - build and test / redhat/ubi9:latest, gcc-10
Process completed with exit code 2.
Debug - build and test / redhat/ubi9:latest, gcc-10
Process completed with exit code 127.
Debug - build and test / redhat/ubi9:latest, gcc-10
Process completed with exit code 127.
Release - build, test and benchmarks / redhat/ubi8:latest, gcc-7
Process completed with exit code 2.
Release - build, test and benchmarks / redhat/ubi8:latest, gcc-7
Process completed with exit code 127.
Release - build, test and benchmarks / redhat/ubi8:latest, gcc-7
Process completed with exit code 127.
Release - build, test and benchmarks / redhat/ubi9:latest, gcc-9
Process completed with exit code 2.
Release - build, test and benchmarks / redhat/ubi9:latest, gcc-9
Process completed with exit code 127.
Release - build, test and benchmarks / redhat/ubi9:latest, gcc-9
Process completed with exit code 127.
Release - build, test and benchmarks / debian:11, gcc-9
Process completed with exit code 2.
Release - build, test and benchmarks / debian:11, gcc-9
Process completed with exit code 127.
Release - build, test and benchmarks / debian:11, gcc-9
Process completed with exit code 127.
Debug - build and test / debian:11, gcc-8
Process completed with exit code 2.
Debug - build and test / debian:11, gcc-8
Process completed with exit code 127.
Debug - build and test / debian:11, gcc-8
Process completed with exit code 127.
Debug - build and test / redhat/ubi8:latest, gcc-8
Process completed with exit code 2.
Debug - build and test / redhat/ubi8:latest, gcc-8
Process completed with exit code 127.
Debug - build and test / redhat/ubi8:latest, gcc-8
Process completed with exit code 127.
Release - build, test and benchmarks / rockylinux:8, gcc-9
Process completed with exit code 2.
Release - build, test and benchmarks / rockylinux:8, gcc-9
Process completed with exit code 127.
Release - build, test and benchmarks / rockylinux:8, gcc-9
Process completed with exit code 127.
Debug - build and test / rockylinux:8, gcc-8
Process completed with exit code 2.
Debug - build and test / rockylinux:8, gcc-8
Process completed with exit code 127.
Debug - build and test / rockylinux:8, gcc-8
Process completed with exit code 127.
Release - build, test and benchmarks / ubuntu:20.04, gcc-9
Process completed with exit code 2.
Release - build, test and benchmarks / ubuntu:20.04, gcc-9
Process completed with exit code 127.
Release - build, test and benchmarks / ubuntu:20.04, gcc-9
Process completed with exit code 127.
Release - build, test and benchmarks / debian:11, gcc-8
Process completed with exit code 2.
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 / redhat/ubi8:latest, gcc-8
Process completed with exit code 2.
Release - build, test and benchmarks / redhat/ubi8:latest, gcc-8
Process completed with exit code 127.
Release - build, test and benchmarks / redhat/ubi8:latest, gcc-8
Process completed with exit code 127.
Release - build, test and benchmarks / rockylinux:8, gcc-8
Process completed with exit code 2.
Release - build, test and benchmarks / rockylinux:8, gcc-8
Process completed with exit code 127.
Release - build, test and benchmarks / rockylinux:8, gcc-8
Process completed with exit code 127.
Release - build, test and benchmarks / debian:11, gcc-10
Cache save failed.
Release - build, test and benchmarks / redhat/ubi9:latest, gcc-10
Cache save failed.
Release - build, test and benchmarks / debian:10, gcc-7
Cache save failed.
Release - build, test and benchmarks / rockylinux:8, gcc-7
Cache save failed.
Release - build, test and benchmarks / redhat/ubi8:latest, gcc-7
Cache save failed.
Release - build, test and benchmarks / debian:11, gcc-8
Cache save failed.
Release - build, test and benchmarks / redhat/ubi8:latest, gcc-8
Cache save failed.
Release - build, test and benchmarks / rockylinux:8, gcc-8
Cache save failed.