Check failing UVM test

[ananthsub]

Summary: see if this fixes the error

tests/test_uvm_tensor.py::test_uvm_tensor - RuntimeError: CUDA error: invalid device ordinal

https://github.com/pytorch/torchsnapshot/actions/runs/5422322107/jobs/9858818161

Differential Revision: D47158196

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D47158196

[codecov[bot]]

Codecov Report

Merging #145 (ecc7768) into main (aa9ebfd) will decrease coverage by 4.88%. The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #145      +/-   ##
==========================================
- Coverage   90.58%   85.71%   -4.88%     
==========================================
  Files          59       59              
  Lines        4442     4444       +2     
==========================================
- Hits         4024     3809     -215     
- Misses        418      635     +217     

Impacted Files	Coverage Δ
tests/test_uvm_tensor.py	57.14% <0.00%> (-9.53%)	:arrow_down:

... and 6 files with indirect coverage changes

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

[facebook-github-bot]

Hi @ananthsub!

Thank you for your pull request.

We require contributors to sign our Contributor License Agreement, and yours needs attention.

You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!