cmake: Introduce ctest labels for testing

[wjwithagen]

cmake: Introduce ctest TEST labels for testing and COST

Tests in CMake/Ctest can have labels on which can be filtered

  ctest  --print-labels
  Test project /home/wjw/work/ceph/build
  All Labels:
    freebsd
    long
    tox
    unittest
    vstart

Which allows to run certain subsets of by using RE filters
in ctest.

COST will determine the order in which the tests are executed.
Current settings will start with long running tests.
Like:

        Start 118: unittest_erasure_code_shec_all
        Start  31: unittest_bufferlist
        Start 106: readable.sh
        Start  13: run-cli-tests
        Start 105: check-generated.sh
        Start 140: safe-to-destroy.sh
        Start 130: ceph_test_object_map
        Start  15: smoke.sh
        Start  12: rbd-ggate.sh
        Start 169: unittest_rbd_mirror
        Start 154: test_ceph_argparse.py
        Start 134: unittest_fastbmap_allocator
        Start 141: unittest_osdmap
        Start   1: run-tox-mgr-dashboard
        Start   2: run-tox-mgr-insights
        Start   3: run-tox-mgr-ansible

Checklist

• References tracker ticket
• Updates documentation if necessary
• Includes tests for new functionality or reproducer for bug

---

Show available Jenkins commands

• jenkins retest this please
• jenkins test make check
• jenkins test make check arm64
• jenkins test submodules
• jenkins test dashboard
• jenkins test dashboard backend
• jenkins test docs
• jenkins render docs

[epuertat]

Looks ok. Just a few suggestions/questions left over there.

[tchaikov]

i'd recommend s/build:/cmake:/ in the title of your commit message. we could be more specific here.

[epuertat]

Looks like this is improving even further! Thanks @wjwithagen! Just a few suggestions: mostly related to the hardcoded values and perhaps explaining this in Ceph Developer's docs.

[epuertat]

BTW, with the help of @alfredodeza we've created a Jenkins Build Analyzer parser for CTest Failures, so the output in case of failure (like the above "make check fail") would look like the following:

CTest Failure

Label Time Summary:
long        = 3576.34 sec*proc (14 tests)
tox         = 183.55 sec*proc (6 tests)
unittest    = 5227.38 sec*proc (161 tests)

Total Test time (real) = 4063.85 sec

The following tests FAILED:
	174 - unittest_seastar_buffer (Failed)
	176 - unittest_seastar_socket (Failed)
	177 - unittest_seastar_messenger (Failed)
	178 - unittest_seastar_thread_pool (Timeout)
	179 - unittest_seastar_perfcounters (Failed)```

[wjwithagen]

You can supress the total label runtime if wanted with ctest --no-label-summary
And perhaps @tchaikov could/would mark his seastar test with a label as well.

[epuertat]

Looks great. Just added a minor suggestion to improve the docs already provided. Thanks a lot for this @wjwithagen !

[stale]

This pull request has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs for another 30 days.
If you are a maintainer or core committer, please follow-up on this pull request to identify what steps should be taken by the author to move this proposed change forward.
If you are the author of this pull request, thank you for your proposed contribution. If you believe this change is still appropriate, please ensure that any feedback has been addressed and ask for a code review.

[epuertat]

Keep away from this, bad stale bot!

I think this is valuable in order to speed-up/fine-tune CI.

[github-actions]

This pull request has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs for another 30 days.
If you are a maintainer or core committer, please follow-up on this pull request to identify what steps should be taken by the author to move this proposed change forward.
If you are the author of this pull request, thank you for your proposed contribution. If you believe this change is still appropriate, please ensure that any feedback has been addressed and ask for a code review.

[github-actions]

This pull request has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs for another 30 days.
If you are a maintainer or core committer, please follow-up on this pull request to identify what steps should be taken by the author to move this proposed change forward.
If you are the author of this pull request, thank you for your proposed contribution. If you believe this change is still appropriate, please ensure that any feedback has been addressed and ask for a code review.

[github-actions]

This pull request has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs for another 30 days.
If you are a maintainer or core committer, please follow-up on this pull request to identify what steps should be taken by the author to move this proposed change forward.
If you are the author of this pull request, thank you for your proposed contribution. If you believe this change is still appropriate, please ensure that any feedback has been addressed and ask for a code review.

[github-actions]

This pull request has been automatically closed because there has been no activity for 90 days. Please feel free to reopen this pull request (or open a new one) if the proposed change is still appropriate. Thank you for your contribution!

[jmundack]

@wjwithagen - i am unsure if you are still working on ceph BUT was hoping/wondering if we can/should revive this PR.

We are trying to improve the general builds, tests - developer experience around this and I think would really help with that endeavor

[epuertat]

Recovering this PR in the context of CI improvements, as this would enable both:

• Improved scheduling of tests,
• Conditional running of tests based on git changed files. This requires further work to create mappings between modified source code directories and ctest labels (e.g.: in .gitattributes).

[idryomov]

• Conditional running of tests based on git changed files. This requires further work to create mappings between modified source code directories and ctest labels (e.g.: in .gitattributes).

@cbodley is trying out an approach to do this based on parsing CODEOWNERS file inside of ceph-build: ceph/ceph-build#2361

[github-actions]

This pull request has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs for another 30 days.
If you are a maintainer or core committer, please follow-up on this pull request to identify what steps should be taken by the author to move this proposed change forward.
If you are the author of this pull request, thank you for your proposed contribution. If you believe this change is still appropriate, please ensure that any feedback has been addressed and ask for a code review.

[github-actions]

This pull request has been automatically closed because there has been no activity for 90 days. Please feel free to reopen this pull request (or open a new one) if the proposed change is still appropriate. Thank you for your contribution!