From 5111a6c8ab32e98bde9c50e7a37787b3ee9ea043 Mon Sep 17 00:00:00 2001 From: Logan Date: Wed, 12 Aug 2026 12:12:33 -0400 Subject: [PATCH] ci(e2e): run the WebKit project even when chromium fails MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The WebKit step had no `if:`, so a chromium failure skipped it — and chromium has been failing on the container's audio clock for every push of the last two sessions. The job log says `conclusion: skipped`, so the one place WebKit2GTK gets any coverage has produced no signal at all while the plan recorded a possible WebKit regression as unverified. --- .gitea/workflows/ci.yml | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/.gitea/workflows/ci.yml b/.gitea/workflows/ci.yml index f1b6b32..c7814d2 100644 --- a/.gitea/workflows/ci.yml +++ b/.gitea/workflows/ci.yml @@ -296,7 +296,15 @@ jobs: # assertion is an event payload, a testid, an attribute or backend # state, so a WebKit failure here is an engine bug, not baseline # noise. It costs ~11 s. + # + # `if: !cancelled()` because without it a chromium failure skips + # this step, and chromium has been failing on the container's + # audio clock — so the run that was the *only* source of WebKit + # signal quietly stopped producing any, and the plan spent a pass + # treating "CI also runs WebKit" as true when the job log said + # `conclusion: skipped`. - name: E2E — webkit + if: ${{ !cancelled() }} working-directory: /src env: YJ_E2E_WEBKIT: '1'