The vibe-check bot has observed 5 review failures classified as unknown on deucebucket/deckdoc in the last 30 days.
This is almost certainly an infrastructure or environment problem — network reachability, self-hosted runner health, repo access scope, Azure content filter, etc. — rather than a defect in any individual PR. Repeatedly re-triggering reviews will not help until the root cause is addressed.
Representative stderr tail (last 500 chars):
ERROR: pms_review.py exited 1
Full audit trail: github-webhook/vibe-check-log.jsonl on the bot host — filter jq 'select(.repo=="deucebucket/deckdoc" and .status=="failed")'.
Opened automatically by failure_escalator.py (#54, routing refined in #56). Cooldown is 30 days per (original_repo, error_source) pair, so no duplicate issue will be created until then.
The vibe-check bot has observed 5 review failures classified as
unknownondeucebucket/deckdocin the last 30 days.This is almost certainly an infrastructure or environment problem — network reachability, self-hosted runner health, repo access scope, Azure content filter, etc. — rather than a defect in any individual PR. Repeatedly re-triggering reviews will not help until the root cause is addressed.
Representative stderr tail (last 500 chars):
Full audit trail:
github-webhook/vibe-check-log.jsonlon the bot host — filterjq 'select(.repo=="deucebucket/deckdoc" and .status=="failed")'.Opened automatically by
failure_escalator.py(#54, routing refined in #56). Cooldown is 30 days per (original_repo, error_source) pair, so no duplicate issue will be created until then.