RE: Why is parula failing?

Tharakan, Robins <tharar@amazon.com>

From: "Tharakan, Robins" <tharar@amazon.com>
To: Tom Lane <tgl@sss.pgh.pa.us>, David Rowley <dgrowleyml@gmail.com>
Cc: "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>
Date: 2024-04-02T02:06:14Z
Lists: pgsql-hackers
> ... in connection with which, I can't help noticing that parula is using a very old compiler:
>
> configure: using compiler=gcc (GCC) 7.3.1 20180712 (Red Hat 7.3.1-17)
>
> From some quick checking around, that would have to be near the beginning of aarch64
> support in RHEL (Fedora hadn't promoted aarch64 to a primary architecture until earlier
> that same year).  It's not exactly hard to believe that there were some lingering compiler bugs.

> I wonder why parula is using that when its underlying system seems markedly newer (the kernel at least has a recent build date).

Parula used GCC v7.3.1 since that's what came by default.
I've now switched to GCC v13.2 and triggered a run. Let's see if the tests stabilize now.
-
Robins



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Revert "Temporarily install debugging in partition_prune test"

  2. Temporarily install debugging in partition_prune test

  3. Review wording on tablespaces w.r.t. partitioned tables