Skip to content

[WIP] NO-JIRA: implement TEST_FOCUS support in step-registry test scripts#77530

Draft
xingxingxia wants to merge 1 commit intoopenshift:mainfrom
xingxingxia:test-focus-implementation
Draft

[WIP] NO-JIRA: implement TEST_FOCUS support in step-registry test scripts#77530
xingxingxia wants to merge 1 commit intoopenshift:mainfrom
xingxingxia:test-focus-implementation

Conversation

@xingxingxia
Copy link
Copy Markdown
Contributor

This PR is for #77059 (comment) with a separate PR. CC @everettraven , @ShazaAldawamneh

Add TEST_FOCUS parameter support to openshift-e2e-test, baremetalds-e2e-test,
and single-node-e2e-test step-registry scripts to enable focusing on specific
test patterns before applying TEST_SKIPS filtering.

This implementation allows jobs to use TEST_FOCUS to first filter tests
to run, then optionally apply TEST_SKIPS to exclude specific tests from
that focused set.
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 8, 2026
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 8, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 8, 2026

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

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@xingxingxia: This pull request explicitly references no jira issue.

Details

In response to this:

This PR is for #77059 (comment) with a separate PR. CC @everettraven , @ShazaAldawamneh

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
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 8, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: xingxingxia
Once this PR has been reviewed and has the lgtm label, please assign smg247 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:

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
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@xingxingxia: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-kube-state-metrics-main-okd-scos-e2e-aws-ovn openshift/kube-state-metrics presubmit Registry content changed
pull-ci-openshift-kube-state-metrics-main-e2e-aws openshift/kube-state-metrics presubmit Registry content changed
pull-ci-openshift-kube-state-metrics-release-5.0-e2e-aws openshift/kube-state-metrics presubmit Registry content changed
pull-ci-openshift-kube-state-metrics-release-4.23-e2e-aws openshift/kube-state-metrics presubmit Registry content changed
pull-ci-openshift-kube-state-metrics-release-4.22-e2e-aws openshift/kube-state-metrics presubmit Registry content changed
pull-ci-openshift-kube-state-metrics-release-4.21-okd-scos-e2e-aws-ovn openshift/kube-state-metrics presubmit Registry content changed
pull-ci-openshift-kube-state-metrics-release-4.21-e2e-aws openshift/kube-state-metrics presubmit Registry content changed
pull-ci-openshift-kube-state-metrics-release-4.20-e2e-aws openshift/kube-state-metrics presubmit Registry content changed
pull-ci-openshift-kube-state-metrics-release-4.19-e2e-aws openshift/kube-state-metrics presubmit Registry content changed
pull-ci-openshift-kube-state-metrics-release-4.18-e2e-aws openshift/kube-state-metrics presubmit Registry content changed
pull-ci-openshift-kube-state-metrics-release-4.17-e2e-aws openshift/kube-state-metrics presubmit Registry content changed
pull-ci-openshift-kube-state-metrics-release-4.16-e2e-aws openshift/kube-state-metrics presubmit Registry content changed
pull-ci-openshift-kube-state-metrics-release-4.15-e2e-aws openshift/kube-state-metrics presubmit Registry content changed
pull-ci-openshift-kube-state-metrics-release-4.14-e2e-aws openshift/kube-state-metrics presubmit Registry content changed
pull-ci-openshift-kube-state-metrics-release-4.13-e2e-aws openshift/kube-state-metrics presubmit Registry content changed
pull-ci-openshift-kube-state-metrics-release-4.12-e2e-aws openshift/kube-state-metrics presubmit Registry content changed
pull-ci-openshift-kube-state-metrics-release-4.11-e2e-aws openshift/kube-state-metrics presubmit Registry content changed
pull-ci-openshift-kube-state-metrics-release-4.10-e2e-aws openshift/kube-state-metrics presubmit Registry content changed
pull-ci-openshift-kube-state-metrics-release-4.9-e2e-aws openshift/kube-state-metrics presubmit Registry content changed
pull-ci-openshift-kube-state-metrics-release-4.8-e2e-aws openshift/kube-state-metrics presubmit Registry content changed
pull-ci-openshift-kube-state-metrics-release-4.7-e2e-aws openshift/kube-state-metrics presubmit Registry content changed
pull-ci-openshift-kube-state-metrics-release-4.6-e2e-aws openshift/kube-state-metrics presubmit Registry content changed
pull-ci-openshift-kube-state-metrics-main-e2e-aws-upgrade openshift/kube-state-metrics presubmit Registry content changed
pull-ci-openshift-kube-state-metrics-release-5.0-e2e-aws-upgrade openshift/kube-state-metrics presubmit Registry content changed
pull-ci-openshift-kube-state-metrics-release-4.23-e2e-aws-upgrade openshift/kube-state-metrics presubmit Registry content changed

A total of 19623 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs.

A full list of affected jobs can be found here
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants