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

Поиск
Список
Период
Сортировка
От Robins Tharakan
Тема Re: Build failure with GCC 15 (defaults to -std=gnu23)
Дата
Msg-id CAEP4nAxMtdyj7xtrf_fPNj8qU0bprOR=fDiCc154_UhQyUZ5cA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Build failure with GCC 15 (defaults to -std=gnu23)  (Robins Tharakan <tharakan@gmail.com>)
Ответы Re: Build failure with GCC 15 (defaults to -std=gnu23)
Re: Build failure with GCC 15 (defaults to -std=gnu23)
Список pgsql-bugs
Дерево обсуждения

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
$


Anyway, I have triggered another v17 run. If the above was purely coincidental, then
that run should fail too.

Ref:
-
robins

В списке pgsql-bugs по дате отправления: