-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Move vsphere periodic job to release-next branch, remove from 0.8.1 branch. #5367
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
Move vsphere periodic job to release-next branch, remove from 0.8.1 branch. #5367
Conversation
|
Failures are expected due to the |
mgencur
left a comment
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.
Hi @markusthoemmes I left one comment which probably needs clarification.
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.
I'm not sure this whole thing will work because of this template. For other Knative tests we use https://github.com/openshift/release/blob/master/ci-operator/templates/openshift/installer/cluster-launch-installer-src.yaml which uses this image to execute our tests: https://github.com/openshift/release/blob/master/ci-operator/templates/openshift/installer/cluster-launch-installer-src.yaml#L15 . It needs to actually include our source. The upi-e2e.yaml template seems to use a different image and I suppose it will only include OpenShift test suite, not Knative sources/test suites. Better to check with @stevekuznetsov or @petr-muller
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.
I am not familiar with the cluster-launch-installer-upi-e2e template, but what @mgencur says is correct - it would be probably a good idea to get in touch with whoever wrote/owns that template and check if it's able to do what you expect to do.
|
/test pj-rehearse |
1 similar comment
|
/test pj-rehearse |
348957a to
e68ae2f
Compare
e68ae2f to
09bfcf7
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: markusthoemmes The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test pj-rehearse |
7 similar comments
|
/test pj-rehearse |
|
/test pj-rehearse |
|
/test pj-rehearse |
|
/test pj-rehearse |
|
/test pj-rehearse |
|
/test pj-rehearse |
|
/test pj-rehearse |
|
@markusthoemmes: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions 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. |
As per title, this moves the periodic vsphere job over to the release-next branch.
Also tries to circumvent make based problems by sidestepping it.