TRT-2571: Add "tests ran" filter to job runs table

[stbenjam]

Summary

• Adds a ran_test_names filter to the job runs table to find any job where a specific test executed, regardless of outcome (pass/fail/flake)
• Uses an EXISTS subquery against prow_job_run_tests at query time instead of adding to the materialized view
• Updates the test analysis page "See job runs" button to use this filter, showing all runs where the test ran rather than only failures

Jira: https://issues.redhat.com/browse/TRT-2571

Test plan

• Navigate to job runs table, add a filter on "Tests ran" column, verify it returns job runs where that test executed
• Verify "Failed tests" and "Flaked tests" filters still work as before
• Go to test analysis page, click "See job runs" button, verify it shows all runs (not just failures)

🤖 Generated with Claude Code

[openshift-ci-robot]

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-robot]

@stbenjam: This pull request references TRT-2571 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Summary

• Adds a ran_test_names filter to the job runs table to find any job where a specific test executed, regardless of outcome (pass/fail/flake)
• Uses an EXISTS subquery against prow_job_run_tests at query time instead of adding to the materialized view
• Updates the test analysis page "See job runs" button to use this filter, showing all runs where the test ran rather than only failures

Jira: https://issues.redhat.com/browse/TRT-2571

Test plan

• Navigate to job runs table, add a filter on "Tests ran" column, verify it returns job runs where that test executed
• Verify "Failed tests" and "Flaked tests" filters still work as before
• Go to test analysis page, click "See job runs" button, verify it shows all runs (not just failures)

🤖 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-ci-robot]

@stbenjam: This pull request references TRT-2571 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Summary

• Adds a ran_test_names filter to the job runs table to find any job where a specific test executed, regardless of outcome (pass/fail/flake)
• Uses an EXISTS subquery against prow_job_run_tests at query time instead of adding to the materialized view
• Updates the test analysis page "See job runs" button to use this filter, showing all runs where the test ran rather than only failures

Jira: https://issues.redhat.com/browse/TRT-2571

Test plan

• Navigate to job runs table, add a filter on "Tests ran" column, verify it returns job runs where that test executed
• Verify "Failed tests" and "Flaked tests" filters still work as before
• Go to test analysis page, click "See job runs" button, verify it shows all runs (not just failures)

🤖 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-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: stbenjam

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 [stbenjam]

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

[openshift-ci-robot]

@stbenjam: This pull request references TRT-2571 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 story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Summary

• Adds a ran_test_names filter to the job runs table to find any job where a specific test executed, regardless of outcome (pass/fail/flake)
• Uses an EXISTS subquery against prow_job_run_tests at query time instead of adding to the materialized view
• Updates the test analysis page "See job runs" button to use this filter, showing all runs where the test ran rather than only failures

Jira: https://issues.redhat.com/browse/TRT-2571

Test plan

• Navigate to job runs table, add a filter on "Tests ran" column, verify it returns job runs where that test executed
• Verify "Failed tests" and "Flaked tests" filters still work as before
• Go to test analysis page, click "See job runs" button, verify it shows all runs (not just failures)

🤖 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-ci-robot]

Scheduling required tests:
/test e2e

[openshift-ci]

@stbenjam: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.