fix(qa): stop suite execution after the first failed scenario#113843
Merged
Conversation
Contributor
|
ClawSweeper status: review started. I am starting a fresh review of this pull request: fix(qa): stop suite execution after the first failed scenario This is item 1/1 in the current shard. Shard 0/1. This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking. Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted. |
Contributor
Author
|
Merged via squash.
|
github-actions Bot
pushed a commit
to Desicool/openclaw
that referenced
this pull request
Jul 26, 2026
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.
What Problem This Solves
Fixes an issue where QA operators running fail-fast suites could not use the flag through the normal host or profile CLI, and mixed flow, native, script, and Multipass runs continued launching work after the first failure. Missing started scenario results could also produce misleading successful or incomplete evidence.
Why This Change Was Made
Routes fail-fast through the canonical host, profile, Multipass, native runner, and existing stop-aware unified scheduler. Separately tracks submitted, started, and actually returned scenarios so execution, reports, and evidence all stop at the same failure boundary. Synthesizes canonical failed evidence for missing started results, retains producer-owned evidence, and preserves ordinary weighted parallel scheduling when fail-fast is disabled.
User Impact
QA users can stop unnecessary gateways, browser tests, scripts, and VM work immediately after the first genuine failure. The generated suite report, summary, and evidence accurately distinguish failed started scenarios from work that never ran.
Evidence