Hi Junio,
On Mon, 21 Aug 2023, Junio C Hamano wrote:
> 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.
Right, we'd need that `concurrency: ${{ github.sha }}` attribute on the
`config` job.
BTW there is another caveat. According to the documentation, if a job is
queued while another job is already queued, that other job is canceled in
favor of the latest one.
I have not verified this by testing it out, but have no reason to doubt
it.
If that's the case, pushing, say, `master`, `main` and `next` to the same
SHA will see one of them canceled. Which might be okay, if the cancelation
message on the canceled one is indicative enough.
This all depends on reducing the number of flakes (in particular the p4
tests in the ASAN job), but that's a story for another day.
Ciao,
Johannes
