DISABLED test_int64_upsample3d_cuda_bfloat16 (main.TestTorchDeviceTypeCUDA) #146007

pytorch-bot · 2025-01-30T03:41:54Z

Platforms: rocm

This test was disabled because it is failing in CI. See recent examples and the most recent trunk workflow logs.

Over the past 3 hours, it has been determined flaky in 7 workflow(s) with 14 failures and 7 successes.

Debugging instructions (after clicking on the recent samples link):
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:

Click on the workflow logs linked above
Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
Grep for test_int64_upsample3d_cuda_bfloat16
There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.

Sample error message

Traceback (most recent call last):
  File "/var/lib/jenkins/pytorch/test/test_torch.py", line 185, in test_int64_upsample3d
    torch.nn.functional.interpolate(x, scale_factor=2, mode='nearest')
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/nn/functional.py", line 4651, in interpolate
    return torch._C._nn.upsample_nearest3d(input, output_size, scale_factors)
torch.OutOfMemoryError: HIP out of memory. Tried to allocate 56.25 GiB. GPU 0 has a total capacity of 63.98 GiB of which 55.80 GiB is free. Of the allocated memory 7.06 GiB is allocated by PyTorch, and 0 bytes is reserved by PyTorch but unallocated. If reserved but unallocated memory is large try setting PYTORCH_HIP_ALLOC_CONF=expandable_segments:True to avoid fragmentation.  See documentation for Memory Management  (https://pytorch.org/docs/stable/notes/cuda.html#environment-variables)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/var/lib/jenkins/pytorch/test/test_torch.py", line 187, in test_int64_upsample3d
    self.fail(f"Unexpected exception raised: {e}")
  File "/opt/conda/envs/py_3.10/lib/python3.10/unittest/case.py", line 675, in fail
    raise self.failureException(msg)
AssertionError: Unexpected exception raised: HIP out of memory. Tried to allocate 56.25 GiB. GPU 0 has a total capacity of 63.98 GiB of which 55.80 GiB is free. Of the allocated memory 7.06 GiB is allocated by PyTorch, and 0 bytes is reserved by PyTorch but unallocated. If reserved but unallocated memory is large try setting PYTORCH_HIP_ALLOC_CONF=expandable_segments:True to avoid fragmentation.  See documentation for Memory Management  (https://pytorch.org/docs/stable/notes/cuda.html#environment-variables)

To execute this test, run the following from the base repo dir:
    PYTORCH_TEST_WITH_ROCM=1 python test/test_torch.py TestTorchDeviceTypeCUDA.test_int64_upsample3d_cuda_bfloat16

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0

Test file path: test_torch.py

cc @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @naromero77amd @mruberry @ZainRizvi @clee2000 @wdvr

The text was updated successfully, but these errors were encountered:

pytorch-bot · 2025-01-30T03:42:00Z

Hello there! From the DISABLED prefix in this issue title, it looks like you are attempting to disable a test in PyTorch CI. The information I have parsed is below:

Test name: test_int64_upsample3d_cuda_bfloat16 (__main__.TestTorchDeviceTypeCUDA)
Platforms for which to skip the test: rocm
Disabled by pytorch-bot[bot]

Within ~15 minutes, test_int64_upsample3d_cuda_bfloat16 (__main__.TestTorchDeviceTypeCUDA) will be disabled in PyTorch CI for these platforms: rocm. Please verify that your test name looks correct, e.g., test_cuda_assert_async (__main__.TestCuda).

To modify the platforms list, please include a line in the issue body, like below. The default action will disable the test for all platforms if no platforms list is specified.

Platforms: case-insensitive, list, of, platforms

We currently support the following platforms: asan, dynamo, inductor, linux, mac, macos, rocm, slow, win, windows.

How to re-enable a test

To re-enable the test globally, close the issue. To re-enable a test for only a subset of plat 8000 forms, remove the platforms from the list in the issue body. This may take some time to propagate. To re-enable a test only for a PR, put Fixes #146007 in the PR body and rerun the test jobs. Note that if a test is flaky, it maybe be difficult to tell if the test is still flaky on the PR.

pytorch-bot · 2025-01-30T03:42:00Z

Hello there! From the DISABLED prefix in this issue title, it looks like you are attempting to disable a test in PyTorch CI. The information I have parsed is below:

Test name: test_int64_upsample3d_cuda_bfloat16 (__main__.TestTorchDeviceTypeCUDA)
Platforms for which to skip the test: rocm
Disabled by pytorch-bot[bot]

Within ~15 minutes, test_int64_upsample3d_cuda_bfloat16 (__main__.TestTorchDeviceTypeCUDA) will be disabled in PyTorch CI for these platforms: rocm. Please verify that your test name looks correct, e.g., test_cuda_assert_async (__main__.TestCuda).

To modify the platforms list, please include a line in the issue body, like below. The default action will disable the test for all platforms if no platforms list is specified.

Platforms: case-insensitive, list, of, platforms

We currently support the following platforms: asan, dynamo, inductor, linux, mac, macos, rocm, slow, win, windows.

How to re-enable a test

To re-enable the test globally, close the issue. To re-enable a test for only a subset of platforms, remove the platforms from the list in the issue body. This may take some time to propagate. To re-enable a test only for a PR, put Fixes #146007 in the PR body and rerun the test jobs. Note that if a test is flaky, it maybe be difficult to tell if the test is still flaky on the PR.

pytorch-bot · 2025-01-30T03:42:00Z

Hello there! From the DISABLED prefix in this issue title, it looks like you are attempting to disable a test in PyTorch CI. The information I have parsed is below:

Test name: test_int64_upsample3d_cuda_bfloat16 (__main__.TestTorchDeviceTypeCUDA)
Platforms for which to skip the test: rocm
Disabled by pytorch-bot[bot]

Within ~15 minutes, test_int64_upsample3d_cuda_bfloat16 (__main__.TestTorchDeviceTypeCUDA) will be disabled in PyTorch CI for these platforms: rocm. Please verify that your test name looks correct, e.g., test_cuda_assert_async (__main__.TestCuda).

To modify the platforms list, please include a line in the issue body, like below. The default action will disable the test for all platforms if no platforms list is specified.

Platforms: case-insensitive, list, of, platforms

We currently support the following platforms: asan, dynamo, inductor, linux, mac, macos, rocm, slow, win, windows.

How to re-enable a test

To re-enable the test globally, close the issue. To re-enable a test for only a subset of platforms, remove the platforms from the list in the issue body. This may take some time to propagate. To re-enable a test only for a PR, put Fixes #146007 in the PR body and rerun the test jobs. Note that if a test is flaky, it maybe be difficult to tell if the test is still flaky on the PR.

pytorch-bot · 2025-01-30T03:42:00Z

Hello there! From the DISABLED prefix in this issue title, it looks like you are attempting to disable a test in PyTorch CI. The information I have parsed is below:

Test name: test_int64_upsample3d_cuda_bfloat16 (__main__.TestTorchDeviceTypeCUDA)
Platforms for which to skip the test: rocm
Disabled by pytorch-bot[bot]

Within ~15 minutes, test_int64_upsample3d_cuda_bfloat16 (__main__.TestTorchDeviceTypeCUDA) will be disabled in PyTorch CI for these platforms: rocm. Please verify that your test name looks correct, e.g., test_cuda_assert_async (__main__.TestCuda).

To modify the platforms list, please include a line in the issue body, like below. The default action will disable the test for all platforms if no platforms list is specified.

Platforms: case-insensitive, list, of, platforms

We currently support the following platforms: asan, dynamo, inductor, linux, mac, macos, rocm, slow, win, windows.

How to re-enable a test

To re-enable the test globally, close the issue. To re-enable a test for only a subset of platforms, remove the platforms from the list in the issue body. This may take some time to propagate. To re-enable a test only for a PR, put Fixes #146007 in the PR body and rerun the test jobs. Note that if a test is flaky, it maybe be difficult to tell if the test is still flaky on the PR.

pytorch-bot · 2025-01-30T03:42:27Z

Hello there! From the DISABLED prefix in this issue title, it looks like you are attempting to disable a test in PyTorch CI. The information I have parsed is below:

Test name: test_int64_upsample3d_cuda_bfloat16 (__main__.TestTorchDeviceTypeCUDA)
Platforms for which to skip the test: rocm
Disabled by pytorch-bot[bot]

Within ~15 minutes, test_int64_upsample3d_cuda_bfloat16 (__main__.TestTorchDeviceTypeCUDA) will be disabled in PyTorch CI for these platforms: rocm. Please verify that your test name looks correct, e.g., test_cuda_assert_async (__main__.TestCuda).

To modify the platforms list, please include a line in the issue body, like below. The default action will disable the test for all platforms if no platforms list is specified.

Platforms: case-insensitive, list, of, platforms

We currently support the following platforms: asan, dynamo, inductor, linux, mac, macos, rocm, slow, win, windows.

How to re-enable a test

To re-enable the test globally, close the issue. To re-enable a test for only a subset of platforms, remove the platforms from the list in the issue body. This may take some time to propagate. To re-enable a test only for a PR, put Fixes #146007 in the PR body and rerun the test jobs. Note that if a test is flaky, it maybe be difficult to tell if the test is still flaky on the PR.

pytorch-bot · 2025-01-30T06:43:23Z

Another case of trunk flakiness has been found here. The list of platforms [rocm] appears to contain all the recently affected platforms [rocm]. Either the change didn't propogate fast enough or disable bot might be broken.

pytorch-bot · 2025-02-13T06:46:09Z

Resolving the issue because the test is not flaky anymore after 450 reruns without any failures and the issue hasn't been updated in 14 days. Please reopen the issue to re-disable the test if you think this is a false positive

pytorch-bot · 2025-02-13T12:51:01Z