Re: Build failure with GCC 15 (defaults to -std=gnu23)

Robins Tharakan <tharakan@gmail.com>

From: Robins Tharakan <tharakan@gmail.com>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Andres Freund <andres@anarazel.de>, Thomas Munro <thomas.munro@gmail.com>, Peter Eisentraut <peter@eisentraut.org>, Sam James <sam@gentoo.org>, pgsql-bugs@lists.postgresql.org
Date: 2024-12-14T10:46:57Z
Lists: pgsql-bugs
On Sat, 14 Dec 2024 at 00:18, Andrew Dunstan <andrew@dunslane.net> wrote:

> We actually have a good deal of protection against concurrent runs
> clobbering each other.
>
> It's not clear to me if you're using "run_branches.pl --run-parallel" or
> not. If not, you might like to consider changing to that - it's the
> recommended way of doing concurrent runs. Apart from any other reason it
> removes the need for a lot of redundant git fetches. By default it staggers
> concurrent build starts by 60 seconds.
>
>
In this case I didn't use run_branches.pl. I just opened up two sessions
and triggered two
separate runs for v16 / v17 (with --force) since master just came out
green. Efficiency aside,
at worst I was expecting two concurrent runs to be slower, but not error
out.

Unrelated, for a slow system my understanding was that it's quite
inefficient to keep running older
branches every few minutes (like HEAD does) - so for some of the animals I
explicitly run older
branches (for e.g. v13) every few hours, but HEAD runs every few minutes.

Are you saying it's still a good idea to run all together every few minutes
(and let older branches
skip if there's nothing to do)?

-
robins

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Require sizeof(bool) == 1.

  2. If a C23 compiler is detected, try asking for C17.

  3. Fix C23 compiler warning

  4. Rename C23 keyword

  5. Assume that <stdbool.h> conforms to the C standard.

  6. Revise tree-walk APIs to improve spec compliance & silence warnings.