Skip to content

TRT-2255: Try two-stage testing in Sippy, version #1#68555

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
stbenjam:try-non-autorun-required
Aug 27, 2025
Merged

TRT-2255: Try two-stage testing in Sippy, version #1#68555
openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
stbenjam:try-non-autorun-required

Conversation

@stbenjam
Copy link
Member

@stbenjam stbenjam commented Aug 27, 2025

Manual pipelined version, autorun false, but not optional on e2e. PR when opened will run lint, unit, etc, but developer has to opt-in to e2e (/test remaining-required).

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 27, 2025
@stbenjam
Copy link
Member Author

/pj-rehearse ack

@openshift-ci-robot
Copy link
Contributor

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

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Aug 27, 2025
@stbenjam stbenjam changed the title Try two-stage testing in Sippy, version #1 TRT-2255: Try two-stage testing in Sippy, version #1 Aug 27, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 27, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Aug 27, 2025

@stbenjam: This pull request references TRT-2255 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.20.0" version, but no target version was set.

Details

In response to this:

Non-pipelined version, autorun false, but not optional on e2e. PR when opened will run lint, unit, etc, but developer has to opt-in to e2e (/test remaining-required).

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.

@smg247
Copy link
Member

smg247 commented Aug 27, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 27, 2025
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 54693f7 and 2 for PR HEAD af003c6 in total

Non-pipelined version, autorun false, but not optional on e2e.
@stbenjam stbenjam force-pushed the try-non-autorun-required branch from af003c6 to 3e14973 Compare August 27, 2025 16:23
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Aug 27, 2025
@openshift-ci-robot openshift-ci-robot removed the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Aug 27, 2025
@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@stbenjam: 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-sippy-main-e2e openshift/sippy presubmit Ci-operator config 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.

@stbenjam
Copy link
Member Author

/pj-rehearse ack

@openshift-ci-robot
Copy link
Contributor

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

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Aug 27, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Aug 27, 2025

@stbenjam: This pull request references TRT-2255 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.20.0" version, but no target version was set.

Details

In response to this:

Manual pipelined version, autorun false, but not optional on e2e. PR when opened will run lint, unit, etc, but developer has to opt-in to e2e (/test remaining-required).

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.

@smg247
Copy link
Member

smg247 commented Aug 27, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 27, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 27, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: smg247, 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:

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 27, 2025

@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.

@openshift-merge-bot openshift-merge-bot bot merged commit f0d29a1 into openshift:master Aug 27, 2025
15 checks passed
etmurasaki pushed a commit to etmurasaki/release that referenced this pull request Sep 3, 2025
Non-pipelined version, autorun false, but not optional on e2e.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants