[dinghwah]

Adding code-coverage report for daos unit test.

Steps for the author:

• Commit message follows the guidelines.
• Appropriate Features or Test-tag pragmas were used.
• Appropriate Functional Test Stages were run.
• At least two positive code reviews including at least one code owner from each category referenced in the PR.
• Testing is complete. If necessary, forced-landing label added and a reason added in a comment.

After all prior steps are complete:

• Gatekeeper requested (daos-gatekeeper added as a reviewer).

[github-actions]

Errors are Unable to load ticket data
https://daosio.atlassian.net/browse/DAOS-17259

[phender]

Test stage Functional Hardware Medium MD on SSD completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-16338/207/execution/node/705/log

This is known issue https://daosio.atlassian.net/browse/DAOS-18218

[phender]

Summary of updated test results:

• Build 206 (w/o CI_CODE_COVERAGE checked) - failed Fault Injection
• Build 207 (w/o CI_CODE_COVERAGE checked) - re-run of 206. Passed Fault-Injection. One functional test failure - known issue DAOS-18218
• Build 208 (w/ CI_CODE_COVERAGE checked) - passed w/ code coverage report.

[phender]

Summary of updated test results:

• Build 206 (w/o CI_CODE_COVERAGE checked) - failed Fault Injection
• Build 207 (w/o CI_CODE_COVERAGE checked) - re-run of 206. Passed Fault-Injection. One functional test failure - known issue DAOS-18218
• Build 208 (w/ CI_CODE_COVERAGE checked) - passed w/ code coverage report.

Build 210 (w/o CI_CODE_COVERAGE) passed

[ryon-jensen]

What's the expected impact to CI of the code coverage stage? If I understand the Jenkins file changes correctly, the stage will only run once a week, and only for unit tests? Is it a new scheduled run, or extra stage for an already existing scheduled run?
Also, the increase in timeouts applies to all builds, not just when code coverage is enabled, correct?

==>Yes, CI with code coverage will be run weekly with Unit Tests only for now. This is a new schedule run. Functional tests on VM and Hardware will be added when gcov on them are become available.
Yes, the increase in timeouts applies to all builds.

[daosbuild3]

Test stage NLT on EL 8.8 completed with status UNSTABLE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/daos//view/change-requests/job/PR-16338/213/testReport/

[daltonbohning]

@phender @dinghwah Do we still need this?