From b4b7edcc5d75e16de8b8db01949be484f3f02968 Mon Sep 17 00:00:00 2001 From: Sascha Grunert Date: Tue, 8 Nov 2022 16:00:51 +0100 Subject: [PATCH] Fix typo in `--progress` deprecation message (#1076) Signed-off-by: Sascha Grunert Signed-off-by: Sascha Grunert --- types/config.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/types/config.go b/types/config.go index 84ee93790..4ec636eb2 100644 --- a/types/config.go +++ b/types/config.go @@ -301,7 +301,7 @@ var SuiteConfigFlags = GinkgoFlags{ {KeyPath: "D.RegexScansFilePath", DeprecatedName: "regexScansFilePath", DeprecatedDocLink: "removed--regexscansfilepath", DeprecatedVersion: "2.0.0"}, {KeyPath: "D.DebugParallel", DeprecatedName: "debug", DeprecatedDocLink: "removed--debug", DeprecatedVersion: "2.0.0"}, {KeyPath: "D.EmitSpecProgress", DeprecatedName: "progress", SectionKey: "debug", - DeprecatedVersion: "2.5.0", Usage: ". The funcitonality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck."}, + DeprecatedVersion: "2.5.0", Usage: ". The functionality provided by --progress was confusing and is no longer needed. Use --show-node-events instead to see node entry and exit events included in the timeline of failed and verbose specs. Or you can run with -vv to always see all node events. Lastly, --poll-progress-after and the PollProgressAfter decorator now provide a better mechanism for debugging specs that tend to get stuck."}, } // ParallelConfigFlags provides flags for the Ginkgo test process (not the CLI)