On Fri, Oct 7, 2022 at 7:17 PM Amit Langote <amitlangote09@gmail.com> wrote:
> On Fri, Oct 7, 2022 at 19:15 Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
>> On 2022-Oct-07, Amit Langote wrote:
>> > > Thanks for the heads up. Hmm, this I am not sure how to reproduce on
>> > > my own, so I am currently left with second-guessing what may be going
>> > > wrong on 32 bit machines with whichever of the 4 patches.
>> > >
>> > > For now, I'll just post 0001, which I am claiming has no semantic
>> > > changes (proof pending), to rule out that that one's responsible.
>> >
>> > Nope, not 0001. Here's 0001+0002.
I had forgotten to actually attach anything with that email.
>> Please note that you can set up a github repository so that cirrus-ci
>> tests whatever patches you like, without having to post them to
>> pg-hackers. See src/tools/ci/README, it takes three minutes if you
>> already have the account and repository.
>
> Ah, that’s right. Will do so, thanks for the suggestion.
I'm waiting to hear from GitHub Support to resolve an error I'm facing
trying to add Cirrus CI to my account.
--
Thanks, Amit Langote
EDB: http://www.enterprisedb.com
