Skip to content
Build

DI unit balanced port allocation fix #150

Sign in to view logs

DI unit balanced port allocation fix

DI unit balanced port allocation fix #150

Triggered via pull request November 7, 2024 13:59
@FinnWilkinsonFinnWilkinson
synchronize #431
di-unit-updates
Status Failure
Total duration 1h 9m 22s
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 2 warnings
Debug - build and test / debian:11, gcc-8
Process completed with exit code 100.
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.
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 / 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/ubi9:latest, gcc-9
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/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.
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 / 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.
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 / 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.
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 / 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.
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-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 / 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 / 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.
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.
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 / 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.
Debug - build and test / ubuntu:18.04, gcc-7
Process completed with exit code 2.
Debug - build and test / ubuntu:18.04, gcc-7
Process completed with exit code 127.
Debug - build and test / ubuntu:18.04, gcc-7
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-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.
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 / 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 / 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.
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 / 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 / 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 / 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.
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.
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 / 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.
Release - build, test and benchmarks / ubuntu:18.04, gcc-7
Process completed with exit code 2.
Release - build, test and benchmarks / ubuntu:18.04, gcc-7
Process completed with exit code 127.
Release - build, test and benchmarks / ubuntu:18.04, gcc-7
Process completed with exit code 127.
Debug - build and test / ubuntu:18.04, gcc-7
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Release - build, test and benchmarks / ubuntu:18.04, gcc-7
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.