Re: Why is parula failing?

From: Robins Tharakan <tharakan(at)gmail(dot)com>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, "Tharakan, Robins" <tharar(at)amazon(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Why is parula failing?
Date: 2024-04-15 05:42:32
Message-ID: CAEP4nAxHumpB89p7YBv9xPEYRRp9sVfS_KA1++z4z0PmLtdu6Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 15 Apr 2024 at 14:55, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> If GetNowFloat() somehow was returning a negative number then we could
> end up with a large delay. But if gettimeofday() was so badly broken
> then wouldn't there be some evidence of this in the log timestamps on
> failing runs?

3 things stand out for me here, unsure if they're related somehow:

1. Issue where reltuples=48 (in essence runs complete, but few tests fail)
2. SIGABRT - most of which are DDLs (runs complete, but engine crashes +
many tests fail)
3. pg_sleep() stuck - (runs never complete, IIUC never gets reported to
buildfarm)

For #3, one thing I had done earlier (and then reverted) was to set the
'wait_timeout' from current undef to 2 hours. I'll set it again to 2hrs
in hopes that #3 starts getting reported to buildfarm too.

> I'm not that familiar with the buildfarm config, but I do see some
> Valgrind related setting in there. Is PostgreSQL running under
> Valgrind on these runs?

Not yet. I was tempted, but valgrind has not yet been enabled on
this member. IIUC by default they're disabled.

'use_valgrind' => undef,

-
robins

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2024-04-15 05:47:54 Re: TerminateOtherDBBackends code comments inconsistency.
Previous Message David Rowley 2024-04-15 05:24:56 Re: Why is parula failing?