From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Noah Misch <noah(at)leadboat(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: fairywren hung in pg_basebackup tests |
Date: | 2022-07-25 15:24:13 |
Message-ID: | CA+hUKG+e2c0Y9eoh1inV4M=ewGMEPuKsHmY-y=_+ygvSxwxYYg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jul 26, 2022 at 3:08 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Dagfinn Ilmari Mannsåker | 2022-07-25 15:26:32 | Re: Unprivileged user can induce crash by using an SUSET param in PGOPTIONS |
Previous Message | Noah Misch | 2022-07-25 15:16:43 | Re: fairywren hung in pg_basebackup tests |