From 15a31f95e474beb9babbafd3820b87964e6d2e21 Mon Sep 17 00:00:00 2001 From: kawa Date: Mon, 5 Oct 2026 13:37:14 +0200 Subject: [PATCH] Give the private browser checks 90 s per test (#66) On Docker-Builder1 the emulator comparisons now exceed Playwright's 30 s default (13 Chromium parity tests in run 136) although they pass locally in under 10 s. The job limit rises to 60 minutes to fit the slower runs. Co-Authored-By: Claude Opus 5.5 --- .gitea/workflows/private-checks.yml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/.gitea/workflows/private-checks.yml b/.gitea/workflows/private-checks.yml index ae431fb..d153f4b 100644 --- a/.gitea/workflows/private-checks.yml +++ b/.gitea/workflows/private-checks.yml @@ -12,7 +12,7 @@ jobs: runs-on: docker-build container: image: node:22-bookworm - timeout-minutes: 40 + timeout-minutes: 60 env: CRYSTAL_ROM_PATH: .reference/ci/crystal.gbc steps: @@ -46,8 +46,9 @@ jobs: run: npm test -- --maxWorkers=2 - run: npx playwright install --with-deps chromium webkit # One worker: with two, the runner host dropped off mid-run (runs 122, 130, 132, 134). + # The emulator comparisons can take over 30 s each on this host (run 136). - name: Chromium and WebKit gameplay and reference comparisons - run: npm run test:e2e -- --workers=1 --trace=off + run: npm run test:e2e -- --workers=1 --timeout=90000 --trace=off - name: Remove private data and browser output if: always() run: rm -rf .reference test-results playwright-report test-saves