Skip to main content

Overview

The investigate-ci-failure tool investigates a failing CI run by fetching structured test failure data from Trunk. Given a GitHub Actions workflow URL, this tool looks up test result bundles, parses them to extract test names and error messages, filters out quarantined (known-flaky) tests, and returns structured failure details the agent can act on. For more information, see Autofix CI Failures. Return Type: Structured failure details with test names, error messages, stdout, and stderr. If the CI job failed before tests ran (build or compilation failure), the tool suggests pulling raw logs from the workflow URL as a fallback.

Prerequisites

Parameters

Required Parameters

Optional Parameters

Getting Parameter Values

Get workflow URL: Navigate to your GitHub Actions run and copy the full URL from your browser’s address bar. It follows the pattern:

Usage Examples

Investigate a workflow failure

What the tool does

  • Looks up test result uploads Trunk has received for that run
  • Parses the test runs to extract test names, error messages, stdout and stderr
  • Filters out quarantined (known-flaky) tests so you only see real failures
  • Returns structured failure details you can act on
When tests didn’t run: If the CI job failed before any tests ran (e.g., a build or compilation failure), the tool will tell you so and suggest pulling raw CI logs directly from the workflow URL as a fallback.

Error Handling