debug-stuck-eval

Diagnose stalled AI evaluations in the Hawk/Inspect framework.

25|11|Updated Feb 6, 2025
One-click install
npx skills add https://github.com/METR/inspect-action --skill debug-stuck-eval
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-stuck-eval
Source: https://github.com/METR/inspect-action/tree/main/.claude/skills/debug-stuck-eval
Command: npx skills add https://github.com/METR/inspect-action --skill debug-stuck-eval

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps diagnose and resolve issues when AI evaluations are not progressing as expected, preventing wasted time and resources.

Core Features & Use Cases

  • Status Checking: Quickly assess the state of running evaluations.
  • Log Analysis: Pinpoint errors and patterns causing evaluations to hang.
  • API Testing: Directly test external API connections to isolate issues.
  • Use Case: An evaluation has been running for hours with no new samples completed. Use this Skill to check its status, review logs for errors like "Retrying request to /responses", and test the API directly to find the root cause.

Quick Start

Use the debug-stuck-eval skill to check the status of eval-set-id '12345'.

Frequently Asked Questions about debug-stuck-eval

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix a stuck eval that is not progressing in Hawk?

To fix a stuck eval in Hawk, check the evaluation status with `hawk status`, analyze `hawk logs` for retry loops or 500 errors, and use `curl` to test the API connection directly to isolate the root cause.

Why does my Inspect AI evaluation hang with no samples completing?

An Inspect AI evaluation may hang due to API connectivity issues or server errors. Reviewing logs for repeated retry requests or 500 errors helps identify whether the runner is stuck waiting for unresponsive external endpoints.

What is the best way to troubleshoot 500 errors in an AI evaluation?

The best way to troubleshoot 500 errors in an AI evaluation is to use direct API testing via `curl` alongside log analysis. This isolates whether the failure originates from the evaluation runner or the external API provider.

How do I check the status of a frozen eval set?

You can check the status of a frozen eval set by running the `hawk status` command with the specific eval-set-id. This quickly assesses the state of the running evaluation to determine if it has stalled.

How to break a retry loop causing an eval timeout?

To break a retry loop causing an eval timeout, use `hawk logs` to pinpoint the failing requests, then test the targeted endpoint with `curl` to verify API health and resolve the underlying connection issue.