TRT-2795: Test Analysis: Regressions disappear when variant filters are applied

[openshift-trt-agent]

Summary

Fixes TRT-2795: Regressions disappear from the Test Analysis page when variant filters are applied.

• The variant filter comparison in TestRegressionsTable was extracting only the value part of regression variants via parseVariantName (e.g. "gcp" from "Platform:gcp") but comparing it against the full filter value ("Platform:gcp"), so the match always failed and all regressions were filtered out.
• Fixed by comparing the full variant string first (handles key:value filter values like Platform:gcp), then falling back to the parsed name (handles value-only filter values like never-stable and aggregated).

Test plan

• Verified with seed data that regressions display correctly without filters (3 regressions visible)
• Applied Platform:gcp positive filter, confirmed only the gcp regression (Add separate top ten lists for test failures with bugs and without bugs #3) is shown
• Applied NOT Platform:gcp negation filter, confirmed the two aws regressions (Initial #1, add web based reporting #2) are shown
• Default negation filters (never-stable, aggregated) continue to work correctly
• make lint passes
• make test passes (Go + Jest)

Screenshots

Before filter (no variant filter applied, 3 regressions visible):

With Platform:gcp filter (only regression #3 shown):

With NOT Platform:gcp filter (regressions #1 and #2 shown):

---

Generated with Claude Code

[openshift-ci-robot]

@openshift-trt-agent[bot]: This pull request references TRT-2795 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Summary

Fixes TRT-2795: Regressions disappear from the Test Analysis page when variant filters are applied.

• The variant filter comparison in TestRegressionsTable was extracting only the value part of regression variants via parseVariantName (e.g. "gcp" from "Platform:gcp") but comparing it against the full filter value ("Platform:gcp"), so the match always failed and all regressions were filtered out.
• Fixed by comparing the full variant string first (handles key:value filter values like Platform:gcp), then falling back to the parsed name (handles value-only filter values like never-stable and aggregated).

Test plan

• Verified with seed data that regressions display correctly without filters (3 regressions visible)
• Applied Platform:gcp positive filter, confirmed only the gcp regression (Add separate top ten lists for test failures with bugs and without bugs #3) is shown
• Applied NOT Platform:gcp negation filter, confirmed the two aws regressions (Initial #1, add web based reporting #2) are shown
• Default negation filters (never-stable, aggregated) continue to work correctly
• make lint passes
• make test passes (Go + Jest)

Screenshots

Before filter (no variant filter applied, 3 regressions visible):

With Platform:gcp filter (only regression #3 shown):

With NOT Platform:gcp filter (regressions #1 and #2 shown):

---

Generated with Claude Code

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

[openshift-ci]

Hi @openshift-trt-agent[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[smg247]

@coderabbitai review

[smg247]

/ok-to-test

[coderabbitai]

Action performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[smg247]

/ok-to-test

[smg247]

/test agentic-staging

[openshift-merge-bot]

Scheduling required tests:
/test e2e

[openshift-trt-agent]

Sippy Staging Environment

URL: https://removed-per-mailto-naturals.trycloudflare.com

This environment is built from this PR and will remain available for approximately 60 minutes (until ~12:51 UTC).

[smg247]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-trt-agent[bot], smg247

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [smg247]

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