Fix run-smoke.yml overlapping-runs failure - #9
Merged
Conversation
Two PRs merging 37s apart each triggered their own push-to-main smoke run against the shared dev backend with no guard against overlap (unlike ci.yml, which got this same fix 2026-08-12). The second run hit a hard 120s pytest-timeout kill and failed with no report.json produced. Mirrors ci.yml's existing pattern.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
run-smoke.ymlagainst the shared dev backend. This workflow had noconcurrency:guard (unlikeci.yml, which got one 2026-08-12 for the identical reason).report.jsonwas produced — but for an infra reason, not a code defect.concurrencyblockci.ymlalready uses, adapted for this workflow's triggers (push/workflow_dispatch/workflow_call — nopull_request, so grouped bygithub.refalone).Test plan
actionlintcleanmainno longer produce an overlapping smoke run (second cancels the first instead of contending for the backend)