Skip to content

split GCP MCO g1/g2 longduration jobs into p1/p2/p3 for release-4.19#76308

Open
HarshwardhanPatil07 wants to merge 4 commits intoopenshift:mainfrom
HarshwardhanPatil07:split-gcp-mco-g1g2-to-p1p2p3
Open

split GCP MCO g1/g2 longduration jobs into p1/p2/p3 for release-4.19#76308
HarshwardhanPatil07 wants to merge 4 commits intoopenshift:mainfrom
HarshwardhanPatil07:split-gcp-mco-g1g2-to-p1p2p3

Conversation

@HarshwardhanPatil07
Copy link

Converts gcp-ipi-f14-longduration-mco-g1/g2 to p1/p2/p3 pattern in release-4.19.

The g1/g2 pattern used TEST_IMPORTANCE to split tests. The new p1/p2/p3 pattern
uses TEST_FILTERS with priority tags (P1&, P2&, ~P1&;~P2&)

Changes:

  • release-4.19: gcp-ipi-f14-longduration-mco-g1/g2 → p1/p2/p3

@HarshwardhanPatil07
Copy link
Author

/cc @ptalgulk01

Signed-off-by: HarshwardhanPatil07 <harshpat@redhat.com>
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 16, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

@ptalgulk01
Copy link
Contributor

/pj-rhearse periodic-ci-openshift-openshift-tests-private-release-4.19-amd64-nightly-gcp-ipi-f14-longduration-mco-p1

@ptalgulk01
Copy link
Contributor

/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.19-amd64-nightly-gcp-ipi-f14-longduration-mco-p1

@openshift-ci-robot
Copy link
Contributor

@ptalgulk01: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

Signed-off-by: HarshwardhanPatil07 <harshpat@redhat.com>
Signed-off-by: HarshwardhanPatil07 <harshpat@redhat.com>
@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@HarshwardhanPatil07: 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
periodic-ci-openshift-openshift-tests-private-release-4.19-amd64-nightly-gcp-ipi-f14-longduration-mco-p1 N/A periodic Periodic changed
periodic-ci-openshift-openshift-tests-private-release-4.19-amd64-nightly-gcp-ipi-f14-longduration-mco-p2 N/A periodic Periodic changed
periodic-ci-openshift-openshift-tests-private-release-4.19-amd64-nightly-gcp-ipi-f14-longduration-mco-p3 N/A periodic Periodic changed
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.

@HarshwardhanPatil07
Copy link
Author

/assign @HarshwardhanPatil07

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants