From 79cff6cd1072f28d67730fe4ee50a173086b061e Mon Sep 17 00:00:00 2001 From: Aaron Crickenberger Date: Fri, 16 Aug 2019 16:26:28 -0700 Subject: [PATCH] Demote regular resource tracking tests from release-blocking Add a Feature:RegularResourceUsageTracking tag to these tests so they're not picked up by the release-blocking job that focuses on [Serial] tests (but excludes [Feature:.*] tests) They take a combined 65 minutes on average. If they really need to be in release-blocking as implemented, we should consider a separate job to focus just on this feature. --- test/e2e/node/kubelet_perf.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/e2e/node/kubelet_perf.go b/test/e2e/node/kubelet_perf.go index 96d8de99e41..245c2b1c997 100644 --- a/test/e2e/node/kubelet_perf.go +++ b/test/e2e/node/kubelet_perf.go @@ -215,7 +215,7 @@ var _ = SIGDescribe("Kubelet [Serial] [Slow]", func() { result := om.GetLatestRuntimeOperationErrorRate() e2elog.Logf("runtime operation error metrics:\n%s", e2ekubelet.FormatRuntimeOperationErrorRate(result)) }) - SIGDescribe("regular resource usage tracking", func() { + SIGDescribe("regular resource usage tracking [Feature:RegularResourceUsageTracking]", func() { // We assume that the scheduler will make reasonable scheduling choices // and assign ~N pods on the node. // Although we want to track N pods per node, there are N + add-on pods