-
Notifications
You must be signed in to change notification settings - Fork 38.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
bump(github.com/onsi/ginkgo):v1.2.0-94-g5ca1211 #43273
bump(github.com/onsi/ginkgo):v1.2.0-94-g5ca1211 #43273
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: smarterclayton
Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
9e18b17
to
c1161dd
Compare
Totally unscientific, but in the GCE e2e runs they normally take between 850-900s, and this first run finished in 799. Will run a few more times to get some better variance measurements. We may be able to bump parallelism too. |
@k8s-bot gce e2e test this |
1 similar comment
@k8s-bot gce e2e test this |
@k8s-bot verify test this |
@k8s-bot gce e2e test this |
969872c
to
05ff408
Compare
Looks like this improves GCE e2e run by 4-5 minutes on average. |
Readding label |
Picks up parallel execution improvements in Ginkgo that distribute jobs more evenly with parallel
05ff408
to
f654505
Compare
@k8s-bot bazel build this |
@k8s-bot cvm gce e2e test this |
Automatic merge from submit-queue (batch tested with PRs 43273, 44287, 44281) |
https://k8s-gubernator.appspot.com/builds/kubernetes-jenkins/logs/ci-kubernetes-e2e-gci-gce/ Brought variability from 25-34 minutes down to a much tighter 24-26 minutes. I think this is a success. |
Picks up parallel execution improvements in Ginkgo that distribute jobs more evenly with parallel runs. Opened after observing long tail runs in OpenShift - testing there showed a much more compact run in terms of CPU onsi/ginkgo#333
We'll need some soak time to be sure this has no issues.