Build Firmwares using GCC without Link Time Optimization

Ring3: Fixed PAN page faults. #319

Sign in to view logs

Triggered via push October 1, 2024 16:26

MikhailKrichanov

new-Ring3

Status Failure

Total duration 26m 44s

Artifacts 2

build_nolto.yaml

on: push

Linux GCC Common

Matrix: Test AMD

Matrix: Test ARM

Annotations

3 errors and 2 warnings

Test ARM (ArmVirtQemu, ARM,AARCH64, GCC, RELEASE,DEBUG)

Process completed with exit code 1.

Test ARM (ArmVirtQemu, ARM,AARCH64, GCC, RELEASE,DEBUG)

Process completed with exit code 1.

Test ARM (ArmVirtQemu, ARM,AARCH64, GCC, RELEASE,DEBUG)

Process completed with exit code 1.

Test AMD (Ovmf, Ia32,X64,3264, GCC, RELEASE,DEBUG)

The following actions use a deprecated Node.js version and will be forced to run on node20: robinraju/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Test ARM (ArmVirtQemu, ARM,AARCH64, GCC, RELEASE,DEBUG)

The following actions use a deprecated Node.js version and will be forced to run on node20: robinraju/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime

Name	Size
GCC Firmware Artifacts	7.18 MB
GCC Firmware NO_LTO Artifacts	3.85 MB