Re: 002_pg_upgrade is broken for custom install

From: Álvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 002_pg_upgrade is broken for custom install
Date: 2025-04-04 11:31:59
Message-ID: 202504041131.fnobf5zxldqs@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2025-Apr-04, Ashutosh Bapat wrote:

> # test failed
> stderr:
> # Tests were run but no plan was declared and done_testing() was not seen.
> # Looks like your test exited with 29 just after 4.
>
> Doesn't look like it's expected.

Nope. Please have a look at the tmp_check/log/regress_002* log file --
that might contain a better indication of what the problem is.

--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2025-04-04 11:41:43 Re: 002_pg_upgrade is broken for custom install
Previous Message Ashutosh Bapat 2025-04-04 11:27:30 002_pg_upgrade is broken for custom install