Re: Inconsistent output handling in 002_pg_upgrade.pl test logs

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Joel Jacobson <joel(at)compiler(dot)org>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Inconsistent output handling in 002_pg_upgrade.pl test logs
Date: 2024-10-28 12:44:40
Message-ID: 3D0A223A-2D28-42B8-877F-337589C2A627@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 28 Oct 2024, at 13:38, Joel Jacobson <joel(at)compiler(dot)org> wrote:
>
> Hi hackers,
>
> I've noticed some inconsistency in 002_pg_upgrade.pl in how it handles output
> during test failures. Currently, it uses note to print the header:
>
> note "=== contents of $log ===\n";
>
> but print for the log content and footer:
>
> print slurp_file($log);
> print "=== EOF ===\n";

Ugh, nice catch.

> Option 1: Keep output together using note

> Option 2: Adjust header message for separate logs

> Thoughts on these options?

I would prefer to output this to the log only and not the TAP output, to avoid
the risk of not seeing the test output for all the log output on the screen.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message torikoshia 2024-10-28 13:05:03 Re: RFC: Logging plan of the running query
Previous Message Joel Jacobson 2024-10-28 12:38:12 Inconsistent output handling in 002_pg_upgrade.pl test logs