CIAO: before_merging/scheduled, pt 7: test (kernels)

Stack

• !12695 (merged): test (scripts)
• !12696 (merged): test (tezt)
• !12697 (merged): test (kernels) <-- you are here
• !12698 (merged): docs
• !12699 (merged): coverage
• !12700 (merged): packaging (debian repository)
• !12701 (merged): concluding cleanup

What

Part of the CIAO translation of the test stage for the before_merging/scheduled pipelines.

This MR translates the job related to testing kernels: test_evm_compatibility, test_risc_v_kernels, test_etherlink_kernel, test_kernels.

Why

How

This translation is really straightforward and similar to previous MRs. That is, no surprises.

Manually testing the MR

This MR is best reviewed commit-per-commit for the OCaml part. Commits should have a message explaining any non-obvious changes.

For the generated YML, do review the result of these commands (see previous MRs like !11501 (merged) for setup instructions for gci-tezos):

$ gci-tezos diff-full-config master . master_branch,test_release_tag,release_tag,non_release_tag,non_release_tag_test,beta_release_tag
$ gci-tezos diff-full-config master . schedule_extended_tests
$ gci-tezos diff-full-config master . before_merging

Note, depending on the state on local checkout, you might get results of the above commands by replacing master with git merge-base origin/master HEAD, where origin might change depending on the name of your tezos git remote. this also requires that you've run a fetch on origin such that it does not lag behind the branch in this MR.

The first command shows no diff, meaning that those environments are unaffected.

The second two commands will show a diff. There might be some changes that might not be obvious -- it is perhaps easiest to review the diff commit per commit:

$ gci-tezos log-full-config master..HEAD all-envs

This allows you to read, commit-per-commit, the message of the commit and the fully merged diff per environment.

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