-
Notifications
You must be signed in to change notification settings - Fork 24.9k
Open
Labels
module: flaky-testsProblem is a flaky test in CIProblem is a flaky test in CImodule: functorchPertaining to torch.func or pytorch/functorchPertaining to torch.func or pytorch/functorchskippedDenotes a (flaky) test currently skipped in CI.Denotes a (flaky) test currently skipped in CI.triagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate moduleThis issue has been looked at a team member, and triaged and prioritized into an appropriate module
Description
Platforms: linux, slow, 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 5 workflow(s) with 5 failures and 5 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_op_has_batch_rule_mv_cuda_float32
- 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 "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/testing/_internal/common_utils.py", line 3108, in wrapper
method(*args, **kwargs)
File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/testing/_internal/common_utils.py", line 3108, in wrapper
method(*args, **kwargs)
File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/testing/_internal/common_utils.py", line 3107, in wrapper
with policy():
File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/testing/_internal/common_utils.py", line 2489, in __exit__
raise RuntimeError(msg)
RuntimeError: CUDA driver API confirmed a leak in __main__.TestVmapOperatorsOpInfoCUDA.test_op_has_batch_rule_mv_cuda_float32! Caching allocator allocated memory was 0 and is now reported as 1024 on device 0. CUDA driver allocated memory was 178520064 and is now 180617216.
To execute this test, run the following from the base repo dir:
PYTORCH_TEST_CUDA_MEM_LEAK_CHECK=1 python test/functorch/test_vmap.py TestVmapOperatorsOpInfoCUDA.test_op_has_batch_rule_mv_cuda_float32
This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0
Test file path: functorch/test_vmap.py
Metadata
Metadata
Assignees
Labels
module: flaky-testsProblem is a flaky test in CIProblem is a flaky test in CImodule: functorchPertaining to torch.func or pytorch/functorchPertaining to torch.func or pytorch/functorchskippedDenotes a (flaky) test currently skipped in CI.Denotes a (flaky) test currently skipped in CI.triagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate moduleThis issue has been looked at a team member, and triaged and prioritized into an appropriate module