Closed
Description
Platforms: linux
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 7 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_grad_with_manual_interleaved_ScheduleClass0_use_new_runtime_True - 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_distributed.py", line 1721, in wrapper
raise rv
AssertionError: Tensor-likes are not close!
Mismatched elements: 158 / 512 (30.9%)
Greatest absolute difference: 0.0002696812152862549 at index (331,) (up to 4e-05 allowed)
Greatest relative difference: 0.09954891353845596 at index (176,) (up to 1e-05 allowed)
To execute this test, run the following from the base repo dir:
python test/distributed/pipelining/test_schedule_multiproc.py ScheduleTest.test_grad_with_manual_interleaved_ScheduleClass0_use_new_runtime_True
This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0
Test file path: distributed/pipelining/test_schedule_multiproc.py
For all disabled tests (by GitHub issue), see https://hud.pytorch.org/disabled.
cc @H-Huang @awgu @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @clee2000