Fix smoke-claude: handle tool failures gracefully and guarantee safe output#14171
Fix smoke-claude: handle tool failures gracefully and guarantee safe output#14171
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
… outputs, reduce timeout to 10min Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
| run-success: "🎬 **THE END** — [{workflow_name}]({run_url}) **MISSION: ACCOMPLISHED!** The hero saves the day! ✨" | ||
| run-failure: "💫 **TO BE CONTINUED...** [{workflow_name}]({run_url}) {status}! Our hero faces unexpected challenges..." | ||
| timeout-minutes: 15 | ||
| timeout-minutes: 10 |
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Updates the Smoke Claude agentic workflow to better handle agentic-workflows MCP tool responses (including error cases), reduce runtime timeout, and strengthen guidance to always produce required safe outputs.
Changes:
- Reduce
smoke-claudeworkflow timeout from 15 to 10 minutes (and recompile lockfile). - Improve
agentic-workflowsMCP tool testing instructions to handle errors gracefully and still proceed to safe outputs. - Update output instructions to make issue creation mandatory regardless of test results.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
docs/src/content/docs/agent-factory-status.mdx |
Removes a malformed/extra workflow row from the status table. |
.github/workflows/smoke-claude.md |
Updates timeout and strengthens instructions for MCP tool error handling + mandatory safe output issue creation. |
.github/workflows/smoke-claude.lock.yml |
Recompiled workflow YAML reflecting the updated timeout/frontmatter hash. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| - ✅ or ❌ for each test result | ||
| - Overall status: PASS or FAIL | ||
|
|
||
| 3. Use the `add_comment` tool with `item_number` set to the discussion number you extracted in step 9 to add a **fun comic-book style comment** to that discussion - be playful and use comic-book language like "💥 WHOOSH!" |
There was a problem hiding this comment.
In Output step 3, the instructions say to call add_comment with item_number set to the extracted discussion number. Elsewhere in this workflow (step 9) and in other smoke workflows, discussions are targeted via discussion_number, and using item_number risks posting to an issue/PR with the same number instead of the discussion. Consider switching this to discussion_number: <extracted_number> for consistency and correctness.
| 3. Use the `add_comment` tool with `item_number` set to the discussion number you extracted in step 9 to add a **fun comic-book style comment** to that discussion - be playful and use comic-book language like "💥 WHOOSH!" | |
| 3. Use the `add_comment` tool with `discussion_number` set to the discussion number you extracted in step 9 to add a **fun comic-book style comment** to that discussion - be playful and use comic-book language like "💥 WHOOSH!" |
The smoke-claude workflow failed when the agentic-workflows tool returned errors, and didn't always create diagnostic issues on test failures. Timeout also exceeded the 10-minute target.
Changes
CRITICALdirective requiring issue creation before any other operationsExample
Before:
After:
Output section now explicitly requires issue creation:
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.