feat: add recency indicator to most-flaky-tests report

[dhiller]

What this PR does / why we need it:

Adds visual distinction between actively flaky tests and stale entries in the most-flaky-tests report, so reviewers can focus on tests that are currently failing.

• Tests with recent consistent failures: red left border + "active" badge
• Tests with only stale failures: dimmed (60% opacity) with gray border + "stale" badge (hover restores full opacity)
• Reuses HasMinRecentFailures filter from fix: require recent consistent failures for auto-quarantine #5125 with the same configurable flags

Which issue(s) this PR fixes:

Depends on #5125

Special notes for your reviewer:

• Unit tests verify HasRecentFailures flag is set correctly for recent and stale candidates
• All quarantine tests pass, go vet clean

🤖 Assisted by Claude Code

[kubevirt-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign tiraboschi for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[gemini-code-assist]

Code Review

This pull request introduces a mechanism to filter test impacts based on the recency, count, and interval of build failures, adding new configuration options (max-failure-age, min-recent-failures, and min-failure-interval) to the auto-quarantine and flaky test reporting tools. The HTML report has also been updated to visually distinguish active and stale failures. The review feedback highlights a potential index out of range panic in HasMinRecentFailures when recentIntervals is empty, suggests adding validation to prevent negative values for the new configuration parameters, and recommends moving the instantiation of recentFailureFilter outside of the loop to avoid redundant allocations.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

If minCount is configured to 0 (or a negative value) and recentIntervals is empty, len(recentIntervals) < minCount evaluates to false. The code then proceeds to access recentIntervals[0] on line 179, which will cause an index out of range panic. Adding an explicit check for len(recentIntervals) == 0 prevents this panic.

Suggested change

	if len(recentIntervals) < minCount {
	return false
	}
	if len(recentIntervals) == 0 || len(recentIntervals) < minCount {
	return false
	}

[gemini-code-assist]

Please add validation for these new numeric configuration parameters to ensure they are not negative, preventing invalid configurations.

You can define a Validate method on autoQuarantineOptions and call it in the command runners (e.g., AutoQuarantine and MostFlakyTestsReport):

func (a autoQuarantineOptions) Validate() error {
	if a.maxFailureAge < 0 {
		return fmt.Errorf("max-failure-age cannot be negative")
	}
	if a.minRecentFailures < 0 {
		return fmt.Errorf("min-recent-failures cannot be negative")
	}
	if a.minFailureInterval < 0 {
		return fmt.Errorf("min-failure-interval cannot be negative")
	}
	return nil
}

References

1. When validating numeric configuration parameters such as timeouts or durations, ensure that negative values are explicitly handled, for example by returning an error, to prevent invalid configurations.

[gemini-code-assist]

recentFailureFilter is independent of the loop variables and can be instantiated once outside the for _, topXTest := range topXTests loop (before line 177) to avoid redundant allocations on every iteration.