From 443112706ac503a1b25c2338f4f1ca09ec888d0c Mon Sep 17 00:00:00 2001 From: andreBurnt <5591226+andreBurnt@users.noreply.github.com> Date: Sun, 6 Sep 2026 07:28:33 -0700 Subject: [PATCH] Maestro (local): queue pending runs in the maestro-test concurrency group With the default (queue: single), a run that finishes Build APK while another run is already pending in the maestro-test group cancels that pending run, which then never gets a Maestro verdict for its commit. queue: max keeps the one-at-a-time constraint (no cancel-in-progress) and lets up to 100 runs wait, at no runner cost. Fixes #7654 Co-Authored-By: Claude Fable 5.1 --- .github/workflows/maestro-local.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.github/workflows/maestro-local.yml b/.github/workflows/maestro-local.yml index 739c67764a..274ddf1dfb 100644 --- a/.github/workflows/maestro-local.yml +++ b/.github/workflows/maestro-local.yml @@ -75,8 +75,11 @@ jobs: needs: [ build-apk ] # Allow only one to run at a time, since they use the same environment. # Otherwise, tests running in parallel can break each other. + # queue: max lets several runs wait their turn instead of the default, where a + # newly queued run cancels the one already pending (that run then never gets a verdict). concurrency: group: maestro-test + queue: max steps: - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 if: (github.event_name == 'pull_request' && github.event.pull_request.fork == null) || github.event_name == 'workflow_dispatch'