public inbox for [email protected]  

help / color / mirror / Atom feed

From: Andrew Dunstan <[email protected]>
To: vignesh C <[email protected]>
To: PostgreSQL Hackers <[email protected]>
Subject: Re: Random pg_upgrade 004_subscription test failure on drongo
Date: Thu, 13 Mar 2025 08:19:31 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CALDaNm3tjY44HoSwY84=XGEbTg0ruVfD4hAMTm=TgBqVysH4Qw@mail.gmail.com>
References: <CALDaNm3tjY44HoSwY84=XGEbTg0ruVfD4hAMTm=TgBqVysH4Qw@mail.gmail.com>


On 2025-03-13 Th 5:04 AM, vignesh C wrote:
> Hi,
>
> In one of the recent buildfarm runs, the test
> pg_upgrade/004_subscription test fails at [1].
> It has failed with the following:
> Restoring database schemas in the new cluster
> *failure*
>
> Consult the last few lines of
> "C:/prog/bf/root/HEAD/pgsql.build/testrun/pg_upgrade/004_subscription/data/t_004_subscription_new_sub_data/pgdata/pg_upgrade_output.d/20250310T194018.517/log/pg_upgrade_dump_1.log"
> for
> the probable cause of the failure.
> Failure, exiting
>
> Unfortunately we don't have pg_upgrade_output.d contents in buildfarm
> to see what is the exact reason.



That's not supposed to happen. I am testing a fix to see if I can make 
it collect the logs, but for now we'll have to wait till the next failure ..



cheers


andrew


--
Andrew Dunstan
EDB: https://www.enterprisedb.com

view thread (9+ messages)  latest in thread

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Random pg_upgrade 004_subscription test failure on drongo
  In-Reply-To: <[email protected]>

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

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