developer/galaxy-game
1
1
Fork 0
Code Issues Pull Requests Actions Packages Releases Wiki Activity

ci: serialize go-unit/ui-test/integration on a shared concurrency group
Tests · Go / test (push) Has been cancelled
Details
Tests · Go / test (pull_request) Has been cancelled
Details
Tests · Integration / integration (pull_request) Has been cancelled
Details
Tests · UI / test (push) Waiting to run
Details
Tests · UI / test (pull_request) Successful in 3m11s
Details

Browse Source 
These three jobs run on the host runner, which shares a single workspace.
Run concurrently, they race on workspace teardown: ui-test's production
build leaves a root-owned ui/frontend/build that a sibling job's (non-root)
cleanup cannot remove, which then spuriously fails that job — observed
repeatedly on go-unit when it overlapped a ui-test build. Put all three in
one global concurrency group (galaxy-host-runner, cancel-in-progress:
false) so they run one at a time and never collide. CI becomes more serial
but the false failures stop.

This also subsumes ui-test's former ui-test-singleton group, which guarded
the Playwright :5173 port; the shared group preserves that guarantee.
This commit is contained in:
Ilia Denisov
2026-05-31 18:11:34 +02:00
parent 5d2f2bfc26
commit 046857177e
3 changed files with 28 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/ui-test.yaml
+9 -7
View File
@@ -18,14 +18,16 @@ on:
# Playwright launches its own `pnpm dev` on :5173, and in host-mode
# the runner shares the host's port namespace with every other job,
# so two parallel ui-test runs collide on EADDRINUSE. Serialise via a
# singleton concurrency group with queueing — new runs wait their
# turn instead of cancelling the in-progress one. cancel-in-progress
# is explicitly false because Gitea has shown spurious self-cancel
# behaviour under cancel-in-progress: true even when no other run
# shares the group.
# so two parallel ui-test runs collide on EADDRINUSE. Serialise via the
# shared `galaxy-host-runner` concurrency group (also used by go-unit and
# integration) with queueing — new runs wait their turn instead of
# cancelling the in-progress one. The shared group additionally avoids the
# host-workspace teardown race those jobs hit (see go-unit.yaml). New runs
# wait their turn; cancel-in-progress is explicitly false because Gitea has
# shown spurious self-cancel behaviour under cancel-in-progress: true even
# when no other run shares the group.
concurrency:
group: ui-test-singleton
group: galaxy-host-runner
cancel-in-progress: false
jobs: