From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: xid_wraparound tests intermittent failure. |
Date: | 2024-07-22 19:53:08 |
Message-ID: | 9d23c3bb-c037-45b4-b421-225b0fa83b80@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2024-07-22 Mo 12:46 PM, Tom Lane wrote:
> Masahiko Sawada<sawada(dot)mshk(at)gmail(dot)com> writes:
>> Looking at dodo's failures, it seems that while it passes
>> module-xid_wraparound-check, all failures happened only during
>> testmodules-install-check-C. Can we check the server logs written
>> during xid_wraparound test in testmodules-install-check-C?
> Oooh, that is indeed an interesting observation. There are enough
> examples now that it's hard to dismiss it as chance, but why would
> the two runs be different?
It's not deterministic.
I tested the theory that it was some other concurrent tests causing the
issue, but that didn't wash. Here's what I did:
for f in `seq 1 100`
do echo iteration = $f
meson test --suite xid_wraparound || break
done
It took until iteration 6 to get an error. I don't think my Ubuntu
instance is especially slow. e.g. "meson compile" normally takes a
handful of seconds. Maybe concurrent tests make it more likely, but they
can't be the only cause.
cheers
andrew
--
Andrew Dunstan
EDB:https://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Bossart | 2024-07-22 20:07:10 | Re: optimizing pg_upgrade's once-in-each-database steps |
Previous Message | Andres Freund | 2024-07-22 19:37:30 | Re: CI, macports, darwin version problems |