Re: Building with musl in CI and the build farm

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Wolfgang Walther <walther(at)technowledgy(dot)de>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Building with musl in CI and the build farm
Date: 2024-04-04 15:19:11
Message-ID: 562618.1712243951@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Wolfgang Walther <walther(at)technowledgy(dot)de> writes:
>> That is not the concern here. What I think Peter is worried about,
>> and certainly what I'm worried about, is that a breakage in
>> SanityCheck comprehensively breaks all CI testing for all Postgres
>> developers.

> You'd have to commit a failing patch first to break CI for all other
> developers.

No, what I'm more worried about is some change in the environment
causing the build to start failing. When that happens, it'd better
be an environment that many of us are familiar with and can test/fix.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Wolfgang Walther 2024-04-04 19:09:30 Re: Building with musl in CI and the build farm
Previous Message Wolfgang Walther 2024-04-04 15:01:32 Re: Building with musl in CI and the build farm

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2024-04-04 15:19:53 Re: Psql meta-command conninfo+
Previous Message Tom Lane 2024-04-04 15:16:28 Re: WIP Incremental JSON Parser