DAOS-15384 test: Re-enable test_wal_checkpoint_metrics

[saurabhtandan]

Re-enable test_wal_checkpoint_metrics

Test-tag: test_wal_checkpoint_metrics Test-nvme: auto_md_on_ssd

Before requesting gatekeeper:

• [ ] Two review approvals and any prior change requests have been resolved.
• [ ] Testing is complete and all tests passed or there is a reason documented in the PR why it should be force landed and forced-landing tag is set.
• [ ] Features: (or Test-tag*) commit pragma was used or there is a reason documented that there are no appropriate tags for this PR.
• [ ] Commit messages follows the guidelines outlined here.
• [ ] Any tests skipped by the ticket being addressed have been run and passed in the PR.

Gatekeeper:

• [ ] You are the appropriate gatekeeper to be landing the patch.
• [ ] The PR has 2 reviews by people familiar with the code, including appropriate owners.
• [ ] Githooks were used. If not, request that user install them and check copyright dates.
• [ ] Checkpatch issues are resolved. Pay particular attention to ones that will show up on future PRs.
• [ ] All builds have passed. Check non-required builds for any new compiler warnings.
• [ ] Sufficient testing is done. Check feature pragmas and test tags and that tests skipped for the ticket are run and now pass with the changes.
• [ ] If applicable, the PR has addressed any potential version compatibility issues.
• [ ] Check the target branch. If it is master branch, should the PR go to a feature branch? If it is a release branch, does it have merge approval in the JIRA ticket.
• [ ] Extra checks if forced landing is requested
  • [ ] Review comments are sufficiently resolved, particularly by prior reviewers that requested changes.
  • [ ] No new NLT or valgrind warnings. Check the classic view.
  • [ ] Quick-build or Quick-functional is not used.
• [ ] Fix the commit message upon landing. Check the standard here. Edit it to create a single commit. If necessary, ask submitter for a new summary.

[github-actions[bot]]

Ticket title is 'engine_pool_checkpoint_* metrics non-zero for pool with check pointing disabled' Status is 'Open' Labels: 'md_on_ssd,scrubbed' https://daosio.atlassian.net/browse/DAOS-15384

[saurabhtandan]

Please check build #1 for test results.

[daltonbohning]

I don't think this ran with md on ssd: https://build.hpdd.intel.com/job/daos-stack/job/daos/job/PR-14313/1/artifact/Functional%20Hardware%20Medium/telemetry/wal_metrics.py/daos_configs.wolf-142/daos_server.yml/view/

  storage:
  - class: dcpm
    scm_list:
    - /dev/pmem0
    scm_mount: /mnt/daos0
  - bdev_list:
    - '0000:13:00.0'
    - 0000:b0:00.0
    class: nvme

It's simpler to use

Skip-func-hw-test-medium-md-on-ssd: false

[saurabhtandan]

I don't think this ran with md on ssd: https://build.hpdd.intel.com/job/daos-stack/job/daos/job/PR-14313/1/artifact/Functional%20Hardware%20Medium/telemetry/wal_metrics.py/daos_configs.wolf-142/daos_server.yml/view/

  storage:
  - class: dcpm
    scm_list:
    - /dev/pmem0
    scm_mount: /mnt/daos0
  - bdev_list:
    - '0000:13:00.0'
    - 0000:b0:00.0
    class: nvme

It's simpler to use

Skip-func-hw-test-medium-md-on-ssd: false

Along with Test-nvme: auto_md_on_ssd or alone? I mean,

Test-nvme: auto_md_on_ssd
Skip-func-hw-test-medium-md-on-ssd: false
Test-repeat: 5```

OR

```Test-tag: test_wal_checkpoint_metrics
Skip-func-hw-test-medium-md-on-ssd: false
Test-repeat: 5```

[daltonbohning]

To run the pmem stage and md on ssd stage

Test-tag: test_wal_checkpoint_metrics
Skip-func-hw-test-medium-md-on-ssd: false

To run just the md on ssd stage

Test-tag: test_wal_checkpoint_metrics
Skip-func-hw-test-medium-md-on-ssd: false
Skip-func-hw-test-medium: true