Re: fairywren hung in pg_basebackup tests

From: Noah Misch <noah(at)leadboat(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: fairywren hung in pg_basebackup tests
Date: 2022-07-24 19:10:17
Message-ID: 20220724191017.GA3373621@rfd.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Jul 24, 2022 at 12:55:56PM -0400, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> > fairywren (msys2 animal) is currently hung in the pg_basebackup tests.
> > Here's the bottom of the regress log. I don't have further info as yet,
> > but can dig is someone has a suggestion.
>
> Hm, what's with the "Use of uninitialized value" warnings?

The warnings are sequelae of:

> > [13:11:33.593](0.000s) not ok 97 - one tablespace tar was created

From that, it follows that $tblspc_tars[0] is undef at:

PostgreSQL::Test::Utils::system_or_bail($tar, 'xf', $tblspc_tars[0],
'-C', $repTsDir);

> > # Running: C:/Windows/System32/tar xf  -C
> > C:\tools\nmsys64\home\pgrunner\bf\root\REL_15_STABLE\pgsql.build\src\bin\pg_basebackup\tmp_check\tmp_test_jVCb/tblspc1replica

I can confirm that Windows tar hangs when invoked that way. For preventing
the hang, the test file could die() or skip the tar-program-using section
after failing 'one tablespace tar was created'. That still leaves a question
about why pg_basebackup didn't make the tablespace tar file. I would check
010_pg_basebackup_main.log for clues about that.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Martin Kalcher 2022-07-24 19:29:39 Re: [PATCH] Introduce array_shuffle() and array_sample()
Previous Message Justin Pryzby 2022-07-24 19:09:59 Re: Schema variables - new implementation for Postgres 15