Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[ROCm] HIP stream priority fix post pytorch#101956 (pytorch#106157)
PR pytorch#101956 introduced additional stream priorities for cuda streams. HIP streams have slightly different semantics. - HIP: 1=low, 0=default, -1=high - CUDA: 0=default, -1=high, -2=higher, etc. This PR forces HIP stream priority to just 0 and -1 to match the pytorch semantics. This fixes a broken unit test. ``` python3 test_cuda_multigpu.py TestCudaMultiGPU.test_streams_priority -v Test results will be stored in test-reports/python-unittest/test_cuda_multigpu Running tests... ---------------------------------------------------------------------- test_streams_priority (__main__.TestCudaMultiGPU) ... ERROR (0.200s) ====================================================================== ERROR [0.200s]: test_streams_priority (__main__.TestCudaMultiGPU) ---------------------------------------------------------------------- Traceback (most recent call last): File "/opt/conda/envs/py_3.8/lib/python3.8/site-packages/torch/testing/_internal/common_utils.py", line 2354, in wrapper method(*args, **kwargs) File "test_cuda_multigpu.py", line 656, in test_streams_priority low, high = torch.cuda.Stream.priority_range() RuntimeError: least_priority == 0 INTERNAL ASSERT FAILED at "/var/lib/jenkins/pytorch-upstream/c10/hip/HIPStream.h":184, please report a bug to PyTorch. Unexpected HIP stream priority range ``` Pull Request resolved: pytorch#106157 Approved by: https://github.com/malfet
- Loading branch information