From 7d2f3a048809bbd0de4e571818ab540a643e1482 Mon Sep 17 00:00:00 2001 From: Ken'ichi Ohmichi Date: Tue, 7 Aug 2018 02:06:10 +0000 Subject: [PATCH] HPA: Make dynamicRequestSizeInMillicores bigger HPA e2e tests specify 20 as requestSizeMillicores on resource-consumer for making CPU workload to test HPA feature, and the value is hard-coded as 20. That means the tests expect 2% CPU workload on every resource-consumer processes, but actual CPU usage(4 - 6%) is over than the expected usage on some environment. Then HPA scales many pods than the test expected, and the test is failed. To make these tests stable, this changes the value to 100 (10% CPU workload on each process). --- test/e2e/common/autoscaling_utils.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/e2e/common/autoscaling_utils.go b/test/e2e/common/autoscaling_utils.go index edd8a5370d4..0e0d202b8d4 100644 --- a/test/e2e/common/autoscaling_utils.go +++ b/test/e2e/common/autoscaling_utils.go @@ -43,7 +43,7 @@ import ( const ( dynamicConsumptionTimeInSeconds = 30 staticConsumptionTimeInSeconds = 3600 - dynamicRequestSizeInMillicores = 20 + dynamicRequestSizeInMillicores = 100 dynamicRequestSizeInMegabytes = 100 dynamicRequestSizeCustomMetric = 10 port = 80