-
Notifications
You must be signed in to change notification settings - Fork 4.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
test: Use latest K8s build for scale tests #16701
Conversation
/test presubmit-kops-aws-small-scale-amazonvpc-using-cl2 |
/retest |
/test presubmit-kops-aws-small-scale-amazonvpc-using-cl2 |
1 similar comment
/test presubmit-kops-aws-small-scale-amazonvpc-using-cl2 |
/test presubmit-kops-aws-small-scale-amazonvpc-using-cl2 |
/test presubmit-kops-aws-scale-amazonvpc-using-cl2 |
/test presubmit-kops-aws-small-scale-amazonvpc-using-cl2 |
/test presubmit-kops-aws-scale-amazonvpc-using-cl2 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hakman 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 |
@hakuna-matatah next time we could add |
I think we could also facilitate that, but wondering why would we want to do that ? Do we want to run for many different versions ? Or just the latest ? |
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
Looks like test run succeeded but it looks like Prow job is stuck in running state - https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kops/16701/presubmit-kops-aws-scale-amazonvpc-using-cl2/1818245175466528768 |
Looks like test run succeeded but it looks like Prow job is stuck in running state - https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kops/16701/presubmit-kops-aws-scale-amazonvpc-using-cl2/1818245175466528768 that's probably kubernetes-sigs/prow#210 |
@hakuna-matatah: 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-sigs/prow repository. I understand the commands that are listed here. |
The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass. This bot retests PRs for certain kubernetes repos according to the following rules:
You can:
/retest |
it's also nice to be explicit in the job config, so we have more confidence that e.g. release-master-informing jobs actually run code from master, though we should always confirm by investigating the uploaded artifacts |
Want to test 1.31.beta to see if it works on AWS.