chore: rev the nvidia driver version for the newer driver #634
Conversation
💖 Thanks for opening your first pull request! 💖 We use semantic commit messages to streamline the release process. Before your pull request can be merged, you should make sure your first commit and PR title start with a semantic prefix. Examples of commit messages with semantic prefixes: - |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: brendandburns The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Codecov Report
@@ Coverage Diff @@
## master #634 +/- ##
=======================================
Coverage 63.82% 63.82%
=======================================
Files 91 91
Lines 13947 13947
=======================================
Hits 8901 8901
Misses 4375 4375
Partials 671 671 |
@overplumbum @mathieu-benoit @brendandburns is this pre-existing E2E test scenario to validate cuda workloads that depend on this driver update?: https://github.com/Azure/aks-engine/blob/master/test/e2e/kubernetes/workloads/cuda-vector-add.yaml Basically we validate that the above workload is schedulable (requires an GPU-enabled/configured node) and finishes successfully to completion. |
/azp run AKS Engine VHD Pipeline |
No pipelines are associated with this pull request. |
lgtm Let's manually merge this when we're ready and update the squash commit message (single commit doesn't have /hold |
Congrats on merging your first pull request! 🎉🎉🎉 |
thanks @brendandburns! |
Fixes #471
Driver info:
https://www.nvidia.co.uk/download/driverResults.aspx/140844/en-us
https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-410-79/index.html