Re: fairywren hung in pg_basebackup tests - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: fairywren hung in pg_basebackup tests
Date
Msg-id CA+hUKG+e2c0Y9eoh1inV4M=ewGMEPuKsHmY-y=_+ygvSxwxYYg@mail.gmail.com
Whole thread Raw
In response to Re: fairywren hung in pg_basebackup tests  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: fairywren hung in pg_basebackup tests
List pgsql-hackers
On Tue, Jul 26, 2022 at 3:08 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I wrote:
> > Right, so the "glob" failed to find anything.  Seeing that this test
> > is new as of 534472375, which postdates fairywren's last successful
> > run, I'd guess that the "glob" needs adjustment for msys path names.

The test added by 534472375 is at the end, hundreds of lines later
than the one that appears to be failing.

> Hmm ... an alternative theory is that the test is fine, and what
> it's telling us is that get_dirent_type() is still wrong on msys.
> Would that end in this symptom?

Hmm, possibly yes (if it sees a non-symlink, it'll skip it).   If
someone can run the test on an msys system, perhaps they could put a
debugging elog() into the code modified by 9d3444dc to log d_name and
the d_type that is returned?  I'm struggling to understand why msys
would change the answer though.



pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: fairywren hung in pg_basebackup tests
Next
From: Dagfinn Ilmari Mannsåker
Date:
Subject: Re: Unprivileged user can induce crash by using an SUSET param in PGOPTIONS