Platforms: linux, 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 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:

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_zero_bubble_with_model_kwargs_ScheduleClass1
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.

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: 6 / 512 (1.2%)
Greatest absolute difference: 0.006939894985407591 at index (77,) (up to 0.005 allowed)
Greatest relative difference: 3.2511918544769287 at index (375,) (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_zero_bubble_with_model_kwargs_ScheduleClass1

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