-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Add canary job for ci-ingress-gce-e2e #19762
Add canary job for ci-ingress-gce-e2e #19762
Conversation
8da7198
to
348b8b4
Compare
Duplicate of ci-ingress-gce-e2e that validates the job can run on k8s-infra-prow-build. Ref: kubernetes/k8s.io#1093 Part of : kubernetes#18549 Signed-off-by: Arnaud Meukam <ameukam@gmail.com>
348b8b4
to
ed4ea0c
Compare
/test pull-test-infra-bazel |
/assign @spiffxp |
/hold cancel |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ameukam, spiffxp The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@ameukam: Updated the
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/test-infra repository. |
By looking at : we can notice that the job has failed for a while. The canary fails with the same pattern: https://testgrid.k8s.io/sig-network-ingress-gce-e2e#ingress-gce-e2e. I don't think we need to migrate this job to the community clusters. |
Duplicate of
ci-ingress-gce-e2e
that validates the job can run onk8s-infra-prow-build.
Ref: kubernetes/k8s.io#1093
Part of : #18549
Signed-off-by: Arnaud Meukam ameukam@gmail.com