Skip to content

CI/CD

CI/CD #60

Triggered via pull request October 22, 2024 11:43
@ABenC377ABenC377
synchronize #437
CI_CD
Status Cancelled
Total duration 7m 14s
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

108 errors and 2 warnings
Debug - build and test / ubuntu:20.04, gcc-10
/home/runner/work/SimEng/SimEng/./.github/actions/setup_gcc_ubuntu/action.yml: (Line: 105, Col: 9, Idx: 3244) - (Line: 106, Col: 109, Idx: 3420): While parsing a block mapping, did not find expected key.
Debug - build and test / ubuntu:20.04, gcc-10
System.ArgumentException: Unexpected type '' encountered while reading 'action manifest root'. The type 'MappingToken' was expected. at GitHub.DistributedTask.ObjectTemplating.Tokens.TemplateTokenExtensions.AssertMapping(TemplateToken value, String objectDescription) at GitHub.Runner.Worker.ActionManifestManager.Load(IExecutionContext executionContext, String manifestFile)
Debug - build and test / ubuntu:20.04, gcc-10
Failed to load /home/runner/work/SimEng/SimEng/./.github/actions/setup_gcc_ubuntu/action.yml
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:18.04, gcc-7
/home/runner/work/SimEng/SimEng/./.github/actions/setup_gcc_ubuntu/action.yml: (Line: 105, Col: 9, Idx: 3244) - (Line: 106, Col: 109, Idx: 3420): While parsing a block mapping, did not find expected key.
Debug - build and test / ubuntu:18.04, gcc-7
System.ArgumentException: Unexpected type '' encountered while reading 'action manifest root'. The type 'MappingToken' was expected. at GitHub.DistributedTask.ObjectTemplating.Tokens.TemplateTokenExtensions.AssertMapping(TemplateToken value, String objectDescription) at GitHub.Runner.Worker.ActionManifestManager.Load(IExecutionContext executionContext, String manifestFile)
Debug - build and test / ubuntu:18.04, gcc-7
Failed to load /home/runner/work/SimEng/SimEng/./.github/actions/setup_gcc_ubuntu/action.yml
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.
Debug - build and test / ubuntu:20.04, gcc-8
/home/runner/work/SimEng/SimEng/./.github/actions/setup_gcc_ubuntu/action.yml: (Line: 105, Col: 9, Idx: 3244) - (Line: 106, Col: 109, Idx: 3420): While parsing a block mapping, did not find expected key.
Debug - build and test / ubuntu:20.04, gcc-8
System.ArgumentException: Unexpected type '' encountered while reading 'action manifest root'. The type 'MappingToken' was expected. at GitHub.DistributedTask.ObjectTemplating.Tokens.TemplateTokenExtensions.AssertMapping(TemplateToken value, String objectDescription) at GitHub.Runner.Worker.ActionManifestManager.Load(IExecutionContext executionContext, String manifestFile)
Debug - build and test / ubuntu:20.04, gcc-8
Failed to load /home/runner/work/SimEng/SimEng/./.github/actions/setup_gcc_ubuntu/action.yml
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-9
/home/runner/work/SimEng/SimEng/./.github/actions/setup_gcc_ubuntu/action.yml: (Line: 105, Col: 9, Idx: 3244) - (Line: 106, Col: 109, Idx: 3420): While parsing a block mapping, did not find expected key.
Debug - build and test / ubuntu:20.04, gcc-9
System.ArgumentException: Unexpected type '' encountered while reading 'action manifest root'. The type 'MappingToken' was expected. at GitHub.DistributedTask.ObjectTemplating.Tokens.TemplateTokenExtensions.AssertMapping(TemplateToken value, String objectDescription) at GitHub.Runner.Worker.ActionManifestManager.Load(IExecutionContext executionContext, String manifestFile)
Debug - build and test / ubuntu:20.04, gcc-9
Failed to load /home/runner/work/SimEng/SimEng/./.github/actions/setup_gcc_ubuntu/action.yml
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 / macos-13, gcc-10
/Users/runner/work/SimEng/SimEng/./.github/actions/setup_gcc_macos/action.yml: (Line: 57, Col: 9, Idx: 1735) - (Line: 57, Col: 45, Idx: 1771): While parsing a block mapping, did not find expected key.
Debug - build and test / macos-13, gcc-10
System.ArgumentException: Unexpected type '' encountered while reading 'action manifest root'. The type 'MappingToken' was expected. at GitHub.DistributedTask.ObjectTemplating.Tokens.TemplateTokenExtensions.AssertMapping(TemplateToken value, String objectDescription) at GitHub.Runner.Worker.ActionManifestManager.Load(IExecutionContext executionContext, String manifestFile)
Debug - build and test / macos-13, gcc-10
Failed to load /Users/runner/work/SimEng/SimEng/./.github/actions/setup_gcc_macos/action.yml
Debug - build and test / macos-13, gcc-10
Process completed with exit code 1.
Debug - build and test / macos-13, gcc-10
Process completed with exit code 1.
Release - build, test and benchmarks / ubuntu:20.04, gcc-10
/home/runner/work/SimEng/SimEng/./.github/actions/setup_gcc_ubuntu/action.yml: (Line: 105, Col: 9, Idx: 3244) - (Line: 106, Col: 109, Idx: 3420): While parsing a block mapping, did not find expected key.
Release - build, test and benchmarks / ubuntu:20.04, gcc-10
System.ArgumentException: Unexpected type '' encountered while reading 'action manifest root'. The type 'MappingToken' was expected. at GitHub.DistributedTask.ObjectTemplating.Tokens.TemplateTokenExtensions.AssertMapping(TemplateToken value, String objectDescription) at GitHub.Runner.Worker.ActionManifestManager.Load(IExecutionContext executionContext, String manifestFile)
Release - build, test and benchmarks / ubuntu:20.04, gcc-10
Failed to load /home/runner/work/SimEng/SimEng/./.github/actions/setup_gcc_ubuntu/action.yml
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 / macos-13, gcc-10
/Users/runner/work/SimEng/SimEng/./.github/actions/setup_gcc_macos/action.yml: (Line: 57, Col: 9, Idx: 1735) - (Line: 57, Col: 45, Idx: 1771): While parsing a block mapping, did not find expected key.
Release - build, test and benchmarks / macos-13, gcc-10
System.ArgumentException: Unexpected type '' encountered while reading 'action manifest root'. The type 'MappingToken' was expected. at GitHub.DistributedTask.ObjectTemplating.Tokens.TemplateTokenExtensions.AssertMapping(TemplateToken value, String objectDescription) at GitHub.Runner.Worker.ActionManifestManager.Load(IExecutionContext executionContext, String manifestFile)
Release - build, test and benchmarks / macos-13, gcc-10
Failed to load /Users/runner/work/SimEng/SimEng/./.github/actions/setup_gcc_macos/action.yml
Release - build, test and benchmarks / macos-13, gcc-10
Process completed with exit code 1.
Release - build, test and benchmarks / macos-13, gcc-10
Process completed with exit code 1.
Release - build, test and benchmarks / ubuntu:18.04, gcc-7
/home/runner/work/SimEng/SimEng/./.github/actions/setup_gcc_ubuntu/action.yml: (Line: 105, Col: 9, Idx: 3244) - (Line: 106, Col: 109, Idx: 3420): While parsing a block mapping, did not find expected key.
Release - build, test and benchmarks / ubuntu:18.04, gcc-7
System.ArgumentException: Unexpected type '' encountered while reading 'action manifest root'. The type 'MappingToken' was expected. at GitHub.DistributedTask.ObjectTemplating.Tokens.TemplateTokenExtensions.AssertMapping(TemplateToken value, String objectDescription) at GitHub.Runner.Worker.ActionManifestManager.Load(IExecutionContext executionContext, String manifestFile)
Release - build, test and benchmarks / ubuntu:18.04, gcc-7
Failed to load /home/runner/work/SimEng/SimEng/./.github/actions/setup_gcc_ubuntu/action.yml
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.
Release - build, test and benchmarks / debian:11, gcc-8
The run was canceled by @ABenC377.
Release - build, test and benchmarks / rockylinux:8, gcc-9
The run was canceled by @ABenC377.
Release - build, test and benchmarks / ubuntu:20.04, gcc-8
The run was canceled by @ABenC377.
Release - build, test and benchmarks / rockylinux:8, gcc-8
The run was canceled by @ABenC377.
Release - build, test and benchmarks / debian:11, gcc-9
The run was canceled by @ABenC377.
Release - build, test and benchmarks / ubuntu:20.04, gcc-9
The run was canceled by @ABenC377.
Release - build, test and benchmarks / debian:10, gcc-7
The run was canceled by @ABenC377.
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 / redhat/ubi9:latest, gcc-9
The run was canceled by @ABenC377.
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 / 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-8
The run was canceled by @ABenC377.
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 / debian:11, gcc-10
The run was canceled by @ABenC377.
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 / redhat/ubi9:latest, gcc-10
The run was canceled by @ABenC377.
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 / debian:10, gcc-7
The run was canceled by @ABenC377.
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 / debian:11, gcc-9
The run was canceled by @ABenC377.
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.
Release - build, test and benchmarks / debian:11, gcc-10
The run was canceled by @ABenC377.
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 / rockylinux:8, gcc-7
The run was canceled by @ABenC377.
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
The run was canceled by @ABenC377.
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 / rockylinux:8, gcc-9
The run was canceled by @ABenC377.
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 / rockylinux:8, gcc-8
The run was canceled by @ABenC377.
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 / rockylinux:8, gcc-7
The run was canceled by @ABenC377.
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 / 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 / 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.
Debug - build and test / redhat/ubi8:latest, gcc-8
The run was canceled by @ABenC377.
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.
Debug - build and test / redhat/ubi8:latest, gcc-7
The run was canceled by @ABenC377.
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 / macos-13, apple_clang_15
The run was canceled by @ABenC377.
Debug - build and test / macos-13, apple_clang_15
Process completed with exit code 1.
Debug - build and test / macos-13, apple_clang_15
Process completed with exit code 1.
Release - build, test and benchmarks / macos-13, apple_clang_15
Process completed with exit code 1.
Release - build, test and benchmarks / macos-13, apple_clang_15
Process completed with exit code 1.
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/.