fetch-related-triages

Fetch Related Triages

Queries the Sippy API to find existing triage records and untriaged regressions that may be related to a given Component Readiness regression. The API matches based on similarly named tests and shared job runs (using the complete job_runs history tracked across each regression's entire lifetime).

When to Use This Skill

• During regression analysis to find existing triages that could cover the current regression
• To find untriaged regressions that share the same root cause and should be triaged together
• To avoid filing duplicate bugs when a related triage already exists

API Endpoint

GET https://sippy.dptools.openshift.org/api/component_readiness/regressions/{id}/matches

No authentication required (uses production Sippy URL).

Usage

# Fetch all related triages (default: all confidence levels)
python3 plugins/ci/skills/fetch-related-triages/fetch_related_triages.py 35479

# Filter to high confidence matches only
python3 plugins/ci/skills/fetch-related-triages/fetch_related_triages.py 35479 --min-confidence 5

# Human-readable summary
python3 plugins/ci/skills/fetch-related-triages/fetch_related_triages.py 35479 --format summary

Arguments

• regression_id (required): The Component Readiness regression ID
• --min-confidence (optional): Minimum confidence level to include (1-10, default: 1)
• --format (optional): Output format — json (default) or summary

Confidence Levels

The API assigns a confidence level (1-10) to each match:

• 10: High confidence — the triage's regressions include the same test (exact test_id match) or very closely related tests with shared failure patterns
• 5: Medium confidence — similarly named tests matched by edit distance, suggesting related tests in the same area
• 2: Low confidence — regressions share the same job runs (identified via the job_runs history tracked across each regression's lifetime), which may indicate a shared root cause but could be coincidental in mass failure scenarios