pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Christoph Berg <myon@debian.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Daniel Gustafsson <daniel@yesql.se>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Reporting script runtimes in pg_regress
Date: Fri, 8 Mar 2019 13:21:19 +0100
Message-ID: <3eb194cf-b878-1f63-8623-6d6add0ed0b7@2ndquadrant.com> (raw)
In-Reply-To: <20190221093702.GA5238@msg.df7cb.de>
References: <20190218143028.GA3700@alvherre.pgsql>
	<28360.1550506699@sss.pgh.pa.us>
	<20190221093702.GA5238@msg.df7cb.de>

On 2019-02-21 10:37, Christoph Berg wrote:
> diff --git a/src/test/regress/pg_regress.c b/src/test/regress/pg_regress.c
> index a18a6f6c45..8080626e94 100644
> --- a/src/test/regress/pg_regress.c
> +++ b/src/test/regress/pg_regress.c
> @@ -1794,12 +1794,14 @@ run_schedule(const char *schedule, test_function tfunc)
>  				else
>  				{
>  					status(_("FAILED"));
> +					status("          "); /* align with failed (ignored) */
>  					fail_count++;
>  				}

So an issue here is that in theory "FAILED" etc. are marked for
translation but your spacers do not take that into account.  Personally,
I have no ambition to translate pg_regress, so we could remove all that.
 But it should be done consistently in either case.

I also think we shouldn't worry about the "failed (ignored)" case.  That
never happens, and I don't want to mess up the spacing we have now for
that.  I'd consider removing support for it altogether.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services




view thread (25+ messages)  latest in thread

Message-ID: <3eb194cf-b878-1f63-8623-6d6add0ed0b7@2ndquadrant.com>
Permalink:  ../3eb194cf-b878-1f63-8623-6d6add0ed0b7@2ndquadrant.com/
Also on:    postgresql.org/message-id/3eb194cf-b878-1f63-8623-6d6add0ed0b7@2ndquadrant.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: peter.eisentraut@2ndquadrant.com, myon@debian.org, tgl@sss.pgh.pa.us, alvherre@2ndquadrant.com, daniel@yesql.se, pgsql-hackers@lists.postgresql.org
  Subject: Re: Reporting script runtimes in pg_regress
  In-Reply-To: <3eb194cf-b878-1f63-8623-6d6add0ed0b7@2ndquadrant.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox