Re: Intermittent buildfarm failures on wrasse

Andres Freund <andres@anarazel.de>

From: Andres Freund <andres@anarazel.de>

To: Noah Misch <noah@leadboat.com>

Cc: Tom Lane <tgl@sss.pgh.pa.us>, Peter Geoghegan <pg@bowt.ie>, David Rowley <dgrowleyml@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2022-04-15T05:12:05Z

Lists: pgsql-hackers

Hi,

On 2022-04-14 19:45:15 -0700, Noah Misch wrote:
> I suspect the failure is somehow impossible in "check".  Yesterday, I cranked
> up the number of locales, so there are now a lot more installcheck.  Before
> that, each farm run had one "check" and two "installcheck".  Those days saw
> ten installcheck failures, zero check failures.

I notice that the buildfarm appears to run initdb with syncing enabled
("syncing data to disk ... ok" in the initdb steps).  Whereas pg_regress
uses --no-sync.

I wonder if that's what makes the difference? Now that you reproduced
it, does it still reproduce with --no-sync added?

Also worth noting that pg_regress doesn't go through pg_ctl...

Greetings,

Andres Freund

Commits

Repurpose PROC_COPYABLE_FLAGS as PROC_XMIN_FLAGS
- 8d9d1286acf9 14.4 landed
- 8d061acd12af 15.0 landed
- 5fd0cccc116b 13.8 landed
Tighten ComputeXidHorizons' handling of walsenders.
- 6fea65508a1a 15.0 landed
Adjust VACUUM's removable cutoff log message.
- 357c8455e649 15.0 landed
Temporarily add some probes of tenk1's relallvisible in create_index.sql.
- 5bb2b6abc8d6 15.0 landed
Set synchronous_commit=on in test_setup.sql.
- 02fea8fdda65 15.0 cited
Rearrange core regression tests to reduce cross-script dependencies.
- cc50080a828d 15.0 cited
snapshot scalability: Don't compute global horizons while building snapshots.
- dc7420c2c927 14.0 cited