Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h6wDx-0004Q3-Je for pgsql-hackers@arkaria.postgresql.org; Thu, 21 Mar 2019 11:51:05 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h6wDw-00053A-6k for pgsql-hackers@arkaria.postgresql.org; Thu, 21 Mar 2019 11:51:04 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h6wDv-00052i-Ud for pgsql-hackers@lists.postgresql.org; Thu, 21 Mar 2019 11:51:03 +0000 Received: from feynman.df7cb.de ([195.49.152.168]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h6wDt-0005G1-NW for pgsql-hackers@lists.postgresql.org; Thu, 21 Mar 2019 11:51:03 +0000 Received: from msg.df7cb.de (unknown [IPv6:2003:5b:203b:100:7627:eaff:fe52:8e03]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by feynman.df7cb.de (Postfix) with ESMTPSA id 44Q4qm4mBQz3F1s; Thu, 21 Mar 2019 12:51:00 +0100 (CET) Date: Thu, 21 Mar 2019 12:51:00 +0100 From: Christoph Berg To: David Steele Cc: Alvaro Herrera , Peter Eisentraut , Tom Lane , Daniel Gustafsson , pgsql-hackers@lists.postgresql.org Subject: Re: Re: Reporting script runtimes in pg_regress Message-ID: <20190321115059.GF2687@msg.df7cb.de> References: <20190308131217.GA13043@alvherre.pgsql> <8a85bece-b18f-0433-acf3-d106b31f0271@pgmasters.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="r5Pyd7+fXNt84Ff3" Content-Disposition: inline In-Reply-To: <8a85bece-b18f-0433-acf3-d106b31f0271@pgmasters.net> User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --r5Pyd7+fXNt84Ff3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Re: David Steele 2019-03-20 <8a85bece-b18f-0433-acf3-d106b31f0271@pgmasters.net> > > > Oh, right. So the way to go would be to use _("FAILED "), and > > > ask translators to use the same length. > > > > Note there's no translation for pg_regress. All these _() markers are > > currently dead code. It seems hard to become motivated to translate > > that kind of program. I don't think it has much value, myself. > > This patch has been "Waiting on Author" since March 8th. Do you know when > you'll have a new version ready? Here is a new revision that blank-pads "ok" to the length of "FAILED". Christoph --r5Pyd7+fXNt84Ff3 Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="0001-Align-timestamps-in-pg_regress-output.patch" From cd2a5927b52473ca9c56e2e5142c257853429224 Mon Sep 17 00:00:00 2001 From: Christoph Berg Date: Thu, 21 Feb 2019 10:35:19 +0100 Subject: [PATCH] Align timestamps in pg_regress output --- src/test/regress/pg_regress.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/test/regress/pg_regress.c b/src/test/regress/pg_regress.c index a18a6f6c45..8111d95b1e 100644 --- a/src/test/regress/pg_regress.c +++ b/src/test/regress/pg_regress.c @@ -1799,7 +1799,7 @@ run_schedule(const char *schedule, test_function tfunc) } else { - status(_("ok")); + status(_("ok ")); /* align with FAILED */ success_count++; } @@ -1879,7 +1879,7 @@ run_single_test(const char *test, test_function tfunc) } else { - status(_("ok")); + status(_("ok ")); /* align with FAILED */ success_count++; } -- 2.20.1 --r5Pyd7+fXNt84Ff3--