lvms-ci:prow-job

What problem does it solve?

When a Prow CI job fails, the logs can be enormous and confusing, making it hard to quickly identify the true failure cause and avoid time-wasting triage.

Core Features & Use Cases

• Artifact-backed failure analysis: Downloads Prow/GCS artifacts (or uses a local artifacts directory) and scans logs to locate failure points with file and line context.
• Error classification by stack layer and severity: Determines whether the failure is a real test failure versus CI/infrastructure flake and assigns a severity (1–5) and stack layer.
• Structured reporting for automation: Outputs both a human-readable report and a machine-readable summary block for deduplication and downstream tooling.

Use case: analyze an LVMS e2e integration test failure by URL, quickly determine whether the failure is AWS infra, external CI/config, setup/deploy, or an actual LVMS/operator test regression, and generate a standardized report for engineers and issue trackers.

Quick Start

Run /lvms-ci:prow-job with a Prow job URL or a local artifacts directory that contains build-log.txt and finished.json to receive a severity-ranked, structured root-cause report.