Skip to content

CI

CI #497

Triggered via schedule April 10, 2026 18:32
Status Cancelled
Total duration 1d 0h 0m 2s
Artifacts –

ci.yml

on: schedule
pacman Build (Arch Linux)
1d 0h
pacman Build (Arch Linux)
Flatpack Build
1d 0h
Flatpack Build
Firmware Build
18s
Firmware Build
Windows Build
1d 0h
Windows Build
macOS Build
1d 0h
macOS Build
Matrix: build-dpkg
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 1 warning
macOS Build
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
pacman Build (Arch Linux)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
dpkg Build (ubuntu 22.04)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Windows Build
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
dpkg Build (ubuntu 20.04)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Flatpack Build
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
dpkg Build (debian 12.4)
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
Firmware Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/