github action: split the run of the fuzzers

[tommady]

fix #5443
according to

• https://docs.github.com/en/actions/using-jobs/using-a-matrix-for-your-jobs
• https://docs.github.com/en/actions/examples/using-concurrency-expressions-and-a-test-matrix

[sylvestre]

Sorry, i didn't merge it
it is great. I am just a bit sad that we have to recompile it every time (3 minutes instead 1)
would it be possible to have the task running one after the other in the same VM ?

[tommady]

Sorry, i didn't merge it it is great. I am just a bit sad that we have to recompile it every time (3 minutes instead 1) would it be possible to have the task running one after the other in the same VM ?

yes it can be, but if we do that it will miss the goal:

run them into dedicated tasks (one per fuzzer)

which I understand is running all the fuzz tests in parallel.
right?

[tommady]

or let me think of a way to reduce the compile time.

[tommady]

oh I am sorry, the fuzz test already using the

- uses: Swatinem/rust-cache@v2

so I think there is nothing I can do right now 😞

[tommady]

Hi @sylvestre
how about this

sorry for the misunderstanding
I thought the Swatinem/rust-cache@v2 action could cache everything,
but after reading the doc and the cargo-fuzz doc,
I found out I was so wrong.

please review this PR again while you have time.
thanks

[sylvestre]

This is perfect, many thanks