ci/ui-test: queue runs in one bucket instead of cancelling #9

Merged
developer merged 1 commits from feature/ui-test-singleton into development 2026-05-15 06:57:09 +00:00
+10 -7
View File
@@ -16,14 +16,17 @@ on:
- '.gitea/workflows/ui-test.yaml' - '.gitea/workflows/ui-test.yaml'
- '!**/*.md' - '!**/*.md'
# Playwright launches its own `pnpm dev` on :5173. In host-mode the # Playwright launches its own `pnpm dev` on :5173, and in host-mode
# runner shares the host's port namespace, so two parallel ui-test # the runner shares the host's port namespace with every other job,
# jobs (e.g. a push event racing with a pull_request event for the # so two parallel ui-test runs collide on EADDRINUSE. Serialise via a
# same commit) collide on EADDRINUSE. Group by the head commit so # singleton concurrency group with queueing — new runs wait their
# push and pull_request events for the same sha share one bucket. # 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.
concurrency: concurrency:
group: ui-test-${{ gitea.event.pull_request.head.sha || gitea.sha }} group: ui-test-singleton
cancel-in-progress: true cancel-in-progress: false
jobs: jobs:
test: test: