DISABLED test_TransformerDecoderLayer_relu_activation_cuda_fp32 (__main__.TestNN)

[pytorch-bot]

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 9 workflow(s) with 18 failures and 9 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:

1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for test_TransformerDecoderLayer_relu_activation_cuda_fp32
4. 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_nn.py", line 7612, in with_tf32_off
    test.test_cuda(self, **kwargs)
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/testing/_internal/common_nn.py", line 3540, in test_cuda
    test_case.assertEqual(cpu_output, gpu_output, atol=self.precision, rtol=0, exact_dtype=False)
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/testing/_internal/common_utils.py", line 4164, in assertEqual
    raise error_metas.pop()[0].to_error(  # type: ignore[index]
AssertionError: Tensor-likes are not close!

Mismatched elements: 32 / 36 (88.9%)
Greatest absolute difference: 0.002995076089351345 at index (0, 2, 2) (up to 0.0002 allowed)
Greatest relative difference: 0.011596624546948736 at index (0, 0, 3) (up to 0 allowed)

To execute this test, run the following from the base repo dir:
    PYTORCH_TEST_WITH_ROCM=1 python test/test_nn.py TestNN.test_TransformerDecoderLayer_relu_activation_cuda_fp32

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0

Test file path: test_nn.py

For all disabled tests (by GitHub issue), see https://hud.pytorch.org/disabled.

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @naromero77amd @clee2000

[pytorch-bot]

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_TransformerDecoderLayer_relu_activation_cuda_fp32 (__main__.TestNN)
• Platforms for which to skip the test: rocm
• Disabled by pytorch-bot[bot]

Within ~15 minutes, test_TransformerDecoderLayer_relu_activation_cuda_fp32 (__main__.TestNN) 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 #157122 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]

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]

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]

Resolving the issue because the test is not flaky anymore after 150 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