Feat: Multi-Release Historical Analysis and Regression Detection

[knabben]

Description

The handbook requires flagging regressions as close to the source as possible (when offending code was merged). Currently, signalhound does not track test history or detect regressions.

Requirements

• Track test history across multiple releases
• Detect regressions (failures after code merge)
• Identify PRs that introduced failures
• Link failures to specific commits/PRs
• Generate regression reports

Acceptance Criteria

• Test history is tracked across releases
• Regressions are detected (failures after merge)
• PRs that introduced failures are identified
• Failures are linked to commits/PRs
• Regression reports are generated
• Unit tests for regression detection
• Integration tests with historical data

Implementation Notes

• Query TestGrid for historical test data
• Query GitHub API for PR/commit information
• Match test failures to PR merge dates
• Generate regression timeline
• Support --detect-regressions command

[knabben]

Related to: #22

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten