CIAO: before_merging/scheduled, pt 4: test (1)

Stack

• !12377 (merged): Generation check
• !12378 (merged): before_merging/scheduled -- scaffolding
• !12382 (merged): before_merging/scheduled -- sanity, packaging
• !12397 (merged): before_merging/scheduled -- build
• !12490 (merged): before_merging/scheduled -- test (1) <- You are here

What

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

Why

How

No surprises here. Jobs are split per pipeline like in previous MRs. There are some changes to the commit_titles to make it easier to generate the two pipeline-specific versions.

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 this command (see previous MRs like !11501 (merged) for setup instructions for gci-tezos):

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

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 will show that this MR only strips irrelevant rules and trigger dependencies from the scheduled pipeline.

The second command shows a diff to the job oc.misc_checks which is just a re-ordering of the script to ease generation. There is also a diff to the job commit_titles with no semantic consequence.

The third command shows no diff.

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