From 6fc41664a62f61862f8198b41934a7f4e51fa6f4 Mon Sep 17 00:00:00 2001 From: epalosh Date: Fri, 29 May 2026 16:11:28 -0500 Subject: [PATCH] CI: raise release build timeout to 360 min (cold Nuitka build) The v0.2.1 release run was cancelled at the 30-min job timeout while Nuitka was still compiling (28 min in, not done). A cold standalone build (MediaPipe + OpenCV + Qt, no ccache on a fresh 4-vCPU runner) needs more than 30 min. Set timeout-minutes to GitHub's per-job max (360) so the build can't be cut off; a healthy run stops as soon as it finishes. --- .github/workflows/release.yml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 92fecc3..20e8a75 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -27,7 +27,13 @@ jobs: build: name: Build installer runs-on: windows-latest - timeout-minutes: 30 + # Cold Nuitka standalone build (MediaPipe + OpenCV + Qt, no ccache on a + # fresh runner) runs ~30-40 min on a 4-vCPU runner — the v0.2.1 run was + # cancelled at the old 30 min mid-Nuitka. Set to GitHub's per-job max + # (360 min / 6h, the hosted-runner hard ceiling) so a slow cold build + # is never cut off; a healthy run stops the moment it finishes, so the + # high ceiling costs nothing. + timeout-minutes: 360 outputs: installer_name: ${{ steps.installer.outputs.name }} version: ${{ steps.version.outputs.version }}