Skip to content

Ring3: Fixed buggy timer interrupt handling for X64. #301

Ring3: Fixed buggy timer interrupt handling for X64.

Ring3: Fixed buggy timer interrupt handling for X64. #301

Triggered via push September 5, 2024 12:54
Status Failure
Total duration 34m 29s
Artifacts 2

build_nolto.yaml

on: push
Matrix: Test AMD
Matrix: Test ARM
Fit to window
Zoom out
Zoom in

Annotations

6 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)
Process completed with exit code 1.
Test AMD (Ovmf, Ia32,X64,3264, GCC, RELEASE,DEBUG)
Process completed with exit code 1.
Test AMD (Ovmf, Ia32,X64,3264, GCC, RELEASE,DEBUG)
Process completed with exit code 1.
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/
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/

Artifacts

Produced during runtime
Name Size
GCC Firmware Artifacts
7.18 MB
GCC Firmware NO_LTO Artifacts
3.82 MB