From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Justin Pryzby <pryzby(at)telsasoft(dot)com> |
Subject: | Re: longfin and tamandua aren't too happy but I'm not sure why |
Date: | 2022-09-28 05:48:17 |
Message-ID: | CA+hUKG+2w+7EmPrvXRf8GJS-2GbBTbaAEPRfrCJCSnMP2+ogAw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Sep 28, 2022 at 6:15 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> There may be a larger conversation to be had here about how
> much our CI infrastructure should be detecting. There seems
> to be a depressingly large gap between what that found and
> what the buildfarm is finding --- not only in portability
> issues, but in things like cpluspluscheck failures, which
> I had supposed CI would find.
+1, Andres had some sanitizer flags in the works (stopped by a weird
problem to be resolved first), and 32 bit CI would clearly be good.
It also seems that ARM is now available to us via CI (either Amazon's
or a Mac), which IIRC is more SIGBUS-y about alignment than x86?
FTR CI reported that cpluspluscheck failure and more[1], so perhaps we
just need to get clearer agreement on the status of CI, ie a policy
that CI had better be passing before you get to the next stage. It's
still pretty new...
[1] https://cirrus-ci.com/github/postgresql-cfbot/postgresql/commitfest/39/3711
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro Horiguchi | 2022-09-28 05:49:24 | Re: Fix some newly modified tab-complete changes |
Previous Message | Bharath Rupireddy | 2022-09-28 05:44:53 | Re: Extend win32 error codes to errno mapping in win32error.c |