skills.rest
openshift-eng
openshift-engOFFICIAL
Explore all skills by this author →
WebsiteGitHub

lvms-ci:prow-job

Analyze Prow CI job artifacts to classify test failures versus infrastructure flakes.

7|15|Updated Jan 23, 2026
Search Tags:#root cause#log analysis#ci#prow#gcs#structured reporting#test failure triage
One-click install
npx skills add https://github.com/openshift-eng/edge-tooling --skill lvms-ci-prow-job
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lvms-ci:prow-job
Source: https://github.com/openshift-eng/edge-tooling/tree/main/plugins/lvms-ci/skills/prow-job
Command: npx skills add https://github.com/openshift-eng/edge-tooling --skill lvms-ci-prow-job

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about lvms-ci:prow-job

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

FAQPage Schema
How do I find the root cause of a Prow CI job failure from build logs?▼

Analyze Prow CI artifacts by downloading job logs from Prow or GCS web URLs, scanning build-log and step logs for fatal errors with file context, and classifying the failure by stack layer and severity to identify the true root cause.

How do I tell if a test failure is an infrastructure flake or a real regression?▼

Distinguish infrastructure flakes from real test failures by analyzing log context around fatal errors, assigning a 1–5 severity score, and categorizing the stack layer to isolate AWS infra, external CI config, or actual LVMS operator regressions.

Can I analyze local Prow job artifacts instead of using a URL?▼

Yes, you can analyze local Prow job artifacts by pointing the tool to a pre-downloaded directory containing build-log.txt and finished.json, enabling deterministic log scanning and root-cause analysis without fetching from a Prow or GCS web URL.

How does structured reporting work for CI test failure triage?▼

Structured reporting for CI test failure triage generates a machine-readable summary block alongside a human-readable report, enabling automated error deduplication and seamless integration with downstream issue tracking and engineering tooling.

What is needed to start triaging an LVMS e2e integration test failure?▼

To start triaging an LVMS e2e integration test failure, you need a Prow job URL or a local artifacts directory containing build-log.txt and finished.json to generate a severity-ranked, structured root-cause report.

Related Skills

Explore More Software Engineering Skills→
openshift-engopenshift-eng
7

microshift-ci:prow-job

Analyzes Prow build logs to identify failing CI steps and classify root causes for MicroShift workflows.

Official
Advanced
J03Fr0stJ03Fr0st

to-tickets

Convert project plans and specifications into structured issue tracker tickets.

Community
Intermediate
openshift-engopenshift-eng

Prow Job Artifact Search

Search and retrieve Prow CI job artifacts from the test-platform-results GCS bucket.

Official
Intermediate
CygnusfearCygnusfear
5

axiom-audit

Query Axiom logs via APL to identify and prioritize errors and warnings.

Community
Advanced