| From: | "Tharakan, Robins" <tharar(at)amazon(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | "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-02 04:27:48 |
| Message-ID: | bd9c2cba1e3941ebaff863675347c516@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I've now switched to GCC v13.2 and triggered a run. Let's see if the tests stabilize now.
So although HEAD ran fine, but I saw multiple failures (v12, v13, v16) all of which passed on subsequent-tries,
of which some were even"signal 6: Aborted".
FWIW, I compiled gcc v13.2 (default options) from source which IIUC shouldn't be to blame. Two other possible
reasons could be that the buildfarm doesn't have an aarch64 + gcc 13.2 combination (quick check I couldn't
see any), or, that this hardware is flaky.
Either way, this instance is a throw-away so let me know if this isn't helping. I'll swap it out in case there's not
much benefit to be had.
Also, it'd be great if someone could point me to a way to update the "Compiler" section in "System Detail" on
the buildfarm page (it wrongly shows GCC as v7.3.1).
-
thanks
robins
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-04-02 04:31:35 | Re: Why is parula failing? |
| Previous Message | Zhijie Hou (Fujitsu) | 2024-04-02 04:24:49 | RE: Synchronizing slots from primary to standby |