From 251f57460f123f28089ff23a7e43990618dd05a8 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Thu, 17 Jan 2019 19:31:03 -0500 Subject: [PATCH] Avoid assuming that we know the spelling of getopt_long's error messages. I've had enough of "fixing" this test case. Whatever value it has is limited to verifying that pgbench fails for an unrecognized switch, and we don't need to assume anything about what getopt_long prints in order to do that. Discussion: https://postgr.es/m/9427.1547701450@sss.pgh.pa.us --- src/bin/pgbench/t/002_pgbench_no_server.pl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/bin/pgbench/t/002_pgbench_no_server.pl b/src/bin/pgbench/t/002_pgbench_no_server.pl index b78057d050..69a6d03bb3 100644 --- a/src/bin/pgbench/t/002_pgbench_no_server.pl +++ b/src/bin/pgbench/t/002_pgbench_no_server.pl @@ -66,7 +66,7 @@ my @options = ( [ 'bad option', '-h home -p 5432 -U calvin -d --bad-option', - [ qr{(unrecognized|illegal) option}, qr{--help.*more information} ] + [qr{--help.*more information}] ], [ 'no file', -- 2.40.0