Nvml v13.2#135
Closed
blthayer wants to merge 9 commits into
Closed
Conversation
…e freshly generated bindings
…eam release and is provided by Utilidata.
This was referenced Mar 27, 2026
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
FYI/PSA: I meant to open this draft PR in my fork repository, and accidentally opened it here... sorry I've been creating so much noise in this repo the last few business days... Anyways, I will leave this PR open in case it's useful to anyone else. Maintainers: please feel free to close or leave open at your discretion.
Overview
nvml.hwith latest v13 header file (details below).field_values_fortest to exercise allNVML_FI_DEVfields that aren't NVLINK.0.9.0, documented here and implemented in this commit.More Details
To obtain the v13 header file:
Test Results
Not all tests pass on my machine on the
mainbranch. So the goal here was to ensure that all test failures are the same betweenmainand this branch. In other words, ensure this branch/updates didn't cause new test failures.Tests executed from the top-level with
cargo test --workspace --no-fail-fast | tee <file name>. I have manually compared which tests failed to ensure that not only are the number of failures correct, but also that the same tests failed.main branch
tests_main.txt
nvml-v13.2 branch at 3647f80
This is before doing some version-bumping in the sub-project
Cargo.tomlfiles, but after an initial update of the top-levelCargo.lockfile.tests_3647f80.txt
nvml-v13.2 branch at 298161f
tests_298161f.txt