Skip to content

Conversation

@petr-muller
Copy link
Member

@petr-muller petr-muller commented Feb 2, 2024

openshift/cluster-version-operator#1032 and openshift/cluster-version-operator#1033 add TP-sensitive behavior to CVO, so having optional, manually triggered jobs does not hurt

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 2, 2024
@openshift-ci openshift-ci bot requested review from DavidHurta and wking February 2, 2024 14:57
@petr-muller
Copy link
Member Author

/pj-rehearse

Copy link
Member

@wking wking left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No opinion on the rehersal output yet, but that's a separate label-set anyway. Diff inspection looks good to me:

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 2, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 2, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: petr-muller, wking

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

@petr-muller
Copy link
Member Author

/pj-rehearse

1 similar comment
@petr-muller
Copy link
Member Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

@petr-muller, pj-rehearse: unable prepare a candidate for rehearsal; rehearsals will not be run. This could be due to a branch that needs to be rebased. ERROR:

couldn't rebase candidate onto master: %!w(<nil>)

@petr-muller petr-muller force-pushed the optional-techpreview-jobs-for-cvo branch from 929dbb5 to 964b7b2 Compare February 26, 2024 17:45
@petr-muller
Copy link
Member Author

/pj-rehearse

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 26, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 26, 2024

New changes are detected. LGTM label has been removed.

@petr-muller
Copy link
Member Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

@petr-muller, pj-rehearse: unable prepare a candidate for rehearsal; rehearsals will not be run. This could be due to a branch that needs to be rebased. ERROR:

couldn't rebase candidate onto master: %!w(<nil>)

@petr-muller petr-muller force-pushed the optional-techpreview-jobs-for-cvo branch from 964b7b2 to 101cb6e Compare March 1, 2024 17:17
@petr-muller
Copy link
Member Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@petr-muller: 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-cluster-version-operator-master-e2e-agnostic-operator-techpreview openshift/cluster-version-operator presubmit Presubmit changed
pull-ci-openshift-cluster-version-operator-master-e2e-agnostic-ovn-techpreview openshift/cluster-version-operator presubmit Presubmit changed
pull-ci-openshift-cluster-version-operator-master-e2e-agnostic-ovn-upgrade-into-change-techpreview openshift/cluster-version-operator presubmit Presubmit changed
pull-ci-openshift-cluster-version-operator-master-e2e-agnostic-ovn-upgrade-out-of-change-techpreview openshift/cluster-version-operator presubmit Presubmit 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 abort to abort all active rehearsals

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.

@openshift-bot
Copy link
Contributor

Issues in openshift/release go stale after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 15d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 2, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 11, 2024

@petr-muller: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/rehearse/openshift/cluster-version-operator/master/e2e-agnostic-ovn-upgrade-out-of-change-techpreview 101cb6e link unknown /pj-rehearse pull-ci-openshift-cluster-version-operator-master-e2e-agnostic-ovn-upgrade-out-of-change-techpreview
ci/rehearse/openshift/cluster-version-operator/master/e2e-agnostic-ovn-upgrade-into-change-techpreview 101cb6e link unknown /pj-rehearse pull-ci-openshift-cluster-version-operator-master-e2e-agnostic-ovn-upgrade-into-change-techpreview
ci/rehearse/openshift/cluster-version-operator/master/e2e-agnostic-ovn-techpreview 101cb6e link unknown /pj-rehearse pull-ci-openshift-cluster-version-operator-master-e2e-agnostic-ovn-techpreview
ci/rehearse/openshift/cluster-version-operator/master/e2e-agnostic-operator-techpreview 101cb6e link unknown /pj-rehearse pull-ci-openshift-cluster-version-operator-master-e2e-agnostic-operator-techpreview
ci/prow/clusterimageset-validate 101cb6e link true /test clusterimageset-validate

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

@openshift-bot
Copy link
Contributor

Stale issue in openshift/release rot after 15d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 15d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 28, 2024
@openshift-bot
Copy link
Contributor

Rotten issues in openshift/release close after 15d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 13, 2024
@openshift-merge-robot
Copy link
Contributor

PR needs rebase.

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.

@openshift-ci openshift-ci bot closed this May 13, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 13, 2024

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues in openshift/release close after 15d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

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. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants