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
[WIP] [TEST ONLY] Serverless: Use own cluster pool #50032
Conversation
[REHEARSALNOTIFIER]
A total of 368 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 Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
/pj rehearse pull-ci-openshift-knative-serverless-operator-main-415-operator-e2e-aws-415 |
/pj-rehearse pull-ci-openshift-knative-serverless-operator-main-415-operator-e2e-aws-415 |
Hmm. Pj-rehearse doesn't react. Re-opening the PR |
/pj-rehearse pull-ci-openshift-knative-serverless-operator-main-415-operator-e2e-aws-415 |
/pj-rehearse pull-ci-openshift-knative-serverless-operator-main-412-operator-e2e-aws-412 This should spin up a new cluster |
/pj-rehearse pull-ci-openshift-knative-serverless-operator-main-415-operator-e2e-aws-415 Checking once again. |
@mgencur: all tests passed! 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/test-infra repository. I understand the commands that are listed here. |
It works. Closing. |
Testing changes from openshift-knative/hack#134