fix(qa): keep smoke profile on one channel#101173
Merged
Merged
Conversation
Member
Author
|
@clawsweeper re-review |
Contributor
|
🦞👀 Command router queued. I will update this comment with the next step. |
Member
|
Maintainer review complete and land-ready. Evidence:
The fix keeps automatic Crabline profiles on the default Telegram channel while preserving explicit non-default scenario selection and the suite's mixed-channel rejection. |
Member
|
Merged via squash.
|
RomneyDa
added a commit
that referenced
this pull request
Jul 6, 2026
github-actions Bot
pushed a commit
to Desicool/openclaw
that referenced
this pull request
Jul 7, 2026
github-actions Bot
pushed a commit
to Desicool/openclaw
that referenced
this pull request
Jul 7, 2026
giodl73-repo
pushed a commit
to giodl73-repo/openclaw
that referenced
this pull request
Jul 8, 2026
giodl73-repo
pushed a commit
to giodl73-repo/openclaw
that referenced
this pull request
Jul 8, 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
Resolves a problem where the
smoke-ciQA profile selected Telegram, Matrix, Slack, and WhatsApp scenarios together, causing CI to fail before scenario execution because one QA suite run supports only one channel driver instance.Why This Change Was Made
Automatic Crabline profile selection now keeps channel-unpinned scenarios plus Crabline's default Telegram scenarios. Explicitly requested non-default scenarios still infer and use their declared channel, and the suite's mixed-channel rejection remains unchanged.
User Impact
QA Smoke CI can start its deterministic scenario run instead of failing during planning when the shared catalog contains scenarios for several channels. Explicit channel-focused QA commands retain their existing behavior.
Evidence
28818865466, job85465286235selected Telegram, Matrix, Slack, and WhatsApp and exited before any scenario execution.tbx_01kwwgg5zsdwddrngk045s9dd7: the smoke profile selected 92 scenarios and failed with the same four-channel planning error.extensions/qa-lab/src/cli.runtime.test.tspassed 91/91.extensions/qa-lab/src/mantis/**; exact-head hosted CI is the typecheck authority..agents/skills/autoreview/scripts/autoreview --mode local --stream-engine-output --prompt '<scoped qa-smoke-selector review>'completed clean with no accepted/actionable findings (patch is correct, confidence0.86).AI-assisted change; implementation and evidence were reviewed and validated as described above.