Re: Test 026_overwrite_contrecord fails on very slow machines (under Valgrind)

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Alexander Lakhin <exclusion(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Test 026_overwrite_contrecord fails on very slow machines (under Valgrind)
Date: 2023-10-18 06:26:40
Message-ID: ZS96oP3mViEk1eqx@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 12, 2023 at 04:46:02PM -0700, Andres Freund wrote:
> The machine skink is hosted on runs numerous buildfarm animals (24 I think
> right now, about to be 28). While it has plenty resources (16 cores/32
> threads, 128GB RAM), test runtime is still pretty variable depending on what
> other tests are running at the same time...

Okay. It seems to me that just setting checkpoint_timeout to 1h
should leave plenty of room to make sure that the test is not unstable
compared to the default of 5 mins. So, why not just do that and see
what happens for a few days?
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2023-10-18 06:39:16 Re: Remove wal_level settings for subscribers in tap tests
Previous Message Peter Eisentraut 2023-10-18 06:16:47 Re: Clean up some pg_dump tests