-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
STONEBLD-2371 Tests for multi platform controller #51236
Conversation
Hi @stuartwdouglas. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test |
@stuartwdouglas |
@@ -16,6 +16,8 @@ ref: | |||
name: "release:latest" | |||
- env: CI_JBS_REQPROCESSOR_IMAGE | |||
name: "release:latest" | |||
- env: OTP_SERVER_IMAGE | |||
name: "release:latest" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
probably no need to add it here, because no job config currently uses this step plus devfiles will be deprecated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@stuartwdouglas wondering, would it make sense to temporarily update this script in this PR so it points to your e2e-tests PR and run rehearsal job to validate it works as expected?
a715e4f
to
9c18ff3
Compare
9c18ff3
to
60ec2fa
Compare
/pj-rehearse pull-ci-redhat-appstudio-multi-platform-controller-main-multi-platform-controller-e2e |
@psturc: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
60ec2fa
to
6f44475
Compare
@psturc any idea what those failures mean? |
/pj-rehearse pull-ci-redhat-appstudio-multi-platform-controller-main-multi-platform-controller-e2e |
@psturc: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse abort |
@psturc: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse abort |
@psturc: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
run regarding the error in check-gh-automation job - it complains about 'openshift-cherrypick-robot' not having access to the repo. afaik we don't use that bot in our org so I think we can ignore this error |
@stuartwdouglas otherwise the rehearsal job needs at least these changes to be addressed in order to be successful |
/test check-gh-automation |
/verify-owners |
/approve |
/pj-rehearse pull-ci-redhat-appstudio-multi-platform-controller-main-multi-platform-controller-e2e |
@psturc: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse pull-ci-redhat-appstudio-multi-platform-controller-main-multi-platform-controller-e2e |
@psturc: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
@psturc,
|
Issues in openshift/release go stale after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
6f44475
to
21f9f52
Compare
The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the openshift org. You can then trigger verification by writing
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
/pj-rehearse pull-ci-redhat-appstudio-multi-platform-controller-main-multi-platform-controller-e2e |
@psturc: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse pull-ci-redhat-appstudio-multi-platform-controller-main-multi-platform-controller-e2e |
@psturc: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
owner: rhtap | ||
product: ocp | ||
timeout: 1h0m0s | ||
version: "4.13" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we've updated all jobs to use 4.14
version: "4.13" | |
version: "4.14" |
release: | ||
architecture: amd64 | ||
channel: fast | ||
version: "4.13" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
version: "4.13" | |
version: "4.14" |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: stuartwdouglas The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@stuartwdouglas: The following tests failed, say
Full PR test history. Your PR dashboard. 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. |
Stale issue in openshift/release rot after 15d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
PR needs rebase. 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. |
Rotten issues in openshift/release close after 15d of inactivity. Reopen the issue by commenting /close |
@openshift-bot: Closed this PR. In response to this:
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. |
No description provided.