kawa/Crystal
2
0 Fork 0
Code Issues 41 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

Run the private browser checks with one worker (#66)
Checks / web (push) Successful in 2m55s
Details
Private ROM checks / private-rom (push) Failing after 35m31s
Details

Browse Source 
Four private runs lost the runner during the Chromium/WebKit step: the
log stops about a minute in, cleanup cannot start, and Docker-Builder1
stays offline until restarted. Halving the browser load tests whether
the host is running out of memory; the step has room in the 40-minute
limit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
kawaandClaude Opus 5.5 committed 2026-10-05 09:53:10 +02:00
1 parent 0d8ff442ce
commit 60fb65bf6a
1 file changed
+2 -1
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/private-checks.yml
+2 -1
View File
@@ -45,8 +45,9 @@ jobs:
- name: Unit and playthrough tests with the ROM - name: Unit and playthrough tests with the ROM
run: npm test -- --maxWorkers=2 run: npm test -- --maxWorkers=2
- run: npx playwright install --with-deps chromium webkit - run: npx playwright install --with-deps chromium webkit
# One worker: with two, the runner host dropped off mid-run (runs 122, 130, 132, 134).
- name: Chromium and WebKit gameplay and reference comparisons - name: Chromium and WebKit gameplay and reference comparisons
run: npm run test:e2e -- --workers=2 --trace=off run: npm run test:e2e -- --workers=1 --trace=off
- name: Remove private data and browser output - name: Remove private data and browser output
if: always() if: always()
run: rm -rf .reference test-results playwright-report test-saves run: rm -rf .reference test-results playwright-report test-saves