From 26d48dbc6fcf63e4921e6f3192fd74cdd9932974 Mon Sep 17 00:00:00 2001 From: frstrtr Date: Thu, 18 Jun 2026 19:47:10 +0000 Subject: [PATCH] ci(qt): cap Qt WebEngine leak gate at timeout-minutes: 20 The leak harness wraps the run in `timeout 180`, but QtWebEngine spawns Chromium zygote/helper child processes that survive when timeout SIGTERMs only the immediate child. The orphans keep the xvfb-run pipe open, so the job hangs to the 360-min runner default instead of finishing. A job-level timeout-minutes makes the runner force-kill the whole process tree, so a hung gate costs ~20 min, not hours. continue-on-error semantics are unchanged (gate stays advisory during Qt bring-up). --- .github/workflows/build.yml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml index 8b59bcd54..65c826d31 100644 --- a/.github/workflows/build.yml +++ b/.github/workflows/build.yml @@ -302,6 +302,11 @@ jobs: qt-webengine: name: Qt WebEngine leak gate runs-on: ubuntu-24.04 + # Hard ceiling: orphaned QtWebEngine/Chromium helper children survive + # the inner `timeout 180`, holding the xvfb pipe open and hanging the + # job to the 360-min runner default. Cap it so a hung leak gate is + # force-killed (with its whole process tree) in minutes, not hours. + timeout-minutes: 20 steps: - uses: actions/checkout@v6