mirror of
https://github.com/QwenLM/qwen-code.git
synced 2026-08-22 15:15:18 +00:00
4694d11c5f
The review-pr job only checked qwen's exit code, the tee status, the timeout sentinel, and an empty log. When the model connection drops mid-review, qwen still exits 0 and emits a terminal stream-json result event with subtype=success / is_error=false whose text carries the inlined '[API Error: ...]'. All existing checks pass, so the job goes green without ever posting a review comment. Inspect the terminal result event explicitly: fail when it is missing, when is_error is true or subtype is not success, or when the result text contains an inlined API error. A failed check now triggers the existing fallback-comment step instead of a silent green success. Refs #5052 |
||
|---|---|---|
| .. | ||
| build-and-publish-image.yml | ||
| check-issue-completeness.yml | ||
| ci.yml | ||
| desktop-release.yml | ||
| docs-page-action.yml | ||
| e2e.yml | ||
| gemini-scheduled-pr-triage.yml | ||
| qwen-automated-issue-triage.yml | ||
| qwen-code-pr-review.yml | ||
| qwen-issue-followup-bot.yml | ||
| qwen-scheduled-issue-triage.yml | ||
| qwen-triage.yml | ||
| release-sdk-python.yml | ||
| release-sdk.yml | ||
| release-vscode-companion.yml | ||
| release.yml | ||
| sdk-python.yml | ||
| stale.yml | ||
| sync-cua-driver-to-oss.yml | ||
| sync-release-to-oss.yml | ||
| terminal-bench.yml | ||