On Sun, Sep 25, 2022 at 04:50:54PM -0400, Hamid Akhtar wrote:
> On Sun, 28 Aug 2022 at 17:30, Nathan Bossart <nathandbossart@gmail.com> wrote:
>
> > On Thu, Aug 25, 2022 at 10:12:00AM +0530, Bharath Rupireddy wrote:
> > > Please review the v12 patch attached.
> >
> > LGTM. I've marked this as ready-for-committer.
> >
>
> This patch needs an update. It is failing on Windows for the test case
> "33/238 postgresql:pg_upgrade / pg_upgrade/002_pg_upgrade with an
> "exit status 2" error.
>
> The details are available on the cfbot.cputue.org.
> https://cirrus-ci.com/task/5709014662119424?logs=check_world#L267
It failed like:
https://api.cirrus-ci.com/v1/artifact/task/5709014662119424/testrun/build/testrun/pg_upgrade/002_pg_upgrade/log/regress_log_002_pg_upgrade
[19:35:31.017](76.307s) ok 10 - run of pg_upgrade for new instance
[19:35:31.017](0.000s) not ok 11 - pg_upgrade_output.d/ removed after pg_upgrade success
[19:35:31.018](0.001s) # Failed test 'pg_upgrade_output.d/ removed after pg_upgrade success'
# at C:/cirrus/src/bin/pg_upgrade/t/002_pg_upgrade.pl line 261.
This is a transient failure; it normally passes:
https://cirrus-ci.com/github/postgresql-cfbot/postgresql/commitfest/39/3389
Actually, it's the same problem as reported here:
20220919213217.ptqfdlcc5idk5xup@awork3.anarazel.de
I don't think there's anything in place to help scrape the cirrusci
logs, but I suppose other patches have had/will have this same failure.
I don't know but maybe meson made this worse, by exercising/stressing
concurrent filesystem operations.
--
Justin
