Prow Job Analyze Test Failure

Analyzing Prow test failures involves downloading job artifacts and logs, then examining build-log.txt and event timelines to identify what broke. This skill automates that process: provide the Prow job URL and test name, and it retrieves artifacts, correlates logs and events, inspects related code, and generates a detailed failure report pinpointing the root cause.

You need the Prow job URL (from test-platform-results) and the specific test name that failed. The skill parses the URL, downloads build logs and interval files, and uses those artifacts to perform the initial investigation and produce a root-cause summary.

Yes. This skill is designed for Prow jobs running Kubernetes-based tests, including E2E scenarios. It analyzes interval files for E2E timelines, stack traces, and event logs to determine why tests failed in your CI/CD environment.

The report collects evidence from logs, events, and artifacts, then presents a structured summary of the failure, potential root causes, and supporting evidence from stack traces and code inspection. It correlates multiple log sources to pinpoint where and why the test broke.

No. The skill automates artifact download and log retrieval from the job URL, including build-log.txt and JSON/YAML event files. You provide only the job URL and test name; it handles the rest of the artifact gathering and analysis.