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 4 workflow(s) with 12 failures and 4 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_mem_leak_from_save_for_bw
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 "functorch/test_aotdispatch.py", line 2652, in test_mem_leak_from_save_for_bw
self.assertTrue(mem_after == mem_before)
File "/opt/conda/envs/py_3.8/lib/python3.8/unittest/case.py", line 765, in assertTrue
raise self.failureException(msg)
AssertionError: False is not true
To execute this test, run the following from the base repo dir:
PYTORCH_TEST_WITH_ROCM=1 python test/functorch/test_aotdispatch.py TestAOTAutogradWithDynamo.test_mem_leak_from_save_for_bw
This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0
```
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_mem_leak_from_save_for_bw (__main__.TestAOTAutogradWithDynamo)`
* Platforms for which to skip the test: rocm
* Disabled by `pytorch-bot[bot]`
Within ~15 minutes, `test_mem_leak_from_save_for_bw (__main__.TestAOTAutogradWithDynamo)` 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 #136229` 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.
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 4 workflow(s) with 12 failures and 4 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:
test_mem_leak_from_save_for_bw
Sample error message
``` Traceback (most recent call last): File "functorch/test_aotdispatch.py", line 2652, in test_mem_leak_from_save_for_bw self.assertTrue(mem_after == mem_before) File "/opt/conda/envs/py_3.8/lib/python3.8/unittest/case.py", line 765, in assertTrue raise self.failureException(msg) AssertionError: False is not true To execute this test, run the following from the base repo dir: PYTORCH_TEST_WITH_ROCM=1 python test/functorch/test_aotdispatch.py TestAOTAutogradWithDynamo.test_mem_leak_from_save_for_bw This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0 ```Test file path:
functorch/test_aotdispatch.py
cc @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @clee2000 @ezyang @chauhang @penguinwu