From 80d3cc30277b8c3915caf33865f969c0b202aaad Mon Sep 17 00:00:00 2001 From: Patrick Ohly Date: Tue, 30 Aug 2022 19:36:01 +0200 Subject: [PATCH] e2e: suppress progress messages for custom progress reporter The custom progress reporter gets invoked via ginkgo.ReportAfterEach after each test. The problem was that the e2e framework unconditionally enables Ginkgo's -progress output which shows execution of all nodes, including this ReportAfterEach. The effect were over 1000 lines of useless output at the start of a test run while skipping disabled tests. The solution is to tell Ginkgo that the ReportAfterEach isn't meant to be reported. --- test/e2e/e2e_test.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/e2e/e2e_test.go b/test/e2e/e2e_test.go index b59232597b6..0c885270479 100644 --- a/test/e2e/e2e_test.go +++ b/test/e2e/e2e_test.go @@ -141,7 +141,7 @@ func TestE2E(t *testing.T) { var _ = ginkgo.ReportAfterEach(func(report ginkgo.SpecReport) { progressReporter.ProcessSpecReport(report) -}) +}, ginkgo.SuppressProgressReporting) var _ = ginkgo.ReportAfterSuite("Kubernetes e2e suite report", func(report ginkgo.Report) { var err error