Fix generate tests when cdi hook exists in path #1408
Merged
+3
−0
Conversation
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
The TestGenerateSpec unit tests resolve the path to the nvidia-cdi-hook binary if it exists on the system making the results dependent on system configuration. This change sets the path to the binary explicitly to skip the resolution in the path. Signed-off-by: Evan Lezar <[email protected]>
Member
Author
|
/cherry-pick release-1.18 |
ArangoGutierrez
approved these changes
Nov 4, 2025
|
🤖 Backport PR created for |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The TestGenerateSpec unit tests resolve the path to the nvidia-cdi-hook binary if it exists on the system making the results dependent on system configuration.
This change sets the path to the binary explicitly to skip the resolution in the path.
Fixes #1388