Closed t0yv0 closed 4 months ago
:tropical_drink: The Update for pulumi/k8s-ci-cluster/001078a09025ede8e4f69d4b94319a3ca387fd66-1688 was successful.
Name Type Operation
+ multicloud pulumi-kubernetes:ci:GkeCluster create
+ password random:index/randomPassword:RandomPassword create
+ ephemeral-ci-cluster gcp:container/cluster:Cluster create
+ primary-node-pool gcp:container/nodePool:NodePool create
+ gke pulumi:providers:kubernetes create
+ k8s-ci-cluster-001078a09025ede8e4f69d4b94319a3ca387fd66-1688 pulumi:pulumi:Stack create
:tropical_drink: The Destroy for pulumi/k8s-ci-cluster/001078a09025ede8e4f69d4b94319a3ca387fd66-1688 was successful.
Name Type Operation
- gke pulumi:providers:kubernetes delete
- primary-node-pool gcp:container/nodePool:NodePool delete
- ephemeral-ci-cluster gcp:container/cluster:Cluster delete
- multicloud pulumi-kubernetes:ci:GkeCluster delete
- password random:index/randomPassword:RandomPassword delete
- k8s-ci-cluster-001078a09025ede8e4f69d4b94319a3ca387fd66-1688 pulumi:pulumi:Stack delete
AFAIK TestAccAwsTsHelloFargate failure should not be affected by these changes. I think I can merge, LMK if need to revert.
Before the change, benchmarks ran in parallel. We are observing very high variance no the benchmarks, part of the problem could be resource contention for network bandwidth across benchmarks. This change will give the entire runner's worth of resources to each benchmark individually, and hopefully reduce variance at the cost of using more CI runner time. Will observe for 1 week and evaluate.