Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

dcgm 4.4.2 test name changed?

Open
  • Is something wrong?
#296 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
cpp
Domain
cli, testing-qa

Research direction

Start with the dcgmi diag entry point and compare the available test options in DCGM 3.3.8 and 4.4.2, including software, memory_bandwidth, and pulse_test. Done means confirming whether these names changed and documenting the correct 4.4.2 options or the reason the tests are unavailable.

Written by the indexing model from the issue text.

Description

I used the following command to run software、memory bandwidth and pulse test
dcgmi diag -j -v -c /opt/dcgm_config.yaml -i 0 -r software
dcgmi diag -j -v -c /opt/dcgm_config.yaml -i 0 -r memory_bandwidth
dcgmi diag -j -v -c /opt/dcgm_config.yaml -i 0 -r pulse_test
This works fine on dcgm 3.3.8.
When I upgrade dcgm to 4.4.2, I tried to install the core、proprietary and cuda package and run the tests above. When I rerun the commands above, it says the requested tests were not found. Does the test name change in the new dcgm? If so, what's the new test options?

Dominant language
C++
Stars
798
Forks
112
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NVIDIA/DCGM

All issues in NVIDIA/DCGM

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.