Re: [PATCH] ci: avoid building from the same commit in parallel

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 22, 2023, 04:36 UTC
Message-ID: <xmqqpm3fn16f.fsf@gitster.g>
In-Reply-To: <xmqq1qfvor35.fsf_-_@gitster.g>

Junio C Hamano <gitster@pobox.com> writes:

>  * There are tons of concurrency groups defined, but as a trial
>    change, here is to cover the "regular" matrix that consumes the
>    most resources (linux-asan-ubsan is the worst culprit, it seems).

Unfortunately, this did not work.

https://github.com/git/git/actions/runs/5933451874 https://github.com/git/git/actions/runs/5933451805

are trial runs that had the same commit with this patch pushed to 'seen' and 'pu'. While one of them started the "regular" matrix, the other one indeed went into paused state and waited. But that is way too late. What happened was that their "config" (which everything else depends on) started in parallel before the serialization at the "regular" matrix kicked in.

So, one did wait before doing the "regular" matrix, until the other one finished everything, and then kept going and did its own "regular" matrix for the same commit. It is because the avoidance of "redundant build" was done at the "config" phase, which both of them had already done X-<.

If we wanted to do this, I suspect that we need to serialize the entire thing, not at the individual level where we currently define the "concurrency" thing.