Skip to content

Smoke Copilot

Smoke Copilot #1698

Triggered via pull request February 5, 2026 02:01
Status Success
Total duration 4m 6s
Artifacts 6

smoke-copilot.lock.yml

on: pull_request
pre_activation
12s
pre_activation
activation
10s
activation
detection
24s
detection
safe_outputs
15s
safe_outputs
send_slack_message
6s
send_slack_message
update_cache_memory
6s
update_cache_memory
conclusion
10s
conclusion
Fit to window
Zoom out
Zoom in

Annotations

2 errors, 10 warnings, and 2 notices
safe_outputs
✗ Message 2 (dispatch_workflow) failed: Failed to dispatch workflow "haiku-printer": No ref found for: refs/pull/13809/merge
safe_outputs
Failed to dispatch workflow "haiku-printer": No ref found for: refs/pull/13809/merge
agent
- Line 5: add_labels requires a 'labels' field (array)
agent
Validation errors found:
agent
Failed to process file /tmp/gh-aw/mcp-logs/rpc-messages.jsonl: EACCES: permission denied, open '/tmp/gh-aw/mcp-logs/rpc-messages.jsonl'
agent
Failed to process file /tmp/gh-aw/mcp-logs/mcp-gateway.log: EACCES: permission denied, open '/tmp/gh-aw/mcp-logs/mcp-gateway.log'
agent
File workflows/smoke-copilot.md contains front matter which will be ignored in runtime import
safe_outputs
1 message(s) were skipped because no handler was loaded. Check your workflow's safe-outputs configuration.
safe_outputs
2 message(s) failed to process
safe_outputs
Skipped (no handler): 1
safe_outputs
⚠️ No handler loaded for message type 'send_slack_message' (message 6/6). The message will be skipped. This may happen if the safe output type is not configured in the workflow's safe-outputs section.
safe_outputs
Target was not found (may have been deleted): Not Found
agent
Safe Inputs MCP Server Startup Log
agent
Safe Outputs MCP Server Startup Log

Artifacts

Produced during runtime
Name Size Digest
agent-artifacts
179 KB
sha256:b7c62e7e222f0b81e1682f1d8c60b85d12451298e00d03d2ddba2949b20a3e09
agent-output
1.31 KB
sha256:653f9692391cf20adce95c7e89121b2afee5392e87598f02ff0992eae2c84b75
agent_outputs
76.7 KB
sha256:65de652d4cafd1d8486559be53f4b16251805932dbeb224d8fa74b322738c020
cache-memory
1.58 KB
sha256:41ef7fde9c5cc7726eddc31771841273572a91459a98e6c464a9a39be7406404
safe-output
1.26 KB
sha256:61a165f1cf4caf180f46f63bf07e3aa53d6eb4b75ac8fe43653fcd8dadb60545
threat-detection.log
495 Bytes
sha256:61cc04429c71e145b4b2c1d9613ab1063707f3c543088ccd3a200343ac7093d1