-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Use latest instead of latest-fast for gce conformance #31486
Use latest instead of latest-fast for gce conformance #31486
Conversation
/cc @dims |
@upodroid: The following test 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. 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. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dims, upodroid 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 |
@upodroid: 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. |
When krel builds latest-fast.txt, it puts the marker in the wrong place. kubernetes/release#3403
For now, i'm using latest.txt to mitigate this.
kubetest2 assumes the following:
which breaks because when krel does a fast build, it stores it at https://storage.googleapis.com/k8s-release-dev/ci/fast/v1.30.0-alpha.0.341+d647d19f6aef81/kubernetes.tar.gz