microshift-ci:prow-job

Analyzing Prow CI logs for MicroShift failures involves scanning build-log and step-log artifacts to pinpoint the failing step and summarize the root cause. This classifies whether the failure is a legitimate test issue or a CI infrastructure problem.

The best way to triage noisy MicroShift e2e failures is by processing Prow job artifacts to locate the failing step. This generates a structured report that distinguishes legitimate test failures from CI infrastructure issues.

Yes, you can use a local artifacts directory for CI log analysis if it contains the required build-log.txt and finished.json files. This allows you to perform failure classification and root cause analysis without downloading artifacts directly from Prow or GCS.

SOS report extraction for MicroShift CI failure classification works by scanning MicroShift-related SOS artifacts to characterize journal and pod issues. This provides relevant evidence to determine whether a failure originates from the test logic or the infrastructure stack layer.

Yes, you need the build-log.txt and finished.json files to classify Prow CI failures accurately. These files provide the necessary context to determine if an error is a legitimate test failure or a CI infrastructure issue within the MicroShift pipeline.