CI: Execute RISC-V Rust tests in a dedicated job

Stack:

• !11821 (merged) (Execute Etherlink kernel tests in their own CI job)
• !12178 (merged) (preliminary work for this MR)
• You are here

What

The test_kernels job has become unbearably slow, mostly because it executes sequentially tests that are now mostly unrelated. To speed-up things, we propose to split the test_kernels job into several ones, which can run in parallel. The cumulative time does not appear to be significantly higher, and it removes test_kernels from the critical path of the CI time.

Why

I want a fast CI.

How

By editing some yaml files.

Manually testing the MR

We need to check I haven’t forgotten something in the process.

Checklist

• Document the interface of any function added or modified (see the coding guidelines)
• Document any change to the user interface, including configuration parameters (see node configuration)
• Provide automatic testing (see the testing guide).
• For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
• Select suitable reviewers using the Reviewers field below.
• Select as Assignee the next person who should take action on that MR