From 25a4758bcc864766ed8bdf09d79d1869f98c1b63 Mon Sep 17 00:00:00 2001 From: Patrick Ohly Date: Mon, 18 Nov 2024 12:44:34 +0100 Subject: [PATCH] testing: allow keeping detailed go test JUnit results Pruning of tests to the top-level test was added for jobs like pull-kubernetes-unit which run many tests. For other, more focused jobs like scheduler-perf benchmarking it would be nice to keep the more detailed information, in particular because it includes the duration per test case. --- hack/make-rules/test.sh | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/hack/make-rules/test.sh b/hack/make-rules/test.sh index 75fa127c7e8..afddf8df982 100755 --- a/hack/make-rules/test.sh +++ b/hack/make-rules/test.sh @@ -81,6 +81,8 @@ fi # Set to 'y' to keep the verbose stdout from tests when KUBE_JUNIT_REPORT_DIR is # set. KUBE_KEEP_VERBOSE_TEST_OUTPUT=${KUBE_KEEP_VERBOSE_TEST_OUTPUT:-n} +# Set to 'false' to disable reduction of the JUnit file to only the top level tests. +KUBE_PRUNE_JUNIT_TESTS=${KUBE_PRUNE_JUNIT_TESTS:-true} kube::test::usage() { kube::log::usage_from_stdin <