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 →
-
Require sizeof(bool) == 1.
- 97525bc5c8ff 18.0 landed
-
If a C23 compiler is detected, try asking for C17.
- f4e8f137bfb0 10 (unreleased) landed
- 0c7171b32e64 9.2 (unreleased) landed
- 102be6634e6f 9.3 (unreleased) landed
- b1b8b8e6f141 9.4 (unreleased) landed
- 5b40ce749c6f 9.5 (unreleased) landed
- 70cf253d18da 9.6 (unreleased) landed
- 170e416034ec 11 (unreleased) landed
- 3f302f0ed06f 12 (unreleased) landed
- 59ea17c43c6c 13.19 landed
- 1fd57e5bbf87 14.16 landed
- f00c401c65af 15.11 landed
-
Fix C23 compiler warning
- f7a929a007e6 16.7 landed
- f3834c12afd8 17.3 landed
-
Rename C23 keyword
- ae145d1de677 16.7 landed
- ad89c8bda1f0 17.3 landed
-
Assume that <stdbool.h> conforms to the C standard.
- bc5a4dfcf739 18.0 landed
- 0813a5e69186 17.3 landed
- 0f6d902308a8 16.7 landed
- 94817d9d94d0 15.11 landed
- e0874080c472 14.16 landed
- 13242b64e15d 13.19 landed
- 15a89e2cc501 12 (unreleased) landed
- 0305dd3adef2 11 (unreleased) landed
-
Revise tree-walk APIs to improve spec compliance & silence warnings.
- 1c27d16e6e5c 16.0 cited