pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Andrew Dunstan <andrew@dunslane.net>
To: Robins Tharakan <tharakan@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andres Freund <andres@anarazel.de>
Cc: Thomas Munro <thomas.munro@gmail.com>
Cc: Peter Eisentraut <peter@eisentraut.org>
Cc: Sam James <sam@gentoo.org>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Build failure with GCC 15 (defaults to -std=gnu23)
Date: Fri, 13 Dec 2024 08:48:04 -0500
Message-ID: <8877ae08-5dcd-45bf-8475-c6d5a5200346@dunslane.net> (raw)
In-Reply-To: <CAEP4nAxMtdyj7xtrf_fPNj8qU0bprOR=fDiCc154_UhQyUZ5cA@mail.gmail.com>
References: <485f5982-18c5-4210-9c7d-7c05453f7033@eisentraut.org>
	<CA+hUKGL0LWK7hVO9r2eb3hFDBptZByOkAKGAjXKJ5mqd9hs_fA@mail.gmail.com>
	<1447160.1732565223@sss.pgh.pa.us>
	<CA+hUKG+5ErSyS2+rqx0bvKAWadP9NQBOsUgZVpz74ZB0DA=nJw@mail.gmail.com>
	<1578470.1732587191@sss.pgh.pa.us>
	<CA+hUKGJ4HEntEJkpqinyaLn3AfXMvCirWk0n2H4LWDxSSGh-Dw@mail.gmail.com>
	<CA+hUKG+y2q0dP=g=bbkAWD66unrSKsQEc29ERvA_6fTC3b954Q@mail.gmail.com>
	<1897695.1732732104@sss.pgh.pa.us>
	<eu34f6armrlbq7cdai3dy45576h3qybme47uxens4cowpghzqe@52owmagijfiu>
	<2gao2zapw2dumahxgma4t3c6cquy4vnjs5bt4yvduexpywwm2m@3uhxxc63xvlq>
	<CAEP4nAw4UHSgcHFL7Rsub0nCHW=6ZCrpiuBUT_dV5+4apS=Q5Q@mail.gmail.com>
	<494522.1732894313@sss.pgh.pa.us>
	<CAEP4nAyRfWZ8T8xzNHHy4p8kLCrXAAY7Hbs2_P8YCOJiu=6SCA@mail.gmail.com>
	<970389.1734052913@sss.pgh.pa.us>
	<CAEP4nAyOKW+CLHrFDHw1e6fjEG+urL2x1DSeFiU8vnaGsOrV1g@mail.gmail.com>
	<CAEP4nAzOaY0PR-7_t6aN-Dwq6vZzO3i0JAAx2BBRUzy3LwtNGw@mail.gmail.com>
	<CAEP4nAxMtdyj7xtrf_fPNj8qU0bprOR=fDiCc154_UhQyUZ5cA@mail.gmail.com>


On 2024-12-12 Th 9:31 PM, Robins Tharakan wrote:
>
> On Fri, 13 Dec 2024 at 12:46, Robins Tharakan <tharakan@gmail.com> wrote:
>
>
>     REL_17_STABLE failed on misc-recovery and one context I can add
>     here is
>     that I triggered both REL_16_STABLE and REL_17_STABLE together and
>     were running neck-and-neck wherein v16 went past this test (in ~4
>     minutes)
>     and v17 (got stuck for ~10 min) and failed.
>
>
> Is it possible that 2 concurrent runs (of different branches) could 
> step on each other?
>
> These are the logs that I captured, and v16 [2] / v17 [1] literally 
> ran at the same
> time (seconds apart).
>
>
> v16 log:
> alligator:REL_16_STABLE [12:24:42] running bin test scripts ...
> alligator:REL_16_STABLE [12:25:28] running test misc-recovery ...
> alligator:REL_16_STABLE [12:29:40] running test misc-subscription ...
>
>
> v17 log:
> alligator:REL_17_STABLE [12:25:09] running bin test psql ...
> alligator:REL_17_STABLE [12:25:19] running bin test scripts ...
> alligator:REL_17_STABLE [12:26:00] running test misc-recovery ...
> alligator:REL_17_STABLE [12:37:15] failed at stage recoveryCheck
> $
>

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.


cheers


andrew

--
Andrew Dunstan
EDB:https://www.enterprisedb.com

view thread (42+ messages)  latest in thread

Message-ID: <8877ae08-5dcd-45bf-8475-c6d5a5200346@dunslane.net>
Permalink:  ../8877ae08-5dcd-45bf-8475-c6d5a5200346@dunslane.net/
Also on:    postgresql.org/message-id/8877ae08-5dcd-45bf-8475-c6d5a5200346@dunslane.net

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: andrew@dunslane.net, tharakan@gmail.com, tgl@sss.pgh.pa.us, andres@anarazel.de, thomas.munro@gmail.com, peter@eisentraut.org, sam@gentoo.org, pgsql-bugs@lists.postgresql.org
  Subject: Re: Build failure with GCC 15 (defaults to -std=gnu23)
  In-Reply-To: <8877ae08-5dcd-45bf-8475-c6d5a5200346@dunslane.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox