Re: Building with musl in CI and the build farm

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: walther(at)technowledgy(dot)de, Andres Freund <andres(at)anarazel(dot)de>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Building with musl in CI and the build farm
Date: 2024-04-04 13:56:25
Message-ID: 7764f41f-29f6-428f-b40d-43ba2da38170@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On 31.03.24 15:34, walther(at)technowledgy(dot)de wrote:
>> I'd rather adapt one of the existing tasks, to avoid increasing CI
>> costs unduly.
>
> I looked into this and I think the only task that could be changed is
> the SanityCheck.

I think SanityCheck should run a simple, "average" environment, like the
current Debian one. Otherwise, niche problems with musl or multi-arch
or whatever will throw off the entire build pipeline.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Wolfgang Walther 2024-04-04 14:11:56 Re: Building with musl in CI and the build farm
Previous Message David Rowley 2024-04-04 10:35:42 Re: BUG #18420: Unexpected values appeared in select query statements that should logically imply each other

Browse pgsql-hackers by date

  From Date Subject
Next Message Wolfgang Walther 2024-04-04 14:11:56 Re: Building with musl in CI and the build farm
Previous Message jian he 2024-04-04 13:54:53 Re: add function argument names to regex* functions.